The standard rm -rf ~/.ghc solution didn't help: $ cabal install Cabal cabal-install Resolving dependencies... In order, the following would be installed: array-0.3.0.3 (new version) deepseq-1.3.0.0 (reinstall) changes: array-0.4.0.0 -> 0.3.0.3 containers-0.4.2.1 (reinstall) changes: array-0.4.0.0 -> 0.3.0.3 filepath-1.2.0.1 (new version) old-time-1.0.0.7 (new version) pretty-1.0.1.2 (new version) text-0.11.2.0 (new package) time-1.2.0.5 (new version) random-1.0.1.1 (new package) transformers-0.3.0.0 (new package) mtl-2.1 (new package) parsec-3.1.2 (new package) unix-2.3.2.0 (new version) directory-1.1.0.2 (reinstall) changes: filepath-1.3.0.0 -> 1.2.0.1, old-time-1.1.0.0 -> 1.0.0.7, unix-2.5.1.0 -> 2.3.2.0 network-2.3.0.11 (new package) HTTP-4000.2.3 (new package) process-1.0.1.5 (new version) Cabal-1.10.2.0 (new version) zlib-0.5.3.3 (new package) cabal-install-0.10.2 -bytestring-in-base (new package) cabal: The install plan contains reinstalls which can break your GHC installation. You can try --solver=modular for the new modular solver that chooses such reinstalls less often and also offers the --avoid-reinstalls option. You can also ghc-pkg unregister the affected packages and run ghc-pkg check to see the effect on reverse dependencies. If you know what you are doing you can use the --force-reinstalls option to override this reinstall check.
$ ghc-pkg list /Library/Frameworks/GHC.framework/Versions/7.4.1-i386/usr/lib/ghc-7.4.1/package.conf.d Cabal-1.14.0 array-0.4.0.0 base-4.5.0.0 bin-package-db-0.0.0.0 binary-0.5.1.0 bytestring-0.9.2.1 containers-0.4.2.1 deepseq-1.3.0.0 directory-1.1.0.2 extensible-exceptions-0.1.1.4 filepath-1.3.0.0 ghc-7.4.1 ghc-prim-0.2.0.0 haskell2010-1.1.0.1 haskell98-2.0.0.1 hoopl-3.8.7.3 hpc-0.5.1.1 integer-gmp-0.4.0.0 old-locale-1.0.0.4 old-time-1.1.0.0 pretty-1.1.1.0 process-1.1.0.1 rts-1.0 template-haskell-2.7.0.0 time-1.4 unix-2.5.1.0 _______________________________________________ Haskell mailing list Haskell@haskell.org http://www.haskell.org/mailman/listinfo/haskell