cabal-install fails on WinXP

I've tried using cabal-install (cabal.exe) for the first time to install yi, and all of the packages fail to download. Reducing to a simple test case, "cabal install binary" fails with: Resolving dependencies... Downloading binary-0.4.4... cabal: Error: some packages failed to install: binary-0.4.4 failed while downloading the package. Where do I look to diagnose this? Alistair

On Wed, 2009-04-15 at 14:17 +0100, Alistair Bayley wrote:
I've tried using cabal-install (cabal.exe) for the first time to install yi, and all of the packages fail to download. Reducing to a simple test case, "cabal install binary" fails with:
Resolving dependencies... Downloading binary-0.4.4... cabal: Error: some packages failed to install: binary-0.4.4 failed while downloading the package.
Where do I look to diagnose this?
Try: cabal fetch binary -v3 It should give you plenty of detail on the HTTP conversation. Could you also file a ticket pointing out how useless the default error message is when the download fails. We should at least tell the user the HTTP error code. Duncan

2009/4/16 Duncan Coutts
Try:
cabal fetch binary -v3
It should give you plenty of detail on the HTTP conversation. Could you also file a ticket pointing out how useless the default error message is when the download fails. We should at least tell the user the HTTP error code.
http://hackage.haskell.org/trac/hackage/ticket/545 fetch -v3 output below. Seems to be trying to use a proxy, but that's not necessary as the machine is "directly" connected (via a router). Alistair C:\bayleya\haskell>cabal fetch binary -v3 Reading installed packages... ("c:\\ghc\\ghc-6.10.1\\bin\\ghc-pkg.exe",["dump","--global"]) ("c:\\ghc\\ghc-6.10.1\\bin\\ghc-pkg.exe",["dump","--user"]) Reading available packages... Warning: The package list for 'hackage.haskell.org' is 16 days old. Run 'cabal update' to get the latest list of available packages. Resolving dependencies... selecting binary-0.4.4 (hackage) and discarding binary-0.2, 0.3, 0.4, 0.4.1, 0.4.2, 0.4.3 and 0.4.3.1 selecting bytestring-0.9.1.4 (installed or hackage) and discarding bytestring-0.9, 0.9.0.1, 0.9.0.2, 0.9.0.3, 0.9.0.4, 0.9.1.0, 0.9.1.1, 0.9.1.2 and 0.9.1.3 selecting ghc-prim-0.1.0.0 (installed) selecting rts-1.0 (installed) selecting containers-0.2.0.0 (installed or hackage) and discarding containers-0.1.0.0 and 0.1.0.1 selecting array-0.2.0.0 (installed or hackage) and discarding array-0.1.0.0 selecting syb-0.1.0.0 (installed or hackage) selecting base-3.0.3.0 (installed) and 4.0.0.0 (installed) and discarding syb-0.1.0.0 selecting integer-0.1.0.0 (installed) Downloading binary-0.4.4... GET http://hackage.haskell.org/packages/archive/binary/0.4.4/binary-0.4.4.tar.gz Sending: GET /packages/archive/binary/0.4.4/binary-0.4.4.tar.gz HTTP/1.1 User-Agent: cabal-install/0.6.2 Host: hackage.haskell.org proxy uri host: lonproxy.lon.invesco.com, port: :6080 Creating new connection to lonproxy.lon.invesco.com:6080 cabal: getHostByName: does not exist (no such host entry)

On Mon, 2009-04-20 at 09:25 +0100, Alistair Bayley wrote:
2009/4/16 Duncan Coutts
: Try:
cabal fetch binary -v3
It should give you plenty of detail on the HTTP conversation. Could you also file a ticket pointing out how useless the default error message is when the download fails. We should at least tell the user the HTTP error code.
http://hackage.haskell.org/trac/hackage/ticket/545
fetch -v3 output below. Seems to be trying to use a proxy, but that's not necessary as the machine is "directly" connected (via a router).
It's using the IE proxy information from the registry. Check the IE "internet settings". If you think it's wrong that it's using it then file a ticket, I mean for example if it were using the proxy when the settings say that the proxy is disabled. Duncan

2009/4/20 Duncan Coutts
It's using the IE proxy information from the registry. Check the IE "internet settings". If you think it's wrong that it's using it then file a ticket, I mean for example if it were using the proxy when the settings say that the proxy is disabled.
It's using the "internet settings" correctly. A question, though: this output: Reading available packages... Warning: The package list for 'hackage.haskell.org' is 16 days old. Run 'cabal update' to get the latest list of available packages. Resolving dependencies... selecting binary-0.4.4 (hackage) and discarding binary-0.2, 0.3, 0.4, 0.4.1, 0.4.2, 0.4.3 and 0.4.3.1 ... (blah blah blah( suggests that it is connecting (succesfully) to hackage to determine which versions of packages to download. Is that correct? If so, it seems a bit odd that this connection works, while the later GETs fail because they try to use the proxy. Alistair

On Thu, 2009-04-23 at 10:53 +0100, Alistair Bayley wrote:
2009/4/20 Duncan Coutts
: It's using the IE proxy information from the registry. Check the IE "internet settings". If you think it's wrong that it's using it then file a ticket, I mean for example if it were using the proxy when the settings say that the proxy is disabled.
It's using the "internet settings" correctly. A question, though: this output:
Reading available packages... Warning: The package list for 'hackage.haskell.org' is 16 days old. Run 'cabal update' to get the latest list of available packages. Resolving dependencies... selecting binary-0.4.4 (hackage) and discarding binary-0.2, 0.3, 0.4, 0.4.1, 0.4.2, 0.4.3 and 0.4.3.1 ... (blah blah blah(
suggests that it is connecting (succesfully) to hackage to determine which versions of packages to download. Is that correct?
No, it's using local information only. It is using the (16 day old) package index from hackage to know what is available remotely.
If so, it seems a bit odd that this connection works, while the later GETs fail because they try to use the proxy.
It's pretty explicit which commands go to the network and which are local. There's no sneaky network access. Duncan

http://hackage.haskell.org/trac/hackage/ticket/545
fetch -v3 output below. Seems to be trying to use a proxy, but that's not necessary as the machine is "directly" connected (via a router).
On my machine, IE has proxy settings configured, Firefox does not (I rarely use IE). cabal seems to use IE's settings; if I change IE so that it does not use a proxy, then it's all good. Thanks, Alistair
participants (2)
-
Alistair Bayley
-
Duncan Coutts