Re: [Python-Dev] Subversion upgraded to 1.5
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 subversion 1.5.1 has the same result. svn update works fine on both hosts in the same sandbox i'm trying to commit from. fwiw, they are both connecting to svn.python.org using IPv6 but that should be irrelevant to svn+ssh as the tcp6 ssh connection works fine. any ideas? -Greg On Sat, Jan 31, 2009 at 7:47 AM, Martin v. Löwis mar...@v.loewis.dewrote: 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: http://mail.python.org/mailman/options/python-dev/greg%40krypto.org ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Subversion upgraded to 1.5
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 ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Subversion upgraded to 1.5
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 python...@svn.python.org works fine. -gps On Sat, Jan 31, 2009 at 2:04 PM, Martin v. Löwis mar...@v.loewis.dewrote: 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 ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Subversion upgraded to 1.5
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 g...@krypto.org wrote: 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 python...@svn.python.org works fine. -gps On Sat, Jan 31, 2009 at 2:04 PM, Martin v. Löwis mar...@v.loewis.dewrote: 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 ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Subversion upgraded to 1.5
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, 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. That alone can't be the problem. I tried to commit something over IPv6, and it worked just fine. Regards, Martin ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Subversion upgraded to 1.5
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 to self Jan 31 23:55:36 dinsdale kernel: IPv6: sending pkt_too_big to self Feb 1 00:02:57 dinsdale kernel: IPv6: sending pkt_too_big to self Of course, it is five minutes off your connect attempt (IIUC), so it also might be irrelevant. Regards, Martin ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
