Hi there! Excuse me, but I am a bit bewildered; should I really have to give cabal --force-reinstalls to upgrade yesod to the new version 1.1.0.2? It says a lot of packages are likely to be broken, as per the paste http://pastebin.com/cYdZkShu. I was under the impression I had RTFM, but maybe I have missed something? /Fredrik
Hi.
Hi there! Excuse me, but I am a bit bewildered; should I really have to give cabal --force-reinstalls to upgrade yesod to the new version 1.1.0.2? It says a lot of packages are likely to be broken, as per the paste http://pastebin.com/cYdZkShu.
I strongly suggest not to use --upgrade-dependencies. It's probably unavoidable to break *some* (Yesod-related) packages for a framework with as many dependencies as Yesod has, unless you use sandboxing. But you shouldn't go ahead installing something if packages like "bin-package-db" or "ghc" appear among the ones that are going to be broken. I've just tested that starting from the 2012.2.0.0 platform and yesod-platform-1.0.4.2, a simple $ cabal install --dry-run yesod yields Resolving dependencies... In order, the following would be installed: clientsession-0.8.0 (new version) conduit-0.5.2.3 (new version) attoparsec-conduit-0.5.0 (new version) blaze-builder-conduit-0.5.0 (new version) http-types-0.7.3 (new version) network-conduit-0.5.0 (new version) shakespeare-1.0.1.1 (new version) hamlet-1.1.0.2 (new version) shakespeare-css-1.0.1.4 (new version) shakespeare-i18n-1.0.0.2 (reinstall) changes: shakespeare-1.0.0.2 -> 1.0.1.1 shakespeare-js-1.0.0.5 (new version) shakespeare-text-1.0.0.4 (new version) simple-sendfile-0.2.6 (new version) stringsearch-0.3.6.3 (new package) tar-0.4.0.0 (new package) unix-time-0.1.2 (new package) fast-logger-0.2.2 (new version) monad-logger-0.2.0 (new package) persistent-1.0.0 (new version) persistent-template-1.0.0 (new version) wai-1.3.0 (new version) wai-logger-0.2.0 (new version) warp-1.3.0.1 (new version) xml-types-0.3.3 (new version) xml-conduit-1.0.3 (new version) yaml-0.8.0.1 (new version) yesod-routes-1.1.0 (new version) zlib-conduit-0.5.0 (new version) http-conduit-1.6.0 (new version) authenticate-1.3.1 (new version) wai-extra-1.3.0 (new version) yesod-core-1.1.1 (new version) yesod-json-1.1.0 (new version) yesod-persistent-1.1.0 (new version) yesod-form-1.1.1 (new version) yesod-auth-1.1.1 (new version) yesod-1.1.0.2 (new version) Warning: The following packages are likely to be broken by the reinstalls: yesod-platform-1.0.4.2 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-auth-1.0.2.1 yesod-1.0.1.6 yesod-json-1.0.0.1 yesod-default-1.0.1.1 Use --force-reinstalls if you want to install anyway. for me, which looks reasonably safe to do with --force-reinstalls. Cheers, Andres
Hello, I ran into some dependency issues with cabal/ghc and could not find any solution on the internet. ghc-pkg check returns nothing, I suppose this is a good thing. But ghc -v returns: ----------------- Glasgow Haskell Compiler, Version 7.4.1, stage 2 booted by GHC version 7.4.1 Using binary package database: /usr/lib/ghc/package.conf.d/package.cache Using binary package database: /home/ming/.ghc/x86_64-linux-7.4.1/package.conf.d/package.cache package blaze-svg-0.3.3.0-50a04482f1f501336d4772805c49480c is unusable due to missing or recursive dependencies: mtl-2.1.1-801101765c9185fec3b8dbd5355f5550 package cairo-0.12.3.1-b5380fec59ee27dbcea4803a68e97987 is unusable due to missing or recursive dependencies: mtl-2.1.1-801101765c9185fec3b8dbd5355f5550 package gio-0.12.3-d4fa99730a97194e714a9725fe2ce6eb is unusable due to missing or recursive dependencies: mtl-2.1.1-801101765c9185fec3b8dbd5355f5550 package gtk-0.12.3.1-b4f922f5295267731eb0ea058e8ec63b is unusable due to missing or recursive dependencies: cairo-0.12.3.1-b5380fec59ee27dbcea4803a68e97987 gio-0.12.3-d4fa99730a97194e714a9725fe2ce6eb mtl-2.1.1-801101765c9185fec3b8dbd5355f5550 pango-0.12.3-86ce88701ca575a64c78e01efb6107e7 package httpd-shed-0.4-4efc4f08c1e731625a137a46b01eaa91 is unusable due to missing or recursive dependencies: network-2.3.1.0-acf1a3e75cbe81f030e6d7af508f064a package network-2.3.1.0-acf1a3e75cbe81f030e6d7af508f064a is unusable due to missing or recursive dependencies: parsec-3.1.3-0cb02763c2a282c8ea5c85882f9bf27d package pango-0.12.3-86ce88701ca575a64c78e01efb6107e7 is unusable due to missing or recursive dependencies: cairo-0.12.3.1-b5380fec59ee27dbcea4803a68e97987 mtl-2.1.1-801101765c9185fec3b8dbd5355f5550 package parsec-3.1.3-0cb02763c2a282c8ea5c85882f9bf27d is unusable due to missing or recursive dependencies: mtl-2.1.1-801101765c9185fec3b8dbd5355f5550 package soegtk-0.12.1-da31ebdf63cd5bad394b6fa20d55647e is unusable due to missing or recursive dependencies: cairo-0.12.3.1-b5380fec59ee27dbcea4803a68e97987 gtk-0.12.3.1-b4f922f5295267731eb0ea058e8ec63b wired-in package ghc-prim mapped to ghc-prim-0.2.0.0-c2ff696e5b8ec4d4b2bc2e42085fe471 wired-in package integer-gmp mapped to integer-gmp-0.4.0.0-3cccac07aef8e27023f605c1f45bdf74 wired-in package base mapped to base-4.5.0.0-40b99d05fae6a4eea95ea69e6e0c9702 wired-in package rts mapped to builtin_rts wired-in package template-haskell mapped to template-haskell-2.7.0.0-8c8cd20e21666657195efabced685fe1 wired-in package dph-seq not found. wired-in package dph-par not found. Hsc static flags: -static *** Deleting temp files: Deleting: *** Deleting temp dirs: Deleting: ghc: no input files Usage: For basic information, try the `--help' option. -------------------------- This looks really scary to me. I already reinstalled GHC completely but it didn't change anything. Is there anything I can do? Thank you in advance.
Hello, nevermind, I solved this problem already. In case some of you face this too: I purged ghc again, then removed .ghc in my home folder and reinstalled it.
On Fri, Aug 24, 2012 at 12:17:49PM +0200, Ming Gao wrote:
Hello, nevermind, I solved this problem already. In case some of you face this too: I purged ghc again, then removed .ghc in my home folder and reinstalled it.
Yes, that is probably the quickest way. For future reference, you could also try unregistering all the packages it said were unusable (via ghc-pkg unregister) and then reinstalling them. With newer versions of cabal-instal this should happen much less often. Don't ignore its warnings about dangerous reinstalls. -Brent
participants (4)
-
Andres Löh -
Brent Yorgey -
Ming Gao -
Obscaenvs