bzr+ssh://host:/ fails with "invalid port number in url"

[Jari Aalto]

The syntax bzr+ssh://host:/ fails with "invalid port number". It could equally well treat the empty port part as meaning the default.

--- old description follows ---

In SSH the connect syntax is:

  user@host:/path/to/file

In Bazaar the syntax:

  bzr+ssh://user@host:/path/to/file

gives error

  bzr: ERROR: Invalid url supplied to transport: "invalid port number in url:

Because the port number seems to be mandatory after the colon.

SUGGESTION

1) Please make the syntax compatible with the SSH notation, so that the missing port number
is not considered an error, but as a sign to use default port number of the transport. Here, the SSH 22

2) Please allow writing SSH-style repository locations. E.g. GIT allows
writing repository locations in pure SSH-syntax:

     user@host:/path/to/file

Make this be interpreted by bzr as "bzr+ssh" transport by default

[Martin Pool (mbp)]

I agree about point #2, though it's a different bug, and already discussed in bug 121195.

[Martin Pool (mbp)]

rcp and url syntax are fundamentally different. The colon is not meant to be there according to the url grammar. However, I agree that we should just treat it as the default.

[Robert Collins (lifeless)]

On Mon, 2008-01-21 at 04:18 +0000, Martin Pool wrote:
> rcp and url syntax are fundamentally different. The colon is not meant
> to be there according to the url grammar. However, I agree that we
> should just treat it as the default.

OTOH the : on its own is a good indication that the user is trying rcp
syntax, and we could use that as a way to give the user clear feedback.
-Rob

--
GPG key available at: <http://www.robertcollins.net/keys.txt>.