errors while installing yesod 0.8

Trying to install yesod 0.8 breaks when it's time to install monad-control. Google wasn't very helpful, nor was the error message I received mlitchard@apotheosis:~/monad-control$ cabal install Resolving dependencies... Configuring monad-control-0.2.0.1... cabal: Error: some packages failed to install: monad-control-0.2.0.1 failed during the configure step. The exception was: ExitFailure 11 note: I've been trying to use the cab command to manage my packages, I get the same error as above when I use cab instead of cabal.I mention this just in case there is some unforseen problem having to do with cab/cabal interaction. Has anyone experienced this problem, or know what I can do to get more useful error messages that might reveal the cause of the breakage?

I haven't seen this error. What version of GHC are you using, and what OS?
Michael
On Wed, Apr 20, 2011 at 12:18 AM, Michael Litchard
Trying to install yesod 0.8 breaks when it's time to install monad-control. Google wasn't very helpful, nor was the error message I received
mlitchard@apotheosis:~/monad-control$ cabal install Resolving dependencies... Configuring monad-control-0.2.0.1... cabal: Error: some packages failed to install: monad-control-0.2.0.1 failed during the configure step. The exception was: ExitFailure 11
note: I've been trying to use the cab command to manage my packages, I get the same error as above when I use cab instead of cabal.I mention this just in case there is some unforseen problem having to do with cab/cabal interaction.
Has anyone experienced this problem, or know what I can do to get more useful error messages that might reveal the cause of the breakage?
_______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe

OS
Linux apotheosis 2.6.35-22-server #33-Ubuntu SMP Sun Sep 19 20:48:58
UTC 2010 x86_64 GNU/Linux
GHC
The Glorious Glasgow Haskell Compilation System, version 6.12.3
Is the problem here that I'm not using ghc 7? I try to be conservative
with my compiler upgrades. But if this might be the problem it seems
like a simple enough fix.
On Tue, Apr 19, 2011 at 2:41 PM, Michael Snoyman
I haven't seen this error. What version of GHC are you using, and what OS? Michael
On Wed, Apr 20, 2011 at 12:18 AM, Michael Litchard
wrote: Trying to install yesod 0.8 breaks when it's time to install monad-control. Google wasn't very helpful, nor was the error message I received
mlitchard@apotheosis:~/monad-control$ cabal install Resolving dependencies... Configuring monad-control-0.2.0.1... cabal: Error: some packages failed to install: monad-control-0.2.0.1 failed during the configure step. The exception was: ExitFailure 11
note: I've been trying to use the cab command to manage my packages, I get the same error as above when I use cab instead of cabal.I mention this just in case there is some unforseen problem having to do with cab/cabal interaction.
Has anyone experienced this problem, or know what I can do to get more useful error messages that might reveal the cause of the breakage?
_______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe

monad-control builds fine on my system with both GHC 7.0.3 and 6.12.3.
$ uname -a
Linux notebookbas 2.6.38-8-generic #42-Ubuntu SMP Mon Apr 11 03:31:24
UTC 2011 x86_64 x86_64 x86_64 GNU/Linux
I do get some "Unrecognised pragma" warnings when building on 6.12.3
because I use the new INLINABLE pragma for a bunch of functions. Maybe
I can add some CPP magic to only enable that when building on GHC-7.
Regards,
Bas
On 19 April 2011 23:52, Michael Litchard
OS Linux apotheosis 2.6.35-22-server #33-Ubuntu SMP Sun Sep 19 20:48:58 UTC 2010 x86_64 GNU/Linux
GHC
The Glorious Glasgow Haskell Compilation System, version 6.12.3
Is the problem here that I'm not using ghc 7? I try to be conservative with my compiler upgrades. But if this might be the problem it seems like a simple enough fix.
On Tue, Apr 19, 2011 at 2:41 PM, Michael Snoyman
wrote: I haven't seen this error. What version of GHC are you using, and what OS? Michael
On Wed, Apr 20, 2011 at 12:18 AM, Michael Litchard
wrote: Trying to install yesod 0.8 breaks when it's time to install monad-control. Google wasn't very helpful, nor was the error message I received
mlitchard@apotheosis:~/monad-control$ cabal install Resolving dependencies... Configuring monad-control-0.2.0.1... cabal: Error: some packages failed to install: monad-control-0.2.0.1 failed during the configure step. The exception was: ExitFailure 11
note: I've been trying to use the cab command to manage my packages, I get the same error as above when I use cab instead of cabal.I mention this just in case there is some unforseen problem having to do with cab/cabal interaction.
Has anyone experienced this problem, or know what I can do to get more useful error messages that might reveal the cause of the breakage?
_______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe
_______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe

I got those warnings as well, but I don't think it's anything to be
particularly concerned about.
On Wed, Apr 20, 2011 at 8:58 AM, Bas van Dijk
monad-control builds fine on my system with both GHC 7.0.3 and 6.12.3.
$ uname -a Linux notebookbas 2.6.38-8-generic #42-Ubuntu SMP Mon Apr 11 03:31:24 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux
I do get some "Unrecognised pragma" warnings when building on 6.12.3 because I use the new INLINABLE pragma for a bunch of functions. Maybe I can add some CPP magic to only enable that when building on GHC-7.
Regards,
Bas
On 19 April 2011 23:52, Michael Litchard
wrote: OS Linux apotheosis 2.6.35-22-server #33-Ubuntu SMP Sun Sep 19 20:48:58 UTC 2010 x86_64 GNU/Linux
GHC
The Glorious Glasgow Haskell Compilation System, version 6.12.3
Is the problem here that I'm not using ghc 7? I try to be conservative with my compiler upgrades. But if this might be the problem it seems like a simple enough fix.
On Tue, Apr 19, 2011 at 2:41 PM, Michael Snoyman
wrote: I haven't seen this error. What version of GHC are you using, and what OS? Michael
On Wed, Apr 20, 2011 at 12:18 AM, Michael Litchard
wrote:
Trying to install yesod 0.8 breaks when it's time to install monad-control. Google wasn't very helpful, nor was the error message I received
mlitchard@apotheosis:~/monad-control$ cabal install Resolving dependencies... Configuring monad-control-0.2.0.1... cabal: Error: some packages failed to install: monad-control-0.2.0.1 failed during the configure step. The exception
was:
ExitFailure 11
note: I've been trying to use the cab command to manage my packages, I get the same error as above when I use cab instead of cabal.I mention this just in case there is some unforseen problem having to do with cab/cabal interaction.
Has anyone experienced this problem, or know what I can do to get more useful error messages that might reveal the cause of the breakage?
_______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe
_______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe

