Comment 4 for bug 556132

Chuck Wilder wrote:
[...]
> > 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.
> >
> I am able to do bzr branch and bzr get successfully with other trunks.
> Could the size play a role? widelands-media tilts the scales at over
> 1.5Gb. Plus it is only on Windows boxes (XP and Vista Pro) that I
> encountered the error. I can bring it down on my Ubuntu boxes without the
> error, so I have a work-around for now.
>
> It's darn frustrating because it seems to transfer just about all of the
> data, then craps out in the final stages. I thought about setting up a
> different SSH key with Launchpad, but haven't gotten around to trying it.
>
> Thanks for your response.

Huh, that's weird! I'd expect key-exchange to be something that happens very
early in the SSH conversation, well before bzr starts making requests about
specific branches or anything like that. But you're right, the traceback shows
it has actually gotten a lot further than I thought. I wonder if paramiko is
giving an incorrect error message?

How long does it run for, exactly? If it's an hour, then maybe you're
experiencing bug 537116.

The contents of bzr's log file ("bzr --version" will tell you where to find it)
after doing "bzr get -Dhpss -Dhpssdetail lp:widelands-media" would be
interesting.

As with bug 537116, a workaround is probably to fetch it incrementally, e.g.:

    bzr branch -r1000 lp:widelands-media
    cd widelands-media
    bzr pull -r2000
    bzr pull -r3000
    ...

Adjust the numbers to whatever works well for you.