(original) (raw)

fwiw, I just turned off IPv6 and it worked fine. That makes no sense to me given that the ssh connection worked fine either way. Does svn itself try and log source addresses somehow when using svn+ssh and balk on IPv6 addrs?

Weird. regardless, this is presumably not related to your subversion upgrade. I don't think I've done any commits from these hosts since I got IPv6 connectivity, only updates.

-gps

On Sat, Jan 31, 2009 at 2:49 PM, Gregory P. Smith <greg@krypto.org> wrote:

I'm just trying to commit the following to trunk:

Sending        Lib/test/test_socket.py
Sending        Misc/NEWS
Sending        Modules/socketmodule.c
Transmitting file data ...

I have another svn commit attempt which appesrs to be hanging and destined to timeout running right now.

ssh -v pythondev@svn.python.org works fine.

-gps

On Sat, Jan 31, 2009 at 2:04 PM, "Martin v. L�wis" <martin@v.loewis.de> wrote:

> any ideas?

Assuming you reported this right after it happened - sorry, no.
I can't find anything relevant in the log files (although a
precise time of failure would have helped).

Does a plain "ssh pythondev@svn.python.org" still work?

What path did you try to check into?

Regards,
Martin