On Sat, 2008-10-11 at 11:52 -0400, Stephen Hicks wrote:
Er, I forgot to --edit-description, nor did I provide a long description. Basically, I've seen a ton of complaints (and no solutions) over the mailing list and IRC about this "recv: resource vanished (Connection reset by peer)" error when attempting to 'cabal update'. I tracked it down to a bug in Network.Browser that causes it to fail when behind a NAT-based router. On the other hand, Network.HTTP.simpleHTTP, while being less feature-rich, doesn't seem to have a problem with NAT. I've submitted a bug report to the maintainer of Network.HTTP, but for the time being, I think it's also prudent to include this simple (pun intended) workaround in cabal install as well.
If you have a moment, could you check if this bug is fixed in the HTTP-4000.x release? Or send us the bug report you previously sent to the maintainer. The maintainer switched of course so I'm not sure if any reports got dropped in between. The current plan is to use HTTP-4000.x for cabal-install, so we want to make sure it is working as well as possible. Duncan