Re: Error while installing new packages with GHC 7.4.1

Hi Antoras,
My suspicion is you've ended up with corrupted packages in your
package database - nothing to do with Hoogle. I suspect trying to
install parsec-3.1.2 directly would give the same error message. Can
you try ghc-pkg list, and at the bottom it will probably say something
like:
The following packages are broken, either because they have a problem
listed above, or because they depend on a broken package.
warp-1.1.0
I often find ghc-pkg unregister <warp> --force on all the packages
cleans them up enough, but someone else may have a better suggestion.
Thanks, Neil
On Fri, Mar 2, 2012 at 12:02 AM, Antoras
Hi Neil,
thanks for your effort. But it still does not work. The old errors disappeared, but new ones occur.
Maybe I have not yet the most current versions:
$ ghc --version The Glorious Glasgow Haskell Compilation System, version 7.4.1
$ cabal --version cabal-install version 0.10.2 using version 1.10.1.0 of the Cabal library
This seems to be the most current version of Cabal. The command 'cabal info cabal' brings: "Versions installed: 1.14.0" but not 1.15
An extract of the error messages:
[...] Configuring parsec-3.1.2... Preprocessing library parsec-3.1.2... Building parsec-3.1.2... <command line>: cannot satisfy -package-id text-0.11.1.13-9b63b6813ed4eef16b7793151cdbba4d: text-0.11.1.13-9b63b6813ed4eef16b7793151cdbba4d is unusable due to missing or recursive dependencies: deepseq-1.3.0.0-a73ec930018135e0dc0a1a3d29c74c88
(use -v for more information) <command line>: cannot satisfy -package Cabal-1.14.0: Cabal-1.14.0-5875475606fe70ef919bbc055077d744 is unusable due to missing or recursive dependencies: array-0.4.0.0-59d1cc0e7979167b002f021942d60f46 containers-0.4.2.1-cfc6420ecc2194c9ed977b06bdfd9e69 directory-1.1.0.2-07820857642f1427d8b3bb49f93f97b0 process-1.1.0.1-18dadd8ad5fc640f55a7afdc7aace500 (use -v for more information) [...]
On Thu 01 Mar 2012 11:06:43 PM CET, Neil Mitchell wrote:
Hi Antoras,
I've just released Hoogle 4.2.9, which allows Cabal 1.15, so hopefully will install correctly for you.
Thanks, Neil
On Thu, Mar 1, 2012 at 5:02 PM, Neil Mitchell
wrote: Hi Antoras,
The darcs version of Hoogle has had a more permissive dependency for a few weeks. Had I realised the dependency caused problems I'd have released a new version immediately! As it stands, I'll release a new version in about 4 hours. If you can't wait that long, try darcs get http://code.haskell.org/hoogle
Thanks, Neil
On Thursday, March 1, 2012, Antoras wrote:
Ok, interesting info. But how to solve the problem now? Should I contact the author of Hoogle and ask him about how solving this?
On 03/01/2012 02:02 AM, Albert Y. C. Lai wrote:
On 12-02-29 06:04 AM, Antoras wrote:
I don't know where the dependency to array-0.3.0.3 comes from. Is it possible to get more info from cabal than -v?
hoogle-4.2.8 has "Cabal>= 1.8&& < 1.13", this brings in Cabal-1.12.0.
Cabal-1.12.0 has "array>= 0.1&& < 0.4", this brings in array-0.3.0.3.
It is a mess to have 2nd instances of libraries that already come with GHC, unless you are an expert in knowing and avoiding the treacherous consequences. See my http://www.vex.net/~trebla/haskell/sicp.xhtml
It is possible to fish the output of "cabal install --dry-run -v3 hoogle" for why array-0.3.0.3 is brought in. It really is fishing, since the output is copious and of low information density. Chinese idiom: needle in ocean (haystack is too easy). Example:
"selecting hoogle-4.2.8 (hackage) and discarding Cabal-1.1.6, 1.2.1, 1.2.2.0, 1.2.3.0, 1.2.4.0, 1.4.0.0, 1.4.0.1, 1.4.0.2, 1.6.0.1, 1.6.0.2, 1.6.0.3, 1.14.0, blaze-builder-0.1, case-insensitive-0.1,"
We see that selecting hoogle-4.2.8 causes ruling out Cabal 1.14.0
Similarly, the line for "selecting Cabal-1.12.0" mentions ruling out array-0.4.0.0
_______________________________________________ Glasgow-haskell-users mailing list Glasgow-haskell-users@haskell.org http://www.haskell.org/mailman/listinfo/glasgow-haskell-users
_______________________________________________ Glasgow-haskell-users mailing list Glasgow-haskell-users@haskell.org http://www.haskell.org/mailman/listinfo/glasgow-haskell-users

