Interesting. We should probably catch this and raise a ConnectionError in this case. (And in general perhaps we should trap SSHException and raise a TransportError instead of dumping a traceback). So this error would look like:
C:\Documents and Settings\Chuck>bzr get lp:widelands-media
Connected (version 2.0, client Twisted)
Authentication (publickey) successful!
Secsh channel 1 opened.
Connection error: SSH failure: Key-exchange timed out waiting for key negotiation
As for why this happened to you, perhaps port 22 is firewalled? Or maybe there was simply an intermittent network problem. Either way, I don't think bzr can do much about it other than report the error as clearly as possible.
Interesting. We should probably catch this and raise a ConnectionError in this case. (And in general perhaps we should trap SSHException and raise a TransportError instead of dumping a traceback). So this error would look like:
C:\Documents and Settings\Chuck>bzr get lp:widelands-media
Connected (version 2.0, client Twisted)
Authentication (publickey) successful!
Secsh channel 1 opened.
Connection error: SSH failure: Key-exchange timed out waiting for key negotiation
As for why this happened to you, perhaps port 22 is firewalled? Or maybe there was simply an intermittent network problem. Either way, I don't think bzr can do much about it other than report the error as clearly as possible.