Build #1 for stackctl-1.7.3.5
Package | stackctl-1.7.3.5 |
---|
Install | PlanningFailed |
---|---|
Docs | NotTried |
Tests | NotTried |
Time submitted | 2025-07-03 16:19:23.125392013 UTC |
---|---|
Compiler | ghc-9.8.4 |
OS | linux |
Arch | x86_64 |
Dependencies | |
Flags | none |
Code Coverage
No Code Coverage was submitted for this report.
Build log
[view raw]
Resolving dependencies... Error: cabal: Could not resolve dependencies: [__0] trying: stackctl-1.7.3.5 (user goal) [__1] trying: base-4.19.2.0/installed-inplace (dependency of stackctl) [__2] next goal: amazonka-sts (dependency of stackctl) [__2] rejecting: amazonka-sts-2.0 (conflict: base==4.19.2.0/installed-inplace, amazonka-sts => base>=4.12 && <4.19) [__2] skipping: amazonka-sts-1.6.1, amazonka-sts-1.6.0, amazonka-sts-1.5.0, amazonka-sts-1.4.5, amazonka-sts-1.4.4, amazonka-sts-1.4.3, amazonka-sts-1.4.2, amazonka-sts-1.4.1, amazonka-sts-1.4.0, amazonka-sts-1.3.7, amazonka-sts-1.3.6, amazonka-sts-1.3.5, amazonka-sts-1.3.4, amazonka-sts-1.3.3.1, amazonka-sts-1.3.3, amazonka-sts-1.3.2, amazonka-sts-1.3.1, amazonka-sts-1.3.0, amazonka-sts-1.2.0.2, amazonka-sts-1.2.0.1, amazonka-sts-1.2.0, amazonka-sts-1.1.0, amazonka-sts-1.0.1, amazonka-sts-1.0.0, amazonka-sts-0.3.6, amazonka-sts-0.3.5, amazonka-sts-0.3.4, amazonka-sts-0.3.3, amazonka-sts-0.3.2, amazonka-sts-0.3.1, amazonka-sts-0.3.0, amazonka-sts-0.2.3, amazonka-sts-0.2.2, amazonka-sts-0.2.1, amazonka-sts-0.2.0, amazonka-sts-0.1.4, amazonka-sts-0.1.3, amazonka-sts-0.1.2, amazonka-sts-0.1.1, amazonka-sts-0.1.0, amazonka-sts-0.0.8, amazonka-sts-0.0.7, amazonka-sts-0.0.6, amazonka-sts-0.0.5, amazonka-sts-0.0.4, amazonka-sts-0.0.3, amazonka-sts-0.0.2, amazonka-sts-0.0.1, amazonka-sts-0.0.0 (has the same characteristics that caused the previous version to fail: excludes 'base' version 4.19.2.0) [__2] fail (backjumping, conflict set: amazonka-sts, base, stackctl) After searching the rest of the dependency tree exhaustively, these were the goals I've had most trouble fulfilling: base, amazonka-sts, stackctl
Test log
No test log was submitted for this report.