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
Hello all,
A while back, I was nattering around the parsing code for Cabal,
and I noticed that Cabal still had code for parsing version tags,
but was explicitly *not* printing out version tags. I proposed
that we should get rid of the parsing code as well, but when
I mentioned this on #ghc Mark
Excerpts from Mikhail Glushenkov's message of 2014-07-26 23:44:39 +0100:
IIRC, Duncan wants to remove version tags both from Cabal and
Data.Version. So perhaps it's time to deprecate them.
My question here is orthogonal to the question of deprecation:
if we are deprecating them, but not
