-
Notifications
You must be signed in to change notification settings - Fork 841
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Stack cabal version deviates from its LTS version #3417
Comments
Okay, beats me who it got there, but I see a
I deleted
Could it possibly be that some extra package or something in a |
The cabal version used by stack is not the one specified by resolver. To me this behavior is also counter-intuitive. There is a discussion of this here, closing this as a dupe of that, if I understand correctly. |
Moving to here from DanielG/ghc-mod#905, since it seems to be more related to stack. Please read that issue for more information.
If there is any additional information I can provide, please let me know!
stack version is,
but the issue was already present in
1.3.x
.I think it maybe can be boiled down to the
dist-dir
being set tocabal-2.0.0.2
even though the resolver is set tolts-9.2
. This causes things like e.g.ghc-mod
to get a wrong cabal version which causes it to error out as mentioned in the earlier linked issue.E.g.
nightly-2017-09-04
usescabal-2.0.0.2
andlts-9.3
usescabal-1.24.2.0
.Replicating
$ stack new Test
defaulted tolts-9.3
$ cd Test
$ ghc-mod check src/Lib.hs
The expectation here is of course that it does not fail compilation. Notably you can see it pulls in
/Users/tehnix/Dropbox/__Synced/Testing/Haskell/Test/.stack-work/dist/x86_64-osx/Cabal-2.0.0.2
, for which it automatically creates the.stack-work
for. Nuking it and rerunning produces the same output.The text was updated successfully, but these errors were encountered: