-
Notifications
You must be signed in to change notification settings - Fork 843
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
allow-newer causes setup failure #1579
Comments
See haskell/cabal#2023 for some background on this. Looks like we need to pass in I think we may actually want to always use Searching cabal's source code revealed this - looks like |
Just encountered this myself, definitely ought to get fixed.. |
Hit this one too; would be very useful with the upcoming GHC release |
@mgsloan said
I ran into this problem on |
@radix It won't work for LTS < 3, and I don't think there's anything we can do about it. This also affected cabal-install - see haskell/cabal#2023
|
@mgsloan ah, I think I misparsed your original comment. |
This is really bad. It is very difficult to build anything with |
@tolysz Thanks for bumping this issue. I'd worked on it, but ran into some issues and hadn't got back to it. I think it's fixed now. Currently waiting on a ghc 8.0 build of stack :) |
Pushed a fix to the fix. |
It seems like allow-newer doesn't always allow-newer! The essential parts of the reproduction below are:
mmorph
transformers-0.5.0.0
is inextra-deps
mmorph
Doesn't allowtransformers-0.5.0.0
allow-newer: True
stack build
errors out withConfiguring mmorph-1.0.4... setup-Simple-Cabal-1.22.5.0-ghc-7.10.3: At least the following dependencies are missing: transformers >=0.2.0.0 && <0.5 && ==0.5.0.0
Currently the only workaround I've found is to add
mmorph
as a local package and relaxing the transformers constraint in its cabal file.Full reproduction:
The text was updated successfully, but these errors were encountered: