Build #1 for gtk-strut-0.1.3.2
Package | gtk-strut-0.1.3.2 |
---|
Install | PlanningFailed |
---|---|
Docs | NotTried |
Tests | NotTried |
Time submitted | 2022-09-17 03:50:23.576451468 UTC |
---|---|
Compiler | ghc-9.2.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: gtk-strut-0.1.3.2 (user goal) [__1] next goal: gi-gtk (dependency of gtk-strut) [__1] rejecting: gi-gtk-4.0.5 (conflict: gtk-strut => gi-gtk>=3.0.38 && <4) [__1] skipping: gi-gtk-4.0.4, gi-gtk-4.0.3, gi-gtk-4.0.2, gi-gtk-4.0.1 (has the same characteristics that caused the previous version to fail: excluded by constraint '>=3.0.38 && <4' from 'gtk-strut') [__1] rejecting: gi-gtk-3.0.38 (conflict: pkg-config package gtk+-3.0-any, not found in the pkg-config database) [__1] rejecting: gi-gtk-3.0.37 (conflict: gtk-strut => gi-gtk>=3.0.38 && <4) [__1] skipping: gi-gtk-3.0.36, gi-gtk-3.0.35, gi-gtk-3.0.34, gi-gtk-3.0.33, gi-gtk-3.0.32, gi-gtk-3.0.31, gi-gtk-3.0.30, gi-gtk-3.0.29, gi-gtk-3.0.28, gi-gtk-3.0.27, gi-gtk-3.0.26, gi-gtk-3.0.25, gi-gtk-3.0.24, gi-gtk-3.0.23, gi-gtk-3.0.22, gi-gtk-3.0.21, gi-gtk-3.0.20, gi-gtk-3.0.19, gi-gtk-3.0.18, gi-gtk-3.0.17, gi-gtk-3.0.16, gi-gtk-3.0.15, gi-gtk-3.0.14, gi-gtk-3.0.13, gi-gtk-3.0.12, gi-gtk-3.0.11, gi-gtk-3.0.10, gi-gtk-3.0.9, gi-gtk-3.0.8, gi-gtk-3.0.7, gi-gtk-3.0.6, gi-gtk-3.0.5, gi-gtk-3.0.4, gi-gtk-3.0.3, gi-gtk-3.0.2, gi-gtk-3.0.1, gi-gtk-0.3.18.15, gi-gtk-0.3.18.14, gi-gtk-0.3.18.13, gi-gtk-0.3.18.12, gi-gtk-0.3.16.12, gi-gtk-0.3.18.10, gi-gtk-0.3.16.11, gi-gtk-0.3.16.10, gi-gtk-0.3.16.9, gi-gtk-0.3.16.8 (has the same characteristics that caused the previous version to fail: excluded by constraint '>=3.0.38 && <4' from 'gtk-strut') [__1] fail (backjumping, conflict set: gi-gtk, gtk-strut) After searching the rest of the dependency tree exhaustively, these were the goals I've had most trouble fulfilling: gtk-strut, gi-gtk
Test log
No test log was submitted for this report.