Hello!
While the primary upstream doesn't have an AAAA record, one of the
mirrors[1] does have a fully functioning AAAA record, and I'd expect
hackage-security's mirror fallback logic to fallback to that one.
If you're using a recent cabal 1.24, you will have to enable the
hackage-security capable transport by enabling the "secure" repos by
making sure the "secure: True" line is active like so in your
~/.cabal/config
repository hackage.haskell.org
url: http://hackage.haskell.org/
secure: True
Starting with the soon to be released cabal 2.0 version,
hackage-security is enabled by default.
If this still doesn't work for you, please file an issue at
https://github.com/haskell/cabal/issues
[1]: http://objects-us-west-1.dream.io/hackage-mirror/"
On Wed, Apr 26, 2017 at 11:42 PM, Serguey Zefirov
I have found that Cabal does not work on IPv6-only networks (which my machine happen to be part of).
The problem is basically this: "ping hackage.haskell.org" does not resolve host while "ping6 hackage.haskell.org" does. Thus cabal cannot do anything useful on that machine.
Do anyone have a solution for that? I was unable to find any on the internet. ;)
_______________________________________________ Haskell-Cafe mailing list To (un)subscribe, modify options or view archives go to: http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe Only members subscribed via the mailman list are allowed to post.