Can nix solve cabal dependency tree conflicts?

[cdepillabout]

@AngeloChecked

Is nix the right tool to fix this problem, or is this library broken and I can’t do anything about it?

Nix mostly doesn’t help you with cabal dependency conflicts.

There are a couple different ways to get started with Nix and Haskell:

Super-Simple Haskell Development with Nix

the simplest, most beginner-friendly approach to developing Haskell under Nix I think what you have here probably is the easiest approach to getting started with Nix + Haskell. For other people reading this, there are a couple other approaches to developing Haskell under Nix that you may want to consider: Use Nix to get GHC, cabal, and system deps. Then use cabal to download and build all Haskell dependencies: $ nix-shell -p haskell.compiler.ghc8104 -p cabal-instal -p zlib # zlib here i…

Although if you have a .cabal file with dependency bounds that can’t be satisfied, nothing here will really help you.

---

If I had to guess what your problem is from your .cabal file, its that you’re using the wrong version of GHC. It is possible that amazonka-certificatemanager (or some transitive dependencies of amazonka-certificatemanager) only work with a specific version of GHC, and you’re not using that version. It looks like you’re on GHC-9.2, so I’d try changing to 9.0 or 8.10.

You might also want to add some additional build-depends with hard constraints for common libraries (like aeson == 1.5.6.0, amazonka-core == 1.6.1) to help the cabal solver out a little.

---

This probably doesn’t matter to you if you’re just playing around, but there is a new version of amazonka that hasn’t been released yet, but works with newer versions of some of the common transitive dependencies:

Amazonka 2.0