-
Notifications
You must be signed in to change notification settings - Fork 12
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
transformers-compat-0.3.3.4 incompatible with transformers-0.3.0.0 from latest HP #5
Comments
Ran into this problem temporarily. Including some other dependencies made the problem go away but not sure why. But this is a pretty annoying problem when it happens. |
FWIW, I just hit this issue because I had other dependency problems which seemed to confuse the solver into thinking that it was transformers-compat & transformers that were breaking things. I installed transformers-compat with -f three and resolved my other conflicts. After everything built successfully I deleted and initialised the sandbox and everything installed just fine without passing the flag to transformers-compat. It's annoying that this error comes up as a red-herring, but it's nice to know that it doesn't break a package with a sane dependency set. :) |
Running into this problem with GHC 7.8.4 and the |
A relevant discussion might be the following one — if you still have this issue, please document the version of cabal-install you're using, since apparently transformers-compat runs into cabal completeness bugs when constructing the build plan (I'm confused whether the bugs only happen without --reorder-goals): |
Indeed, this is simply a I don't know what |
I'm working around ekmett/lens#458 by installing transformers-compat, but the latest version refuses to install, unless I manually provide
-f three
:I've later found this is documented in
https://github.com/ekmett/transformers-compat/commit/v0.3.3.4, but that seems a bit too little. Also, that's not the default behavior I get:
The text was updated successfully, but these errors were encountered: