You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Error: While constructing the build plan, the following exceptions were encountered:
In the dependencies for cabal-install-3.2.0.0:
Cabal-2.4.0.1 from stack configuration does not match ==3.2.* (latest matching version is 3.2.0.0)
hackage-security must match >=0.6.0.0 && <0.7, but the stack configuration has no specified version (latest matching version is 0.6.0.0)
lukko must match >=0.1 && <0.2, but the stack configuration has no specified version (latest matching version is 0.1.1.2)
needed since cabal-install is a build target.
Some different approaches to resolving this:
* Recommended action: try adding the following to your extra-deps in /home/arch/.asdf/installs/haskell/8.6.5/stack/global-project/stack.yaml:
- Cabal-3.2.0.0@sha256:d0d7a1f405f25d0000f5ddef684838bc264842304fd4e7f80ca92b997b710874,27320
- hackage-security-0.6.0.0@sha256:69987d46e7b55fe5f0fc537021c3873c5f6f44a6665d349ee6995fd593df8147,11976
- lukko-0.1.1.2@sha256:c9d3fa30fb6ab2ba16e037586ca79be6e57ec5f00381b6ee5f293400dbdf5515,4485
Plan construction failed.
Adding extra-deps, as the message described, fixed the error.
But is this expected behavior or there's something wrong with my installation?
$ ghc --version
The Glorious Glasgow Haskell Compilation System, version 8.6.5
The text was updated successfully, but these errors were encountered:
Nothing wrong with your installation exactly, the README is just missing some detail.
You need to use the correct resolver to fetch from a Stackage snapshot that has all the packages you need. Adding packages to extra-deps fetches those from Hackage, not a Stackage snapshot, so this works around the problem, but using --resolver lts-14.27 solves it without manually editing files. You can also set the default resolver in the config, see: https://docs.haskellstack.org/en/stable/yaml_configuration/#resolver
I've tried running
But it failed:
Adding
extra-deps
, as the message described, fixed the error.But is this expected behavior or there's something wrong with my installation?
The text was updated successfully, but these errors were encountered: