Closed pbrisbin closed 13 years ago
Through liberal use of --dry-run --verbose
, I'm making some headway.
It seems having deepseq 1.1 and 1.2 on your system at the same time is bad news. Different installs will link against different versions requiring reinstalls of other packages (like text) which breaks a lot of things.
Since aeson-native has a hard requirement for <1.2, I've removed that, unregistered whatever that broke and am more slowly and carefully rebuilding my install -- looking for any place that might try to bring 1.2 back in.
Will report back shortly (I hope).
Well, wasn't that fun.
Here, yesod-auth tries to reinstall cryptohash against crypto-api 0.6 which was brought in somewhere along the way by other yesod-something... ^C that if you're quick.
Ensure a clean ghc-pkg check
and all should be OK again.
I doubt this is yesod's fault -- but I'm hoping reporting here gets me a resolution.
Yesterday, I went through the various yesod packages and
git pull
ed and./scripts/install
ed. Everything was going pretty well until I got to theyesod
repo.Since then, I've tried removing
.ghc
and.cabal
, reinstalling and trying again -- same error. I've even gone so far as removing ghc entirely, rebooting, and trying again. Same error.Attempting to install yesod-core:
OK, so what if I install the older
deepseq
:Same error!?
How bout if I try to install
aeson-native
itself:WTF? Half of those packages are already installed.
And if I let you re-install them, it'll break half my other packages... Then re-installing those will break others and I'll end up back at the original dependency conflict (I've gone around that loop a few times).
Any ideas?