I have now upgraded subversion to 1.5.1 on svn.python.org.
Please let me know if you encounter problems.
Regards,
Martin
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
I'm seeing the following when trying to svn commit:
Transmitting file data ...Read from remote host svn.python.org: Operation
timed out
svn: Commit failed (details follow):
svn: Connection closed unexpectedly
...
That was with subversion 1.4.4; copying my changes to a different host with
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 python...@svn.python.org still work?
What path did you try to check into?
Regards,
Martin
I'm just trying to commit the following to trunk:
SendingLib/test/test_socket.py
SendingMisc/NEWS
SendingModules/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
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
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?
No. subversion ignores the network layer.
Weird. regardless,
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.
I got some messages in kern.log which might be relevant
Jan 31 23:55:36 dinsdale kernel: IPv6: sending pkt_too_big
