bzr+ssh broken for non standard ports.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Fix Released
|
High
|
Andrew Bennetts | ||
bzr (Debian) |
Fix Released
|
Unknown
|
Bug Description
Fixing bzr log bzr:// caused the following regresion going from 0.91rc2 to 0.91.
I have a few bzr+ssh:// repositories hosted on a remote server. In
order to isolate different classes of users from one another, they are
stored in vservers, and each vserver has an SSH daemon listening on a
different port (10022, 20022, etc.). My ~/.ssh/config has entries so
that the right port is automatically selected by ssh when connecting
to the appropriate CNAME.
bzr 0.91rc2 used to work fine, but 0.91 final explicitly adds a "-p
22" to the SSH invocation, thus overriding the configuration and
breaking bzr+ssh:// branches with non-22 ports. I believe this
regression may be related to the following paragraph, listed in "BUG
FIXES" of the NEWS.gz file:
* Fix ''bzr info bzr://host/'' and other operations on ''bzr://' URLs with
an implicit port. We were incorrectly raising PathNotChild due to
inconsistent treatment of the ''_port'' attribute on the Transport object.
(Andrew Bennetts, #133965)
Roland.
Thanks to Roland for the report.
Changed in bzr: | |
status: | Unknown → New |
Changed in bzr: | |
status: | New → Fix Released |
That is likely to be the problem.