© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
demo site
(Get the code!)
This is more than Low importance I think. Judging from IRC it happens to new users quite regularly, and it's a pretty unfortunate first impression of bzr.
Part of the problem is that the "Permission denied (publickey)." message, which is probably the most important part of the output, is somewhat buried by the very verbose error that comes after it. And the advice to try "-Dhpss" is a red herring most of the time.
Ideally, bzr should notice when the SSH connection failed to establish, and report an error more like:
$ bzr branch lp:foo
Permission denied (publickey).
bzr: ERROR: Failed to establish SSH connection to <email address hidden>.
I'm not sure how easy that is to achieve, but it would be a large improvement.