Closed Blaisorblade closed 8 years ago
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.
@robertmassaioli
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 transformers
installed as part of it. Glad I found this thread, but it should probably be documented somewhere more prominent.
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): https://github.com/haskell/cabal/issues/1855#issuecomment-43503323 https://github.com/haskell/cabal/issues/1855#issuecomment-50594924
Indeed, this is simply a cabal-install
issue. As https://github.com/haskell/cabal/issues/1855#issuecomment-50594924 notes, modern cabal-install
(version 1.22 and up) shouldn't have this problem, and if you're using an older version, you should be using the 1.20.0.3 or 1.18.0.5 patch releases.
I don't know what transformers-compat
can do about this, so I'll close this issue.
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: