Build #2 for gi-xlib-2.0.5
| Package | gi-xlib-2.0.5 |
|---|
| Install | PlanningFailed |
|---|---|
| Docs | NotTried |
| Tests | NotTried |
| Time submitted | 2019-06-08 11:23:30.166549064 UTC |
|---|---|
| Compiler | ghc-8.6.3 |
| OS | linux |
| Arch | x86_64 |
| Dependencies | |
| Flags | none |
Code Coverage
No Code Coverage was submitted for this report.
Build log
[view raw]
Warning: The install command is a part of the legacy v1 style of cabal usage. Please switch to using either the new project style and the new-install command or the legacy v1-install alias as new-style projects will become the default in the next version of cabal-install. Please file a bug if you cannot replicate a working v1- use case with the new-style commands. For more information, see: https://wiki.haskell.org/Cabal/NewBuild Resolving dependencies... cabal: Could not resolve dependencies: [__0] trying: gi-xlib-2.0.5 (user goal) [__1] trying: haskell-gi-base-0.22.1 (dependency of gi-xlib) [__2] next goal: haskell-gi (dependency of gi-xlib) [__2] rejecting: haskell-gi-0.22.1, haskell-gi-0.22.0 (conflict: pkg-config package gobject-introspection-1.0>=1.32, not found in the pkg-config database) [__2] rejecting: haskell-gi-0.21.5, haskell-gi-0.21.4, haskell-gi-0.21.3, haskell-gi-0.21.2, haskell-gi-0.21.1, haskell-gi-0.21.0 (conflict: haskell-gi-base==0.22.1, haskell-gi => haskell-gi-base==0.21.*) [__2] rejecting: haskell-gi-0.20.3, haskell-gi-0.20.2, haskell-gi-0.20.1, haskell-gi-0.20, haskell-gi-0.18, haskell-gi-0.17.4, haskell-gi-0.17.3, haskell-gi-0.17.2, haskell-gi-0.17.1, haskell-gi-0.17, haskell-gi-0.15, haskell-gi-0.14, haskell-gi-0.13, haskell-gi-0.12, haskell-gi-0.11, haskell-gi-0.10.2, haskell-gi-0.10.1, haskell-gi-0.10, haskell-gi-0.9, haskell-gi-0.8 (conflict: gi-xlib => haskell-gi>=0.21.0 && <0.23) [__2] fail (backjumping, conflict set: gi-xlib, haskell-gi, haskell-gi-base) After searching the rest of the dependency tree exhaustively, these were the goals I've had most trouble fulfilling: haskell-gi, gi-xlib, haskell-gi-base
Test log
No test log was submitted for this report.