You are right. When I try to install parsec by myself I get the same error message. But neither "ghc-pkg list" nor "ghc-pkg check" prints any error messages. The latter only prints some warnings because of missing haddock files. Complete output of the error message: $cabal install parsec -v Reading available packages... Resolving dependencies... In order, the following would be installed: parsec-3.1.2 (new package) Extracting /home/antoras/.cabal/packages/hackage.haskell.org/parsec/3.1.2/parsec-3.1.2.tar.gz to /tmp/parsec-3.1.25437... Configuring parsec-3.1.2... Flags chosen: base4=True Dependency base ==4.5.0.0: using base-4.5.0.0 Dependency bytestring ==0.9.2.1: using bytestring-0.9.2.1 Dependency mtl ==2.0.1.0: using mtl-2.0.1.0 Dependency text ==0.11.1.13: using text-0.11.1.13 Using Cabal-1.10.1.0 compiled by ghc-7.0 Using compiler: ghc-7.4.1 Using install prefix: /home/antoras/.cabal Binaries installed in: /home/antoras/.cabal/bin Libraries installed in: /home/antoras/.cabal/lib/parsec-3.1.2/ghc-7.4.1 Private binaries installed in: /home/antoras/.cabal/libexec Data files installed in: /home/antoras/.cabal/share/parsec-3.1.2 Documentation installed in: /home/antoras/.cabal/share/doc/parsec-3.1.2 Using alex version 2.3.5 found on system at: /usr/bin/alex Using ar found on system at: /usr/bin/ar No c2hs found Using cpphs version 1.12 found on system at: /home/antoras/.cabal/bin/cpphs No ffihugs found Using gcc version 4.6.2 found on system at: /usr/bin/gcc Using ghc version 7.4.1 found on system at: /usr/bin/ghc Using ghc-pkg version 7.4.1 found on system at: /usr/bin/ghc-pkg No greencard found Using haddock version 2.10.0 found on system at: /usr/bin/haddock Using happy version 1.18.6 found on system at: /usr/bin/happy No hmake found Using hsc2hs version 0.67 found on system at: /usr/bin/hsc2hs Using hscolour version 1.19 found on system at: /home/antoras/.cabal/bin/HsColour No hugs found No jhc found Using ld found on system at: /usr/bin/ld No lhc found No lhc-pkg found No nhc98 found Using pkg-config version 0.26 found on system at: /usr/bin/pkg-config Using ranlib found on system at: /usr/bin/ranlib Using strip found on system at: /usr/bin/strip Using tar found on system at: /bin/tar No uhc found Creating dist/build (and its parents) Creating dist/build/autogen (and its parents) Preprocessing library parsec-3.1.2... Building parsec-3.1.2... Building library... Creating dist/build (and its parents) /usr/bin/ghc --make -package-name parsec-3.1.2 -hide-all-packages -fbuilding-cabal-package -i -idist/build -i. -idist/build/autogen -Idist/build/autogen -Idist/build -optP-include -optPdist/build/autogen/cabal_macros.h -odir dist/build -hidir dist/build -stubdir dist/build -package-id base-4.5.0.0-6db966b4cf8c1a91188e66d354ba065e -package-id bytestring-0.9.2.1-18f26186028d7c0e92e78edc9071d376 -package-id mtl-2.0.1.0-db19dd8a7700e3d3adda8aa8fe5bf53d -package-id text-0.11.1.13-9b63b6813ed4eef16b7793151cdbba4d -O -O2 -XHaskell98 -XExistentialQuantification -XPolymorphicComponents -XMultiParamTypeClasses -XFlexibleInstances -XFlexibleContexts -XDeriveDataTypeable -XCPP Text.Parsec Text.Parsec.String Text.Parsec.ByteString Text.Parsec.ByteString.Lazy Text.Parsec.Text Text.Parsec.Text.Lazy Text.Parsec.Pos Text.Parsec.Error Text.Parsec.Prim Text.Parsec.Char Text.Parsec.Combinator Text.Parsec.Token Text.Parsec.Expr Text.Parsec.Language Text.Parsec.Perm Text.ParserCombinators.Parsec Text.ParserCombinators.Parsec.Char Text.ParserCombinators.Parsec.Combinator Text.ParserCombinators.Parsec.Error Text.ParserCombinators.Parsec.Expr Text.ParserCombinators.Parsec.Language Text.ParserCombinators.Parsec.Perm Text.ParserCombinators.Parsec.Pos Text.ParserCombinators.Parsec.Prim Text.ParserCombinators.Parsec.Token <command line>: cannot satisfy -package-id text-0.11.1.13-9b63b6813ed4eef16b7793151cdbba4d: text-0.11.1.13-9b63b6813ed4eef16b7793151cdbba4d is unusable due to missing or recursive dependencies: deepseq-1.3.0.0-a73ec930018135e0dc0a1a3d29c74c88 (use -v for more information) World file is already up to date. cabal: Error: some packages failed to install: parsec-3.1.2 failed during the building phase. The exception was: ExitFailure 1 On Fri 02 Mar 2012 07:02:26 AM CET, Neil Mitchell wrote:
Hi Antoras,
My suspicion is you've ended up with corrupted packages in your package database - nothing to do with Hoogle. I suspect trying to install parsec-3.1.2 directly would give the same error message. Can you try ghc-pkg list, and at the bottom it will probably say something like:
The following packages are broken, either because they have a problem listed above, or because they depend on a broken package. warp-1.1.0
I often find ghc-pkg unregister<warp> --force on all the packages cleans them up enough, but someone else may have a better suggestion.
Thanks, Neil
On Fri, Mar 2, 2012 at 12:02 AM, Antoras
wrote: Hi Neil,
thanks for your effort. But it still does not work. The old errors disappeared, but new ones occur.
Maybe I have not yet the most current versions:
$ ghc --version The Glorious Glasgow Haskell Compilation System, version 7.4.1
$ cabal --version cabal-install version 0.10.2 using version 1.10.1.0 of the Cabal library
This seems to be the most current version of Cabal. The command 'cabal info cabal' brings: "Versions installed: 1.14.0" but not 1.15
An extract of the error messages:
[...] Configuring parsec-3.1.2... Preprocessing library parsec-3.1.2... Building parsec-3.1.2... <command line>: cannot satisfy -package-id text-0.11.1.13-9b63b6813ed4eef16b7793151cdbba4d: text-0.11.1.13-9b63b6813ed4eef16b7793151cdbba4d is unusable due to missing or recursive dependencies: deepseq-1.3.0.0-a73ec930018135e0dc0a1a3d29c74c88
(use -v for more information) <command line>: cannot satisfy -package Cabal-1.14.0: Cabal-1.14.0-5875475606fe70ef919bbc055077d744 is unusable due to missing or recursive dependencies: array-0.4.0.0-59d1cc0e7979167b002f021942d60f46 containers-0.4.2.1-cfc6420ecc2194c9ed977b06bdfd9e69 directory-1.1.0.2-07820857642f1427d8b3bb49f93f97b0 process-1.1.0.1-18dadd8ad5fc640f55a7afdc7aace500 (use -v for more information) [...]
On Thu 01 Mar 2012 11:06:43 PM CET, Neil Mitchell wrote:
Hi Antoras,
I've just released Hoogle 4.2.9, which allows Cabal 1.15, so hopefully will install correctly for you.
Thanks, Neil
On Thu, Mar 1, 2012 at 5:02 PM, Neil Mitchell
wrote: Hi Antoras,
The darcs version of Hoogle has had a more permissive dependency for a few weeks. Had I realised the dependency caused problems I'd have released a new version immediately! As it stands, I'll release a new version in about 4 hours. If you can't wait that long, try darcs get http://code.haskell.org/hoogle
Thanks, Neil
On Thursday, March 1, 2012, Antoras wrote:
Ok, interesting info. But how to solve the problem now? Should I contact the author of Hoogle and ask him about how solving this?
On 03/01/2012 02:02 AM, Albert Y. C. Lai wrote:
On 12-02-29 06:04 AM, Antoras wrote: > > > > I don't know where the dependency to array-0.3.0.3 comes from. Is it > possible to get more info from cabal than -v?
hoogle-4.2.8 has "Cabal>= 1.8&& < 1.13", this brings in Cabal-1.12.0.
Cabal-1.12.0 has "array>= 0.1&& < 0.4", this brings in array-0.3.0.3.
It is a mess to have 2nd instances of libraries that already come with GHC, unless you are an expert in knowing and avoiding the treacherous consequences. See my http://www.vex.net/~trebla/haskell/sicp.xhtml
It is possible to fish the output of "cabal install --dry-run -v3 hoogle" for why array-0.3.0.3 is brought in. It really is fishing, since the output is copious and of low information density. Chinese idiom: needle in ocean (haystack is too easy). Example:
"selecting hoogle-4.2.8 (hackage) and discarding Cabal-1.1.6, 1.2.1, 1.2.2.0, 1.2.3.0, 1.2.4.0, 1.4.0.0, 1.4.0.1, 1.4.0.2, 1.6.0.1, 1.6.0.2, 1.6.0.3, 1.14.0, blaze-builder-0.1, case-insensitive-0.1,"
We see that selecting hoogle-4.2.8 causes ruling out Cabal 1.14.0
Similarly, the line for "selecting Cabal-1.12.0" mentions ruling out array-0.4.0.0
_______________________________________________ Glasgow-haskell-users mailing list Glasgow-haskell-users@haskell.org http://www.haskell.org/mailman/listinfo/glasgow-haskell-users
_______________________________________________ Glasgow-haskell-users mailing list Glasgow-haskell-users@haskell.org http://www.haskell.org/mailman/listinfo/glasgow-haskell-users

