Bazaar

warn if host not found when trying to contact bound branch

Bug #47951 reported by Jamie Wilkinson on 2006-06-02

Affects		Status	Importance	Assigned to	Milestone
	Bazaar	Fix Released	Medium	Unassigned	Bazaar 0.13

Bug Description

I just tried to pull from a mirror of a branch, because I left my laptop at
home today and I know that it's up to date with an http mirror that I push
out to, so I tried to pull from that mirror URL into my branch at work.

It kept saying "ssh: connect to host dawn port 22: No route to host" and it
took me a couple of attempts before I realised that I had bound the branch
to my laptop.

Would it be possible to put the reason for the connection attempt in the
exception?

I.e., rather than juyst say:

booty% bzr pull http://repo.spacepants.org/z/z.dev
/ [ ] Pull phase
0/2ssh: connect to host dawn port 22: No route to host
bzr: ERROR: exceptions.EOFError:
at /usr/lib/python2.4/site-packages/paramiko/sftp.py line 147
in _read_all

it could note:

ssh: connect to host dawn port 22: No route to host
bzr: ERROR: exceptions.EOFError:
...
attempting to contact dawn before repo.spacpeants.org because branch is
bound.

or something to that effect, as a friendly reminder that one might need to
unbind before working in this branch.

Revision history for this message

John A Meinel (jameinel) wrote on 2007-05-01:

The current error is:
ssh: juju.arbash-meinel.com: No address associated with nodename
bzr: ERROR: Unable to connect to target of bound branch BzrBranch5('file:///...') => sftp://host/path/...: Unable to connect to SSH host juju; EOF during negotiation

Which I think is relatively clear. It is a bit verbose, but it does say that "Unable to connect to SSH host juju".

I think this fix has been around a while.

See also bug #59836, bug #52861, and bug #49172.

Because of bug #49172, I'm marking this as fixed in 0.13