cabal-install fails on WinXP
duncan.coutts at worc.ox.ac.uk
Thu Apr 23 06:06:05 EDT 2009
On Thu, 2009-04-23 at 10:53 +0100, Alistair Bayley wrote:
> 2009/4/20 Duncan Coutts <duncan.coutts at worc.ox.ac.uk>:
> > 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.
More information about the cabal-devel