Build #5 for dotenv-0.1.0.9
| Package | dotenv-0.1.0.9 |
|---|
| Install | PlanningFailed |
|---|---|
| Docs | NotTried |
| Tests | NotTried |
| Time submitted | 2020-10-29 07:02:55.228223681 UTC |
|---|---|
| Compiler | ghc-8.10.2 |
| OS | linux |
| Arch | x86_64 |
| Dependencies | |
| Flags | none |
Code Coverage
No Code Coverage was submitted for this report.
Build log
[view raw]
Resolving dependencies... cabal: Could not resolve dependencies: [__0] next goal: dotenv (user goal) [__0] rejecting: dotenv-0.8.0.7, dotenv-0.8.0.6, dotenv-0.8.0.4, dotenv-0.8.0.3, dotenv-0.8.0.2, dotenv-0.8.0.1, dotenv-0.8.0.0, dotenv-0.7.0.0, dotenv-0.6.0.3, dotenv-0.6.0.2, dotenv-0.6.0.1, dotenv-0.5.2.5, dotenv-0.5.2.4, dotenv-0.5.2.3, dotenv-0.5.2.2, dotenv-0.5.2.1, dotenv-0.5.2.0, dotenv-0.5.1.1, dotenv-0.5.1.0, dotenv-0.5.0.2, dotenv-0.5.0.1, dotenv-0.5.0.0, dotenv-0.4.0.0, dotenv-0.3.4.0, dotenv-0.3.3.0, dotenv-0.3.2.0, dotenv-0.3.1.0, dotenv-0.3.0.3, dotenv-0.3.0.2, dotenv-0.3.0.1, dotenv-0.3.0.0 (constraint from user target requires ==0.1.0.9) [__0] trying: dotenv-0.1.0.9 [__1] next goal: base (dependency of dotenv) [__1] rejecting: base-4.14.1.0/installed-4.14.1.0 (conflict: dotenv => base>=4.5 && <4.9) [__1] skipping: base-4.14.0.0, base-4.13.0.0, base-4.12.0.0, base-4.11.1.0, base-4.11.0.0, base-4.10.1.0, base-4.10.0.0, base-4.9.1.0, base-4.9.0.0 (has the same characteristics that caused the previous version to fail: excluded by constraint '>=4.5 && <4.9' from 'dotenv') [__1] rejecting: base-4.8.2.0, base-4.8.1.0, base-4.8.0.0, base-4.7.0.2, base-4.7.0.1, base-4.7.0.0, base-4.6.0.1, base-4.6.0.0, base-4.5.1.0, base-4.5.0.0, base-4.4.1.0, base-4.4.0.0, base-4.3.1.0, base-4.3.0.0, base-4.2.0.2, base-4.2.0.1, base-4.2.0.0, base-4.1.0.0, base-4.0.0.0, base-3.0.3.2, base-3.0.3.1 (constraint from non-upgradeable package requires installed instance) [__1] fail (backjumping, conflict set: base, dotenv) After searching the rest of the dependency tree exhaustively, these were the goals I've had most trouble fulfilling: dotenv, base
Test log
No test log was submitted for this report.