I am trying to install updated version of yesod-platform, and got this output from "cabal install yesod-platform". Could someone please advise on the most efficient way to proceed? SHA-1.5.1 (new version) asn1-data-0.7.1 (new version) base-unicode-symbols-0.2.2.4 (new version) base64-bytestring-1.0.0.0 (new version) blaze-markup-0.5.1.1 (new version) blaze-html-0.5.1.0 (new version) cipher-aes-0.1.2 (new package) data-default-0.5.0 (new version) cookie-0.4.0.1 (new version) date-cache-0.3.0 (new package) file-embed-0.0.4.6 (new version) hashable-1.1.2.5 (new version) case-insensitive-0.4.0.3 (new version) hspec-expectations-0.3.0.2 (new package) hspec-1.3.0.1 (new version) ... many more, snipping ... my concern was the next part of the message cabal: The following packages are likely to be broken by the reinstalls: yesod-platform-1.0.5 tls-extra-0.4.6 http-conduit-1.4.1.10 yesod-auth-1.0.2.1 yesod-1.0.1.6 authenticate-1.2.1.1 certificate-1.2.3 tls-0.9.5 yesod-core-1.0.1.2 yesod-static-1.0.0.3 yesod-persistent-1.0.0.1 yesod-form-1.0.0.4 yesod-json-1.0.0.1 yesod-default-1.0.1.1 skein-0.1.0.7 clientsession-0.7.5 pureMD5-2.1.0.3 wai-app-static-1.2.0.4 pwstore-fast-2.2 cprng-aes-0.2.3 crypto-conduit-0.3.2 yaml-0.7.0.3 persistent-template-0.9.0.2 persistent-sqlite-0.9.0.2 persistent-0.9.0.4 yesod-test-0.2.1 Use --force-reinstalls if you want to install anyway.
A 29/10/2012, às 23:10, Michael Litchard escreveu:
I am trying to install updated version of yesod-platform, and got this output from "cabal install yesod-platform". Could someone please advise on the most efficient way to proceed?
I get this sort of errors all the time and never seem to understand how to fix them. Is there some place I can read on how to understand these errors, and understand what to do about them, instead of feeling totally at loss and coming every time to the list to ask for help ? Also, why can the reinstalls mess up things ? best Miguel Negrão
On Tue, Oct 30, 2012 at 1:00 AM, Miguel Negrao
A 29/10/2012, às 23:10, Michael Litchard escreveu:
I am trying to install updated version of yesod-platform, and got this output from "cabal install yesod-platform". Could someone please advise on the most efficient way to proceed?
I get this sort of errors all the time and never seem to understand how to fix them. Is there some place I can read on how to understand these errors, and understand what to do about them, instead of feeling totally at loss and coming every time to the list to ask for help ? Also, why can the reinstalls mess up things ?
There is some good explanations of that phenomenon around under the name "Butterfly effect" like : http://cdsmith.wordpress.com/2011/01/17/the-butterfly-effect-in-cabal/ This is really painful when you start to have accumulated a number of packages, and the more dependencies, the more likely you are to hit this... Which is why most people now recommend using sandboxes for installations, to allows you to have several different packages database and not have to scratch your whole GHC installation once you've damaged it (there are always alternative to this radical step, but it takes more time than restarting from zero so nobody use them). Basically, as soon as you hit a problem with a cabal installation that would require a reinstall, you restart from a new sandbox. The solutions to do that are virthualenv, capri or cabal-dev and the next release of cabal itself should have a sandbox mode. The proper solution would be to allow several version of the same package version to cohabit but that's pretty complicated and not yet possible. -- Jedaï
A 30/10/2012, às 09:33, Chaddaï Fouché escreveu:
There is some good explanations of that phenomenon around under the name "Butterfly effect" like : http://cdsmith.wordpress.com/2011/01/17/the-butterfly-effect-in-cabal/
This is really painful when you start to have accumulated a number of packages, and the more dependencies, the more likely you are to hit this... Which is why most people now recommend using sandboxes for installations, to allows you to have several different packages database and not have to scratch your whole GHC installation once you've damaged it (there are always alternative to this radical step, but it takes more time than restarting from zero so nobody use them). Basically, as soon as you hit a problem with a cabal installation that would require a reinstall, you restart from a new sandbox. The solutions to do that are virthualenv, capri or cabal-dev and the next release of cabal itself should have a sandbox mode.
The proper solution would be to allow several version of the same package version to cohabit but that's pretty complicated and not yet possible.
After reading that post and a couple others I tried to install cabal-dev which is supposed to help with some of these issues. Ironically it doesn’t install either... miguelnegrao@Mac-Miguel:~$ cabal install cabal-dev Resolving dependencies... [1 of 1] Compiling Main ( /var/folders/ps/fvzyp6yj5k743k1clpmt24kw0000gn/T/cabal-dev-0.9.1-11243/cabal-dev-0.9.1/Setup.hs, /var/folders/ps/fvzyp6yj5k743k1clpmt24kw0000gn/T/cabal-dev-0.9.1-11243/cabal-dev-0.9.1/dist/setup/Main.o ) Linking /var/folders/ps/fvzyp6yj5k743k1clpmt24kw0000gn/T/cabal-dev-0.9.1-11243/cabal-dev-0.9.1/dist/setup/setup ... ld: warning: could not create compact unwind for _ffi_call_unix64: does not use RBP or RSP based frame unrecognized option `--disable-benchmarks' Failed to install cabal-dev-0.9.1 cabal: Error: some packages failed to install: cabal-dev-0.9.1 failed during the configure step. The exception was: ExitFailure 1 miguelnegrao@Mac-Miguel:~$ cabal -V cabal-install version 1.16.0.1 using version 1.16.0.2 of the Cabal library Is this a lost cause ? :-) best, Miguel
A 30/10/2012, às 18:54, Miguel Negrao escreveu:
After reading that post and a couple others I tried to install cabal-dev which is supposed to help with some of these issues. Ironically it doesn’t install either...
Ok, I think that was because I was using ghc 7.0.4, I updated to 7.4 (haskell platform latest version) and also first uninstalled the haskell platform and nuked ~/.ghc and ~/.cabal and started over (but now using jobs:8 in ~/.cabal/config after having updated to cabal-install-1.16.0.1 ) and quickly got up to date. cabal-dev also installed fine. Let’s hope I get an easier ride from now on. :-) best, Miguel
participants (3)
-
Chaddaï Fouché -
Michael Litchard -
Miguel Negrao