Perhaps it's better to solve this in HTTP itself?
I think so.
cabal: openTCPConnection: host lookup failure for foo
What version of network is it? I ran ‘grep -r “host lookup failure”’ on
the source of 2.5.0.0 and didn’t find anything.
pgpsUnkhCRI5N.pgp
Description: PGP signature
Hi,
On 26 July 2014 08:55, Nikita Karetnikov nik...@karetnikov.org wrote:
What version of network is it? I ran ‘grep -r “host lookup failure”’ on
the source of 2.5.0.0 and didn’t find anything.
$ cabal sandbox hc-pkg list | grep network
network-2.5.0.0
It probably uses perror or
On Sat, Jul 26, 2014 at 4:15 AM, Mikhail Glushenkov
the.dead.shall.r...@gmail.com wrote:
On 26 July 2014 08:55, Nikita Karetnikov nik...@karetnikov.org wrote:
What version of network is it? I ran ‘grep -r “host lookup failure”’ on
the source of 2.5.0.0 and didn’t find anything.
$ cabal
00:00:00 2001
From: Nikita Karetnikov nik...@karetnikov.org
Date: Sat, 26 Jul 2014 01:59:55 +0400
Subject: [PATCH] Print a more friendly message when http_proxy is down.
---
cabal-install/Distribution/Client/HttpUtils.hs | 23 +++
1 file changed, 15 insertions(+), 8 deletions
Hi,
On 26 July 2014 00:20, Nikita Karetnikov nik...@karetnikov.org wrote:
An attempt to fix #1962. I think the exception comes from ‘connect’ in
‘Network.Socket’.
Perhaps it's better to solve this in HTTP itself? It gives decent
error messages in other cases:
$ export HTTP_PROXY=foo
$ cabal
