Build #2 for diagrams-pandoc-0.4
| Package | diagrams-pandoc-0.4 |
|---|
| Install | PlanningFailed |
|---|---|
| Docs | NotTried |
| Tests | NotTried |
| Time submitted | 2024-02-29 18:51:05.067598987 UTC |
|---|---|
| Compiler | ghc-9.6.3 |
| 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: diagrams-pandoc-0.4 (user goal) [__1] trying: text-2.0.2/installed-2.0.2 (dependency of diagrams-pandoc) [__2] trying: diagrams-cairo-1.4.2.1 (dependency of diagrams-pandoc) [__3] next goal: pango (dependency of diagrams-cairo) [__3] rejecting: pango-0.13.10.0 (conflict: pkg-config package pango>=1.0, not found in the pkg-config database) [__3] rejecting: pango-0.13.8.2 (conflict: text==2.0.2/installed-2.0.2, pango => text>=0.11.0.6 && <1.3) [__3] skipping: pango-0.13.8.1, pango-0.13.8.0, pango-0.13.6.1, pango-0.13.6.0, pango-0.13.5.0, pango-0.13.4.0, pango-0.13.3.1, pango-0.13.3.0, pango-0.13.2.0, pango-0.13.1.1, pango-0.13.1.0, pango-0.13.0.5, pango-0.13.0.4, pango-0.13.0.3, pango-0.13.0.2, pango-0.13.0.1, pango-0.13.0.0 (has the same characteristics that caused the previous version to fail: excludes 'text' version 2.0.2) [__3] rejecting: pango-0.12.5.3, pango-0.12.5.0 (conflict: pkg-config package pango>=1.0, not found in the pkg-config database) [__3] rejecting: pango-0.12.4 (conflict: diagrams-cairo => pango>=0.12.5 && <0.14) [__3] skipping: pango-0.12.3, pango-0.12.2, pango-0.12.1, pango-0.12.0, pango-0.11.2, pango-0.11.1, pango-0.11.0 (has the same characteristics that caused the previous version to fail: excluded by constraint '>=0.12.5 && <0.14' from 'diagrams-cairo') [__3] fail (backjumping, conflict set: diagrams-cairo, pango, text) After searching the rest of the dependency tree exhaustively, these were the goals I've had most trouble fulfilling: text, pango, diagrams-cairo, diagrams-pandoc Try running with --minimize-conflict-set to improve the error message.
Test log
No test log was submitted for this report.