Using latest GHC 9.4.3 to compile conferer results in errors caused by upper bounds on dependencies. For example, running cabal build in packages/conferer results in:
Error: cabal: Could not resolve dependencies:
[__0] trying: conferer-aeson-1.1.0.2 (user goal)
[__1] trying: unordered-containers-0.2.19.1 (dependency of conferer-aeson)
[__2] trying: hashable-1.4.1.0 (dependency of unordered-containers)
[__3] trying: text-2.0.1/installed-2.0.1 (dependency of conferer-aeson)
[__4] next goal: conferer (dependency of conferer-aeson)
[__4] rejecting: conferer-1.1.0.0 (conflict: text==2.0.1/installed-2.0.1,
conferer => text>=1.1 && <1.3)
[__4] skipping: conferer-1.0.0.1, conferer-1.0.0.0, conferer-0.4.1.1,
conferer-0.4.1.0, conferer-0.4.0.0, conferer-0.3.0.0, conferer-0.2.0.0,
conferer-0.1.0.4, conferer-0.1.0.3, conferer-0.1.0.2, conferer-0.1.0.1,
conferer-0.1.0.0 (has the same characteristics that caused the previous
version to fail: excludes 'text' version 2.0.1)
[__4] fail (backjumping, conflict set: conferer, conferer-aeson, text)
After searching the rest of the dependency tree exhaustively, these were the
goals I've had most trouble fulfilling: hashable, text, base, conferer,
conferer-aeson, unordered-containers
Try running with --minimize-conflict-set to improve the error message
Removing upper bound on text library resolves the issue and conferer then builds without problems. Similarly, conferer-aeson fails to build because of upper bounds on text and aeson and removing those bounds solves the problem. I haven't tried other libraries in the repo but I expect to see similar problems (and solutions).
Using latest GHC 9.4.3 to compile
conferer
results in errors caused by upper bounds on dependencies. For example, runningcabal build
inpackages/conferer
results in:Removing upper bound on
text
library resolves the issue andconferer
then builds without problems. Similarly,conferer-aeson
fails to build because of upper bounds ontext
andaeson
and removing those bounds solves the problem. I haven't tried other libraries in the repo but I expect to see similar problems (and solutions).