Ok, I got Hoogle to work with GHC 7.0.3. I abandoned my try to update to the newest version of GHC, due to some other things which don't work. For example I can't import Data.Map any more. As long as these errors occur I see no reason to switch to a newer version. With Hoogle 4.2.9 I could successfully create a database and work with it. Neil, thanks for your update, once again. On 03/02/2012 07:02 AM, Neil Mitchell wrote:
Hi Antoras,
My suspicion is you've ended up with corrupted packages in your package database - nothing to do with Hoogle. I suspect trying to install parsec-3.1.2 directly would give the same error message. Can you try ghc-pkg list, and at the bottom it will probably say something like:
The following packages are broken, either because they have a problem listed above, or because they depend on a broken package. warp-1.1.0
I often find ghc-pkg unregister<warp> --force on all the packages cleans them up enough, but someone else may have a better suggestion.
Thanks, Neil
On Fri, Mar 2, 2012 at 12:02 AM, Antoras
wrote: Hi Neil,
thanks for your effort. But it still does not work. The old errors disappeared, but new ones occur.
Maybe I have not yet the most current versions:
$ ghc --version The Glorious Glasgow Haskell Compilation System, version 7.4.1
$ cabal --version cabal-install version 0.10.2 using version 1.10.1.0 of the Cabal library
This seems to be the most current version of Cabal. The command 'cabal info cabal' brings: "Versions installed: 1.14.0" but not 1.15
An extract of the error messages:
[...] Configuring parsec-3.1.2... Preprocessing library parsec-3.1.2... Building parsec-3.1.2... <command line>: cannot satisfy -package-id text-0.11.1.13-9b63b6813ed4eef16b7793151cdbba4d: text-0.11.1.13-9b63b6813ed4eef16b7793151cdbba4d is unusable due to missing or recursive dependencies: deepseq-1.3.0.0-a73ec930018135e0dc0a1a3d29c74c88
(use -v for more information) <command line>: cannot satisfy -package Cabal-1.14.0: Cabal-1.14.0-5875475606fe70ef919bbc055077d744 is unusable due to missing or recursive dependencies: array-0.4.0.0-59d1cc0e7979167b002f021942d60f46 containers-0.4.2.1-cfc6420ecc2194c9ed977b06bdfd9e69 directory-1.1.0.2-07820857642f1427d8b3bb49f93f97b0 process-1.1.0.1-18dadd8ad5fc640f55a7afdc7aace500 (use -v for more information) [...]
On Thu 01 Mar 2012 11:06:43 PM CET, Neil Mitchell wrote:
Hi Antoras,
I've just released Hoogle 4.2.9, which allows Cabal 1.15, so hopefully will install correctly for you.
Thanks, Neil
On Thu, Mar 1, 2012 at 5:02 PM, Neil Mitchell
wrote: Hi Antoras,
The darcs version of Hoogle has had a more permissive dependency for a few weeks. Had I realised the dependency caused problems I'd have released a new version immediately! As it stands, I'll release a new version in about 4 hours. If you can't wait that long, try darcs get http://code.haskell.org/hoogle
Thanks, Neil
On Thursday, March 1, 2012, Antoras wrote:
Ok, interesting info. But how to solve the problem now? Should I contact the author of Hoogle and ask him about how solving this?
On 03/01/2012 02:02 AM, Albert Y. C. Lai wrote:
On 12-02-29 06:04 AM, Antoras wrote: > > I don't know where the dependency to array-0.3.0.3 comes from. Is it > possible to get more info from cabal than -v?
hoogle-4.2.8 has "Cabal>= 1.8&& < 1.13", this brings in Cabal-1.12.0.
Cabal-1.12.0 has "array>= 0.1&& < 0.4", this brings in array-0.3.0.3.
It is a mess to have 2nd instances of libraries that already come with GHC, unless you are an expert in knowing and avoiding the treacherous consequences. See my http://www.vex.net/~trebla/haskell/sicp.xhtml
It is possible to fish the output of "cabal install --dry-run -v3 hoogle" for why array-0.3.0.3 is brought in. It really is fishing, since the output is copious and of low information density. Chinese idiom: needle in ocean (haystack is too easy). Example:
"selecting hoogle-4.2.8 (hackage) and discarding Cabal-1.1.6, 1.2.1, 1.2.2.0, 1.2.3.0, 1.2.4.0, 1.4.0.0, 1.4.0.1, 1.4.0.2, 1.6.0.1, 1.6.0.2, 1.6.0.3, 1.14.0, blaze-builder-0.1, case-insensitive-0.1,"
We see that selecting hoogle-4.2.8 causes ruling out Cabal 1.14.0
Similarly, the line for "selecting Cabal-1.12.0" mentions ruling out array-0.4.0.0
_______________________________________________ Glasgow-haskell-users mailing list Glasgow-haskell-users@haskell.org http://www.haskell.org/mailman/listinfo/glasgow-haskell-users
_______________________________________________ Glasgow-haskell-users mailing list Glasgow-haskell-users@haskell.org http://www.haskell.org/mailman/listinfo/glasgow-haskell-users
participants (2)
-
Antoras
-
Neil Mitchell