On Tue, Apr 19, 2011 at 2:18 PM, Michael Litchard
mlitchard@apotheosis:~/monad-control$ cabal install Resolving dependencies... Configuring monad-control-0.2.0.1... cabal: Error: some packages failed to install: monad-control-0.2.0.1 failed during the configure step. The exception was: ExitFailure 11
note: I've been trying to use the cab command to manage my packages, I get the same error as above when I use cab instead of cabal.I mention this just in case there is some unforseen problem having to do with cab/cabal interaction.
Has anyone experienced this problem, or know what I can do to get more useful error messages that might reveal the cause of the breakage?
You might learn more by issuing the configure / build steps manually (I think `cabal configure` will produce an error). Upping the verbosity will also help: # get pages and pages of details: $ cabal install --verbose=3 I would first suggest trying cabal-dev, though (cab can delegate to cabal-dev now too, but I haven't played with it yet). $ cabal-dev install yesod-0.8 will either work or fail in a way that we can more easily reproduce. --Rogan

New information, may be helpful.
I manually installed hamlet 0.8 with cabal-dev, and it seemed to
install. Here is the message
Registering hamlet-0.8.0...
Installing library in
/home/mlitchard/hamlet-0.8.0/cabal-dev//lib/hamlet-0.8.0/ghc-6.12.3
Registering hamlet-0.8.0...
Then I tried to manually install yesod. Here's what I got.
mlitchard@apotheosis:~$ cd yesod-0.8.0/
mlitchard@apotheosis:~/yesod-0.8.0$ cabal-dev install
Resolving dependencies...
cabal: cannot configure yesod-0.8.0. It requires hamlet ==0.8.*
There is no available version of hamlet that satisfies ==0.8.*
I noticed it did not install in the $HOME/.cabal/ path. How do make
sure it does that?
I think if I can get it to install in the right place this will work out.
On Tue, Apr 19, 2011 at 2:52 PM, Rogan Creswick
On Tue, Apr 19, 2011 at 2:18 PM, Michael Litchard
wrote: mlitchard@apotheosis:~/monad-control$ cabal install Resolving dependencies... Configuring monad-control-0.2.0.1... cabal: Error: some packages failed to install: monad-control-0.2.0.1 failed during the configure step. The exception was: ExitFailure 11
note: I've been trying to use the cab command to manage my packages, I get the same error as above when I use cab instead of cabal.I mention this just in case there is some unforseen problem having to do with cab/cabal interaction.
Has anyone experienced this problem, or know what I can do to get more useful error messages that might reveal the cause of the breakage?
You might learn more by issuing the configure / build steps manually (I think `cabal configure` will produce an error). Upping the verbosity will also help:
# get pages and pages of details: $ cabal install --verbose=3
I would first suggest trying cabal-dev, though (cab can delegate to cabal-dev now too, but I haven't played with it yet).
$ cabal-dev install yesod-0.8
will either work or fail in a way that we can more easily reproduce.
--Rogan

On Tue, Apr 19, 2011 at 3:10 PM, Michael Litchard
New information, may be helpful.
I manually installed hamlet 0.8 with cabal-dev, and it seemed to install. Here is the message
Registering hamlet-0.8.0... Installing library in /home/mlitchard/hamlet-0.8.0/cabal-dev//lib/hamlet-0.8.0/ghc-6.12.3 Registering hamlet-0.8.0...
It looks like you manually downloaded the hamlet-0.8.0.tar.gz, unpacked it, and ran cabal-dev install from inside there -- is that right? (There's nothing wrong with doing it that way, but it doesn't quite do what you expected, based on the rest of your email. Also, if my assumption is wrong, then the rest of my advice may not help.) First, it's important to know that cabal-dev sandboxes everything it can. If you want to install hamlet into your .cabal directory, then you need to use cabal, not cabal-dev. Cabal-dev is meant to keep everything for a given project separate from everything else -- in this way you can have multiple projects that depend on conflicting libraries building at the same time, and it also means that coincidental changes to your user package database won't cause spurious *successes* when you build something, which is a surprisingly common problem. Unfortunately this means that the first time you build a project with cabal-dev, it tends to take a long time (it has to build everything it depends on). Now, there are (at least) two important take-away points / implications of using cabal-dev: (1) cabal-dev won't install a library into a standard location. That's by design, so you don't usually want to cabal-dev install dependencies manually. (2) cabal-dev uses the local hackage cache to select packages in the same way cabal does (cabal-dev actually just uses cabal to do this).
mlitchard@apotheosis:~/yesod-0.8.0$ cabal-dev install Resolving dependencies... cabal: cannot configure yesod-0.8.0. It requires hamlet ==0.8.* There is no available version of hamlet that satisfies ==0.8.*
I think you just need to run 'cabal update' so cabal-dev can see the latest version of hamlet, after which you can cabal-dev install yesod. There are a couple other things to try if that doesn't work for some reason. --Rogan
I noticed it did not install in the $HOME/.cabal/ path. How do make sure it does that? I think if I can get it to install in the right place this will work out.
On Tue, Apr 19, 2011 at 2:52 PM, Rogan Creswick
wrote: On Tue, Apr 19, 2011 at 2:18 PM, Michael Litchard
wrote: mlitchard@apotheosis:~/monad-control$ cabal install Resolving dependencies... Configuring monad-control-0.2.0.1... cabal: Error: some packages failed to install: monad-control-0.2.0.1 failed during the configure step. The exception was: ExitFailure 11
note: I've been trying to use the cab command to manage my packages, I get the same error as above when I use cab instead of cabal.I mention this just in case there is some unforseen problem having to do with cab/cabal interaction.
Has anyone experienced this problem, or know what I can do to get more useful error messages that might reveal the cause of the breakage?
You might learn more by issuing the configure / build steps manually (I think `cabal configure` will produce an error). Upping the verbosity will also help:
# get pages and pages of details: $ cabal install --verbose=3
I would first suggest trying cabal-dev, though (cab can delegate to cabal-dev now too, but I haven't played with it yet).
$ cabal-dev install yesod-0.8
will either work or fail in a way that we can more easily reproduce.
--Rogan

yesod-0.8.0 depends on monad-control-0.2.0.1 which failed to install.
yesod-auth-0.4.0 depends on monad-control-0.2.0.1 which failed to install.
yesod-core-0.8.0 depends on monad-control-0.2.0.1 which failed to install.
yesod-form-0.1.0 depends on monad-control-0.2.0.1 which failed to install.
yesod-json-0.1.0 depends on monad-control-0.2.0.1 which failed to install.
yesod-persistent-0.1.0 depends on monad-control-0.2.0.1 which failed to
install.
yesod-static-0.1.0 depends on monad-control-0.2.0.1 which failed to install.
This is what happened after I did cabal update, then cabal-dev install
yesod. This is the original error I received.
So what else can I try?
On Tue, Apr 19, 2011 at 3:30 PM, Rogan Creswick
On Tue, Apr 19, 2011 at 3:10 PM, Michael Litchard
wrote: New information, may be helpful.
I manually installed hamlet 0.8 with cabal-dev, and it seemed to install. Here is the message
Registering hamlet-0.8.0... Installing library in /home/mlitchard/hamlet-0.8.0/cabal-dev//lib/hamlet-0.8.0/ghc-6.12.3 Registering hamlet-0.8.0...
It looks like you manually downloaded the hamlet-0.8.0.tar.gz, unpacked it, and ran cabal-dev install from inside there -- is that right? (There's nothing wrong with doing it that way, but it doesn't quite do what you expected, based on the rest of your email. Also, if my assumption is wrong, then the rest of my advice may not help.)
First, it's important to know that cabal-dev sandboxes everything it can. If you want to install hamlet into your .cabal directory, then you need to use cabal, not cabal-dev. Cabal-dev is meant to keep everything for a given project separate from everything else -- in this way you can have multiple projects that depend on conflicting libraries building at the same time, and it also means that coincidental changes to your user package database won't cause spurious *successes* when you build something, which is a surprisingly common problem. Unfortunately this means that the first time you build a project with cabal-dev, it tends to take a long time (it has to build everything it depends on).
Now, there are (at least) two important take-away points / implications of using cabal-dev:
(1) cabal-dev won't install a library into a standard location. That's by design, so you don't usually want to cabal-dev install dependencies manually. (2) cabal-dev uses the local hackage cache to select packages in the same way cabal does (cabal-dev actually just uses cabal to do this).
mlitchard@apotheosis:~/yesod-0.8.0$ cabal-dev install Resolving dependencies... cabal: cannot configure yesod-0.8.0. It requires hamlet ==0.8.* There is no available version of hamlet that satisfies ==0.8.*
I think you just need to run 'cabal update' so cabal-dev can see the latest version of hamlet, after which you can cabal-dev install yesod.
There are a couple other things to try if that doesn't work for some reason.
--Rogan
I noticed it did not install in the $HOME/.cabal/ path. How do make sure it does that? I think if I can get it to install in the right place this will work out.
On Tue, Apr 19, 2011 at 2:52 PM, Rogan Creswick
wrote: On Tue, Apr 19, 2011 at 2:18 PM, Michael Litchard
wrote: mlitchard@apotheosis:~/monad-control$ cabal install Resolving dependencies... Configuring monad-control-0.2.0.1... cabal: Error: some packages failed to install: monad-control-0.2.0.1 failed during the configure step. The exception was: ExitFailure 11
note: I've been trying to use the cab command to manage my packages, I get the same error as above when I use cab instead of cabal.I mention this just in case there is some unforseen problem having to do with cab/cabal interaction.
Has anyone experienced this problem, or know what I can do to get more useful error messages that might reveal the cause of the breakage?
You might learn more by issuing the configure / build steps manually (I think `cabal configure` will produce an error). Upping the verbosity will also help:
# get pages and pages of details: $ cabal install --verbose=3
I would first suggest trying cabal-dev, though (cab can delegate to cabal-dev now too, but I haven't played with it yet).
$ cabal-dev install yesod-0.8
will either work or fail in a way that we can more easily reproduce.
--Rogan

I started mindlessly pasting in the output, and the following lept out at me:
,
package authenticate-0.8.2.2-cc3ed2c523ecbf1ad123c3468785149e is
unusable due to missing or recursive dependencies:
http-enumerator-0.3.1-719bcd77e1dcb62efc9cf9b4f0b72271
package http-enumerator-0.3.1-719bcd77e1dcb62efc9cf9b4f0b72271 is
unusable due to missing or recursive dependencies:
attoparsec-enumerator-0.2.0.3-4978ab2dc4d87b7b724534bbfdcb07f1
package json-enumerator-0.0.1-7d4b724ae8c9b5ffa92da26856c4e1f1 is
unusable due to missing or recursive dependencies:
blaze-builder-enumerator-0.2.0.1-23e6e1f270358d3329f627e3a5ce8838
package wai-extra-0.3.2-f8378ad4a5cc6f375d96b718876384fa is unusable
due to missing or recursive dependencies:
There's more of the same I'm leaving out.
I'm going to see if I can go somewhere with these error messages. If I
totally hose things, I'll let you guys know.
On Tue, Apr 19, 2011 at 4:45 PM, Daniel Fischer
On Wednesday 20 April 2011 01:22:20, Michael Litchard wrote:
So what else can I try?
$ cabal install -v3 monad-control
That should give some hints at which point exactly things fail.

Following the install trail I run into this problem
mlitchard@apotheosis:~$ cab install JSONb-1.0.2
Resolving dependencies...
Configuring JSONb-1.0.2...
Preprocessing library JSONb-1.0.2...
Preprocessing executables for JSONb-1.0.2...
Building JSONb-1.0.2...
[1 of 7] Compiling Text.JSON.Escape ( Text/JSON/Escape.hs,
dist/build/Text/JSON/Escape.o )
[2 of 7] Compiling Text.JSONb.Simple ( Text/JSONb/Simple.hs,
dist/build/Text/JSONb/Simple.o )
[3 of 7] Compiling Text.JSONb.Decode ( Text/JSONb/Decode.hs,
dist/build/Text/JSONb/Decode.o )
Text/JSONb/Decode.hs:56:33:
Ambiguous occurrence `number'
It could refer to either `Text.JSONb.Decode.number', defined at
Text/JSONb/Decode.hs:118:0
or `Attoparsec.number', imported from
Data.Attoparsec.Char8 at Text/JSONb/Decode.hs:25:0-52
cabal: Error: some packages failed to install:
JSONb-1.0.2 failed during the building phase. The exception was:
ExitFailure 1
How do I clear up this ambiguity?
On Mon, Apr 25, 2011 at 1:24 PM, Michael Litchard
I started mindlessly pasting in the output, and the following lept out at me:
,
package authenticate-0.8.2.2-cc3ed2c523ecbf1ad123c3468785149e is unusable due to missing or recursive dependencies: http-enumerator-0.3.1-719bcd77e1dcb62efc9cf9b4f0b72271 package http-enumerator-0.3.1-719bcd77e1dcb62efc9cf9b4f0b72271 is unusable due to missing or recursive dependencies: attoparsec-enumerator-0.2.0.3-4978ab2dc4d87b7b724534bbfdcb07f1 package json-enumerator-0.0.1-7d4b724ae8c9b5ffa92da26856c4e1f1 is unusable due to missing or recursive dependencies: blaze-builder-enumerator-0.2.0.1-23e6e1f270358d3329f627e3a5ce8838 package wai-extra-0.3.2-f8378ad4a5cc6f375d96b718876384fa is unusable due to missing or recursive dependencies:
There's more of the same I'm leaving out.
I'm going to see if I can go somewhere with these error messages. If I totally hose things, I'll let you guys know.
On Tue, Apr 19, 2011 at 4:45 PM, Daniel Fischer
wrote: On Wednesday 20 April 2011 01:22:20, Michael Litchard wrote:
So what else can I try?
$ cabal install -v3 monad-control
That should give some hints at which point exactly things fail.

So it appears this is a bug with JSONb-1.0.2. There's a new version
out. IS the answer to use that, or to patch this version?
On Mon, Apr 25, 2011 at 1:48 PM, Michael Litchard
Following the install trail I run into this problem
mlitchard@apotheosis:~$ cab install JSONb-1.0.2 Resolving dependencies... Configuring JSONb-1.0.2... Preprocessing library JSONb-1.0.2... Preprocessing executables for JSONb-1.0.2... Building JSONb-1.0.2... [1 of 7] Compiling Text.JSON.Escape ( Text/JSON/Escape.hs, dist/build/Text/JSON/Escape.o ) [2 of 7] Compiling Text.JSONb.Simple ( Text/JSONb/Simple.hs, dist/build/Text/JSONb/Simple.o ) [3 of 7] Compiling Text.JSONb.Decode ( Text/JSONb/Decode.hs, dist/build/Text/JSONb/Decode.o )
Text/JSONb/Decode.hs:56:33: Ambiguous occurrence `number' It could refer to either `Text.JSONb.Decode.number', defined at Text/JSONb/Decode.hs:118:0 or `Attoparsec.number', imported from Data.Attoparsec.Char8 at Text/JSONb/Decode.hs:25:0-52 cabal: Error: some packages failed to install: JSONb-1.0.2 failed during the building phase. The exception was: ExitFailure 1
How do I clear up this ambiguity?
On Mon, Apr 25, 2011 at 1:24 PM, Michael Litchard
wrote: I started mindlessly pasting in the output, and the following lept out at me:
,
package authenticate-0.8.2.2-cc3ed2c523ecbf1ad123c3468785149e is unusable due to missing or recursive dependencies: http-enumerator-0.3.1-719bcd77e1dcb62efc9cf9b4f0b72271 package http-enumerator-0.3.1-719bcd77e1dcb62efc9cf9b4f0b72271 is unusable due to missing or recursive dependencies: attoparsec-enumerator-0.2.0.3-4978ab2dc4d87b7b724534bbfdcb07f1 package json-enumerator-0.0.1-7d4b724ae8c9b5ffa92da26856c4e1f1 is unusable due to missing or recursive dependencies: blaze-builder-enumerator-0.2.0.1-23e6e1f270358d3329f627e3a5ce8838 package wai-extra-0.3.2-f8378ad4a5cc6f375d96b718876384fa is unusable due to missing or recursive dependencies:
There's more of the same I'm leaving out.
I'm going to see if I can go somewhere with these error messages. If I totally hose things, I'll let you guys know.
On Tue, Apr 19, 2011 at 4:45 PM, Daniel Fischer
wrote: On Wednesday 20 April 2011 01:22:20, Michael Litchard wrote:
So what else can I try?
$ cabal install -v3 monad-control
That should give some hints at which point exactly things fail.

On Mon, Apr 25, 2011 at 2:44 PM, Michael Litchard
So it appears this is a bug with JSONb-1.0.2. There's a new version out. IS the answer to use that, or to patch this version?
If there is a new version, and you indeed need JSONb for something, then you should use the newer version (yesod doesn't depend on it, so I'm a bit unsure why it came up...). --Rogan
On Mon, Apr 25, 2011 at 1:48 PM, Michael Litchard
wrote: Following the install trail I run into this problem
mlitchard@apotheosis:~$ cab install JSONb-1.0.2 Resolving dependencies... Configuring JSONb-1.0.2... Preprocessing library JSONb-1.0.2... Preprocessing executables for JSONb-1.0.2... Building JSONb-1.0.2... [1 of 7] Compiling Text.JSON.Escape ( Text/JSON/Escape.hs, dist/build/Text/JSON/Escape.o ) [2 of 7] Compiling Text.JSONb.Simple ( Text/JSONb/Simple.hs, dist/build/Text/JSONb/Simple.o ) [3 of 7] Compiling Text.JSONb.Decode ( Text/JSONb/Decode.hs, dist/build/Text/JSONb/Decode.o )
Text/JSONb/Decode.hs:56:33: Ambiguous occurrence `number' It could refer to either `Text.JSONb.Decode.number', defined at Text/JSONb/Decode.hs:118:0 or `Attoparsec.number', imported from Data.Attoparsec.Char8 at Text/JSONb/Decode.hs:25:0-52 cabal: Error: some packages failed to install: JSONb-1.0.2 failed during the building phase. The exception was: ExitFailure 1
How do I clear up this ambiguity?
On Mon, Apr 25, 2011 at 1:24 PM, Michael Litchard
wrote: I started mindlessly pasting in the output, and the following lept out at me:
,
package authenticate-0.8.2.2-cc3ed2c523ecbf1ad123c3468785149e is unusable due to missing or recursive dependencies: http-enumerator-0.3.1-719bcd77e1dcb62efc9cf9b4f0b72271 package http-enumerator-0.3.1-719bcd77e1dcb62efc9cf9b4f0b72271 is unusable due to missing or recursive dependencies: attoparsec-enumerator-0.2.0.3-4978ab2dc4d87b7b724534bbfdcb07f1 package json-enumerator-0.0.1-7d4b724ae8c9b5ffa92da26856c4e1f1 is unusable due to missing or recursive dependencies: blaze-builder-enumerator-0.2.0.1-23e6e1f270358d3329f627e3a5ce8838 package wai-extra-0.3.2-f8378ad4a5cc6f375d96b718876384fa is unusable due to missing or recursive dependencies:
There's more of the same I'm leaving out.
I'm going to see if I can go somewhere with these error messages. If I totally hose things, I'll let you guys know.
On Tue, Apr 19, 2011 at 4:45 PM, Daniel Fischer
wrote: On Wednesday 20 April 2011 01:22:20, Michael Litchard wrote:
So what else can I try?
$ cabal install -v3 monad-control
That should give some hints at which point exactly things fail.
_______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe

I think something that yesod uses, uses JSONb. Also, I think I have
borked my haskell environment to the point where it may be best to
zap it and start over.
On Mon, Apr 25, 2011 at 3:05 PM, Rogan Creswick
On Mon, Apr 25, 2011 at 2:44 PM, Michael Litchard
wrote: So it appears this is a bug with JSONb-1.0.2. There's a new version out. IS the answer to use that, or to patch this version?
If there is a new version, and you indeed need JSONb for something, then you should use the newer version (yesod doesn't depend on it, so I'm a bit unsure why it came up...).
--Rogan
On Mon, Apr 25, 2011 at 1:48 PM, Michael Litchard
wrote: Following the install trail I run into this problem
mlitchard@apotheosis:~$ cab install JSONb-1.0.2 Resolving dependencies... Configuring JSONb-1.0.2... Preprocessing library JSONb-1.0.2... Preprocessing executables for JSONb-1.0.2... Building JSONb-1.0.2... [1 of 7] Compiling Text.JSON.Escape ( Text/JSON/Escape.hs, dist/build/Text/JSON/Escape.o ) [2 of 7] Compiling Text.JSONb.Simple ( Text/JSONb/Simple.hs, dist/build/Text/JSONb/Simple.o ) [3 of 7] Compiling Text.JSONb.Decode ( Text/JSONb/Decode.hs, dist/build/Text/JSONb/Decode.o )
Text/JSONb/Decode.hs:56:33: Ambiguous occurrence `number' It could refer to either `Text.JSONb.Decode.number', defined at Text/JSONb/Decode.hs:118:0 or `Attoparsec.number', imported from Data.Attoparsec.Char8 at Text/JSONb/Decode.hs:25:0-52 cabal: Error: some packages failed to install: JSONb-1.0.2 failed during the building phase. The exception was: ExitFailure 1
How do I clear up this ambiguity?
On Mon, Apr 25, 2011 at 1:24 PM, Michael Litchard
wrote: I started mindlessly pasting in the output, and the following lept out at me:
,
package authenticate-0.8.2.2-cc3ed2c523ecbf1ad123c3468785149e is unusable due to missing or recursive dependencies: http-enumerator-0.3.1-719bcd77e1dcb62efc9cf9b4f0b72271 package http-enumerator-0.3.1-719bcd77e1dcb62efc9cf9b4f0b72271 is unusable due to missing or recursive dependencies: attoparsec-enumerator-0.2.0.3-4978ab2dc4d87b7b724534bbfdcb07f1 package json-enumerator-0.0.1-7d4b724ae8c9b5ffa92da26856c4e1f1 is unusable due to missing or recursive dependencies: blaze-builder-enumerator-0.2.0.1-23e6e1f270358d3329f627e3a5ce8838 package wai-extra-0.3.2-f8378ad4a5cc6f375d96b718876384fa is unusable due to missing or recursive dependencies:
There's more of the same I'm leaving out.
I'm going to see if I can go somewhere with these error messages. If I totally hose things, I'll let you guys know.
On Tue, Apr 19, 2011 at 4:45 PM, Daniel Fischer
wrote: On Wednesday 20 April 2011 01:22:20, Michael Litchard wrote:
So what else can I try?
$ cabal install -v3 monad-control
That should give some hints at which point exactly things fail.
_______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe

Oh yeah, this began while trying to install by hand
authenticate-0.8.2.2
On Mon, Apr 25, 2011 at 3:10 PM, Michael Litchard
I think something that yesod uses, uses JSONb. Also, I think I have borked my haskell environment to the point where it may be best to zap it and start over.
On Mon, Apr 25, 2011 at 3:05 PM, Rogan Creswick
wrote: On Mon, Apr 25, 2011 at 2:44 PM, Michael Litchard
wrote: So it appears this is a bug with JSONb-1.0.2. There's a new version out. IS the answer to use that, or to patch this version?
If there is a new version, and you indeed need JSONb for something, then you should use the newer version (yesod doesn't depend on it, so I'm a bit unsure why it came up...).
--Rogan
On Mon, Apr 25, 2011 at 1:48 PM, Michael Litchard
wrote: Following the install trail I run into this problem
mlitchard@apotheosis:~$ cab install JSONb-1.0.2 Resolving dependencies... Configuring JSONb-1.0.2... Preprocessing library JSONb-1.0.2... Preprocessing executables for JSONb-1.0.2... Building JSONb-1.0.2... [1 of 7] Compiling Text.JSON.Escape ( Text/JSON/Escape.hs, dist/build/Text/JSON/Escape.o ) [2 of 7] Compiling Text.JSONb.Simple ( Text/JSONb/Simple.hs, dist/build/Text/JSONb/Simple.o ) [3 of 7] Compiling Text.JSONb.Decode ( Text/JSONb/Decode.hs, dist/build/Text/JSONb/Decode.o )
Text/JSONb/Decode.hs:56:33: Ambiguous occurrence `number' It could refer to either `Text.JSONb.Decode.number', defined at Text/JSONb/Decode.hs:118:0 or `Attoparsec.number', imported from Data.Attoparsec.Char8 at Text/JSONb/Decode.hs:25:0-52 cabal: Error: some packages failed to install: JSONb-1.0.2 failed during the building phase. The exception was: ExitFailure 1
How do I clear up this ambiguity?
On Mon, Apr 25, 2011 at 1:24 PM, Michael Litchard
wrote: I started mindlessly pasting in the output, and the following lept out at me:
,
package authenticate-0.8.2.2-cc3ed2c523ecbf1ad123c3468785149e is unusable due to missing or recursive dependencies: http-enumerator-0.3.1-719bcd77e1dcb62efc9cf9b4f0b72271 package http-enumerator-0.3.1-719bcd77e1dcb62efc9cf9b4f0b72271 is unusable due to missing or recursive dependencies: attoparsec-enumerator-0.2.0.3-4978ab2dc4d87b7b724534bbfdcb07f1 package json-enumerator-0.0.1-7d4b724ae8c9b5ffa92da26856c4e1f1 is unusable due to missing or recursive dependencies: blaze-builder-enumerator-0.2.0.1-23e6e1f270358d3329f627e3a5ce8838 package wai-extra-0.3.2-f8378ad4a5cc6f375d96b718876384fa is unusable due to missing or recursive dependencies:
There's more of the same I'm leaving out.
I'm going to see if I can go somewhere with these error messages. If I totally hose things, I'll let you guys know.
On Tue, Apr 19, 2011 at 4:45 PM, Daniel Fischer
wrote: On Wednesday 20 April 2011 01:22:20, Michael Litchard wrote: > So what else can I try?
$ cabal install -v3 monad-control
That should give some hints at which point exactly things fail.
_______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe

On Mon, Apr 25, 2011 at 3:10 PM, Michael Litchard
I think something that yesod uses, uses JSONb.
Odd. I just checked the transitive dependencies of yesod-0.8.0 (with cab) and it doesn't seem to have that dependency. It could be system-specific, though. It would be nice to figure out what is depending on that version of JSONb so we could better determine if upgrading will break anything. --Rogan
Also, I think I have borked my haskell environment to the point where it may be best to zap it and start over.
On Mon, Apr 25, 2011 at 3:05 PM, Rogan Creswick
wrote: On Mon, Apr 25, 2011 at 2:44 PM, Michael Litchard
wrote: So it appears this is a bug with JSONb-1.0.2. There's a new version out. IS the answer to use that, or to patch this version?
If there is a new version, and you indeed need JSONb for something, then you should use the newer version (yesod doesn't depend on it, so I'm a bit unsure why it came up...).
--Rogan
On Mon, Apr 25, 2011 at 1:48 PM, Michael Litchard
wrote: Following the install trail I run into this problem
mlitchard@apotheosis:~$ cab install JSONb-1.0.2 Resolving dependencies... Configuring JSONb-1.0.2... Preprocessing library JSONb-1.0.2... Preprocessing executables for JSONb-1.0.2... Building JSONb-1.0.2... [1 of 7] Compiling Text.JSON.Escape ( Text/JSON/Escape.hs, dist/build/Text/JSON/Escape.o ) [2 of 7] Compiling Text.JSONb.Simple ( Text/JSONb/Simple.hs, dist/build/Text/JSONb/Simple.o ) [3 of 7] Compiling Text.JSONb.Decode ( Text/JSONb/Decode.hs, dist/build/Text/JSONb/Decode.o )
Text/JSONb/Decode.hs:56:33: Ambiguous occurrence `number' It could refer to either `Text.JSONb.Decode.number', defined at Text/JSONb/Decode.hs:118:0 or `Attoparsec.number', imported from Data.Attoparsec.Char8 at Text/JSONb/Decode.hs:25:0-52 cabal: Error: some packages failed to install: JSONb-1.0.2 failed during the building phase. The exception was: ExitFailure 1
How do I clear up this ambiguity?
On Mon, Apr 25, 2011 at 1:24 PM, Michael Litchard
wrote: I started mindlessly pasting in the output, and the following lept out at me:
,
package authenticate-0.8.2.2-cc3ed2c523ecbf1ad123c3468785149e is unusable due to missing or recursive dependencies: http-enumerator-0.3.1-719bcd77e1dcb62efc9cf9b4f0b72271 package http-enumerator-0.3.1-719bcd77e1dcb62efc9cf9b4f0b72271 is unusable due to missing or recursive dependencies: attoparsec-enumerator-0.2.0.3-4978ab2dc4d87b7b724534bbfdcb07f1 package json-enumerator-0.0.1-7d4b724ae8c9b5ffa92da26856c4e1f1 is unusable due to missing or recursive dependencies: blaze-builder-enumerator-0.2.0.1-23e6e1f270358d3329f627e3a5ce8838 package wai-extra-0.3.2-f8378ad4a5cc6f375d96b718876384fa is unusable due to missing or recursive dependencies:
There's more of the same I'm leaving out.
I'm going to see if I can go somewhere with these error messages. If I totally hose things, I'll let you guys know.
On Tue, Apr 19, 2011 at 4:45 PM, Daniel Fischer
wrote: On Wednesday 20 April 2011 01:22:20, Michael Litchard wrote: > So what else can I try?
$ cabal install -v3 monad-control
That should give some hints at which point exactly things fail.
_______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe

On 26 April 2011 00:20, Rogan Creswick
It would be nice to figure out what is depending on that version of JSONb so we could better determine if upgrading will break anything.
Maybe the following helps: http://bifunctor.homelinux.net/~roel/cgi-bin/hackage-scripts/revdeps/JSONb Bas

In case this ever gets googled ... I'm pretty sure this problem had to do with my environment. I removed $HOME/.cabal and $HOME/.ghc, and upgraded to the latest stable haskell platform. yesod 0.8 has installed fine. I'm not sure what the exact problem was however.

On Tue, Apr 19, 2011 at 4:22 PM, Michael Litchard
yesod-static-0.1.0 depends on monad-control-0.2.0.1 which failed to install.
This is what happened after I did cabal update, then cabal-dev install yesod. This is the original error I received.
Just for a point of reference - I just tried this and monad-control-0.2.0.1 build just fine. (The build failed overall because I didn't have the correct unix-compat c library deps installed.) I poked into the monad-control build system, and the only thing that strikes me as at all unusual is that it uses unicode symbols for :: and -> in Setup.hs. --Rogan
So what else can I try?
On Tue, Apr 19, 2011 at 3:30 PM, Rogan Creswick
wrote: On Tue, Apr 19, 2011 at 3:10 PM, Michael Litchard
wrote: New information, may be helpful.
I manually installed hamlet 0.8 with cabal-dev, and it seemed to install. Here is the message
Registering hamlet-0.8.0... Installing library in /home/mlitchard/hamlet-0.8.0/cabal-dev//lib/hamlet-0.8.0/ghc-6.12.3 Registering hamlet-0.8.0...
It looks like you manually downloaded the hamlet-0.8.0.tar.gz, unpacked it, and ran cabal-dev install from inside there -- is that right? (There's nothing wrong with doing it that way, but it doesn't quite do what you expected, based on the rest of your email. Also, if my assumption is wrong, then the rest of my advice may not help.)
First, it's important to know that cabal-dev sandboxes everything it can. If you want to install hamlet into your .cabal directory, then you need to use cabal, not cabal-dev. Cabal-dev is meant to keep everything for a given project separate from everything else -- in this way you can have multiple projects that depend on conflicting libraries building at the same time, and it also means that coincidental changes to your user package database won't cause spurious *successes* when you build something, which is a surprisingly common problem. Unfortunately this means that the first time you build a project with cabal-dev, it tends to take a long time (it has to build everything it depends on).
Now, there are (at least) two important take-away points / implications of using cabal-dev:
(1) cabal-dev won't install a library into a standard location. That's by design, so you don't usually want to cabal-dev install dependencies manually. (2) cabal-dev uses the local hackage cache to select packages in the same way cabal does (cabal-dev actually just uses cabal to do this).
mlitchard@apotheosis:~/yesod-0.8.0$ cabal-dev install Resolving dependencies... cabal: cannot configure yesod-0.8.0. It requires hamlet ==0.8.* There is no available version of hamlet that satisfies ==0.8.*
I think you just need to run 'cabal update' so cabal-dev can see the latest version of hamlet, after which you can cabal-dev install yesod.
There are a couple other things to try if that doesn't work for some reason.
--Rogan
I noticed it did not install in the $HOME/.cabal/ path. How do make sure it does that? I think if I can get it to install in the right place this will work out.
On Tue, Apr 19, 2011 at 2:52 PM, Rogan Creswick
wrote: On Tue, Apr 19, 2011 at 2:18 PM, Michael Litchard
wrote: mlitchard@apotheosis:~/monad-control$ cabal install Resolving dependencies... Configuring monad-control-0.2.0.1... cabal: Error: some packages failed to install: monad-control-0.2.0.1 failed during the configure step. The exception was: ExitFailure 11
note: I've been trying to use the cab command to manage my packages, I get the same error as above when I use cab instead of cabal.I mention this just in case there is some unforseen problem having to do with cab/cabal interaction.
Has anyone experienced this problem, or know what I can do to get more useful error messages that might reveal the cause of the breakage?
You might learn more by issuing the configure / build steps manually (I think `cabal configure` will produce an error). Upping the verbosity will also help:
# get pages and pages of details: $ cabal install --verbose=3
I would first suggest trying cabal-dev, though (cab can delegate to cabal-dev now too, but I haven't played with it yet).
$ cabal-dev install yesod-0.8
will either work or fail in a way that we can more easily reproduce.
--Rogan

I was also able to install monad-control, both with GHC 7 and 6.12.3. A more
detailed error log will definitely be helpful here.
Michael
On Wed, Apr 20, 2011 at 2:58 AM, Rogan Creswick
On Tue, Apr 19, 2011 at 4:22 PM, Michael Litchard
wrote: yesod-static-0.1.0 depends on monad-control-0.2.0.1 which failed to install.
This is what happened after I did cabal update, then cabal-dev install yesod. This is the original error I received.
Just for a point of reference - I just tried this and monad-control-0.2.0.1 build just fine. (The build failed overall because I didn't have the correct unix-compat c library deps installed.)
I poked into the monad-control build system, and the only thing that strikes me as at all unusual is that it uses unicode symbols for :: and -> in Setup.hs.
--Rogan
So what else can I try?
On Tue, Apr 19, 2011 at 3:30 PM, Rogan Creswick
wrote: On Tue, Apr 19, 2011 at 3:10 PM, Michael Litchard
wrote: New information, may be helpful.
I manually installed hamlet 0.8 with cabal-dev, and it seemed to install. Here is the message
Registering hamlet-0.8.0... Installing library in /home/mlitchard/hamlet-0.8.0/cabal-dev//lib/hamlet-0.8.0/ghc-6.12.3 Registering hamlet-0.8.0...
It looks like you manually downloaded the hamlet-0.8.0.tar.gz, unpacked it, and ran cabal-dev install from inside there -- is that right? (There's nothing wrong with doing it that way, but it doesn't quite do what you expected, based on the rest of your email. Also, if my assumption is wrong, then the rest of my advice may not help.)
First, it's important to know that cabal-dev sandboxes everything it can. If you want to install hamlet into your .cabal directory, then you need to use cabal, not cabal-dev. Cabal-dev is meant to keep everything for a given project separate from everything else -- in this way you can have multiple projects that depend on conflicting libraries building at the same time, and it also means that coincidental changes to your user package database won't cause spurious *successes* when you build something, which is a surprisingly common problem. Unfortunately this means that the first time you build a project with cabal-dev, it tends to take a long time (it has to build everything it depends on).
Now, there are (at least) two important take-away points / implications of using cabal-dev:
(1) cabal-dev won't install a library into a standard location. That's by design, so you don't usually want to cabal-dev install dependencies manually. (2) cabal-dev uses the local hackage cache to select packages in the same way cabal does (cabal-dev actually just uses cabal to do this).
mlitchard@apotheosis:~/yesod-0.8.0$ cabal-dev install Resolving dependencies... cabal: cannot configure yesod-0.8.0. It requires hamlet ==0.8.* There is no available version of hamlet that satisfies ==0.8.*
I think you just need to run 'cabal update' so cabal-dev can see the latest version of hamlet, after which you can cabal-dev install yesod.
There are a couple other things to try if that doesn't work for some reason.
--Rogan
I noticed it did not install in the $HOME/.cabal/ path. How do make sure it does that? I think if I can get it to install in the right place this will work
out.
On Tue, Apr 19, 2011 at 2:52 PM, Rogan Creswick
wrote:
On Tue, Apr 19, 2011 at 2:18 PM, Michael Litchard < michael@schmong.org> wrote:
mlitchard@apotheosis:~/monad-control$ cabal install Resolving dependencies... Configuring monad-control-0.2.0.1... cabal: Error: some packages failed to install: monad-control-0.2.0.1 failed during the configure step. The exception was: ExitFailure 11
note: I've been trying to use the cab command to manage my packages, I get the same error as above when I use cab instead of cabal.I mention this just in case there is some unforseen problem having to do with cab/cabal interaction.
Has anyone experienced this problem, or know what I can do to get more useful error messages that might reveal the cause of the breakage?
You might learn more by issuing the configure / build steps manually (I think `cabal configure` will produce an error). Upping the verbosity will also help:
# get pages and pages of details: $ cabal install --verbose=3
I would first suggest trying cabal-dev, though (cab can delegate to cabal-dev now too, but I haven't played with it yet).
$ cabal-dev install yesod-0.8
will either work or fail in a way that we can more easily reproduce.
--Rogan
_______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe
participants (5)
-
Bas van Dijk
-
Daniel Fischer
-
Michael Litchard
-
Michael Snoyman
-
Rogan Creswick