Confusing error message if ssh login fails while using lp url
Bug #238776 reported by
Rob Weir
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Confirmed
|
High
|
Unassigned | ||
Breezy |
Triaged
|
High
|
Unassigned |
Bug Description
If bzr is presented with a lp: url and has a lp-login set, but finds it can't login (e.g. if no usable ssh keys are available), you get this error:
rob@hypercube:
Permission denied (publickey).
bzr: ERROR: Connection closed: please check connectivity and permissions (and try -Dhpss if further diagnosis is required)
Maybe it could fall back to using HTTP instead of failing.
tags: | added: lp-directory lp-login |
tags: | added: launchpad |
tags: |
added: lpurl removed: lp-directory |
tags: | added: check-for-breezy |
tags: |
added: readonly removed: check-for-breezy |
Changed in brz: | |
status: | New → Confirmed |
status: | Confirmed → Triaged |
importance: | Undecided → High |
To post a comment you must log in.
Hi,
This would be useful if http will work.
I think this would become part of the suggested overhaul of
transports, where the caller indicates whether they are going to
want to write to the transport and the provider acts appropriately.
Although, I'm not sure that there is any provision for fallback in
the current codebase, and so this might be quite a bit of work
on top of the above.
Thanks,
James