"bzr version-info :parent" fails with bzr+ssh on 2.6b2

Bug #1158972 reported by Hartmut Holzgraefe
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Bazaar
New
Undecided
Unassigned

Bug Description

Branching a remote repository using bzr 2.6b2 on both sides i get the following error:

  $ bzr version-info :parent
  bzr: ERROR: <bzrlib.transport.remote.RemoteSSHTransport url=bzr+ssh://hartmut@10.10.33.1/home/hartmut/projects/eventum/sky/vagrant/bzr/eventum_internal/> is not a local path.

The same works fine with 2.6b on the client side against a parent repository on bzr 2.1.4.

As far as i can tell from comparing strace logs a ssh handshake happens in both cases
(i can see version strings sent and received), but then with the 2.6b2 parent the client
i can see that local python code is read which does not happen with the bzr 2.1.4 parent.

--version info

Bazaar (bzr) 2.6b2
  Python interpreter: /usr/bin/python 2.7.3
  Python standard library: /usr/lib/python2.7
  Platform: Linux-3.5.0-26-generic-x86_64-with-Ubuntu-12.10-quantal
  bzrlib: /usr/lib/python2.7/dist-packages/bzrlib
  Bazaar configuration: /root/.bazaar
  Bazaar log file: /root/.bzr.log

and

Bazaar (bzr) 2.1.4
  Python interpreter: /usr/bin/python 2.6.5
  Python standard library: /usr/lib/python2.6
  Platform: Linux-2.6.33.5-rscloud-x86_64-with-Ubuntu-10.04-lucid
  bzrlib: /usr/lib/python2.6/dist-packages/bzrlib

Revision history for this message
John A Meinel (jameinel) wrote : Re: [Bug 1158972] [NEW] "bzr version-info :parent" fails with bzr+ssh on 2.6b2

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

The only thing I can think of is that bzr-2.6b2 is probably trying to
resolve things like "lp:". (eg if parent is lp:foo it will resolve to
the actual bzr+ssh://bazaar.launchpad.net/+branch/foo branch, rather
than failing).

It doesn't make sense that it would require a local path for that. Can
you check if:
 bzr version-info
bzr+ssh://hartmut@10.10.33.1/home/hartmut/projects/eventum/sky/vagrant/bzr/eventum_internal/

Works?

(Is the bug that version-info isn't handling a remote path, or is it a
bug that :parent is thinking somewhere that what it has should be a
local path.)

John
=:->

On 2013-03-23 0:33, Hartmut Holzgraefe wrote:
> Public bug reported:
>
> Branching a remote repository using bzr 2.6b2 on both sides i get
> the following error:
>
> $ bzr version-info :parent bzr: ERROR:
> <bzrlib.transport.remote.RemoteSSHTransport
> url=bzr+ssh://hartmut@10.10.33.1/home/hartmut/projects/eventum/sky/vagrant/bzr/eventum_internal/>
> is not a local path.
>
> The same works fine with 2.6b on the client side against a parent
> repository on bzr 2.1.4.
>
> As far as i can tell from comparing strace logs a ssh handshake
> happens in both cases (i can see version strings sent and
> received), but then with the 2.6b2 parent the client i can see that
> local python code is read which does not happen with the bzr 2.1.4
> parent.
>
> --version info
>
> Bazaar (bzr) 2.6b2 Python interpreter: /usr/bin/python 2.7.3 Python
> standard library: /usr/lib/python2.7 Platform:
> Linux-3.5.0-26-generic-x86_64-with-Ubuntu-12.10-quantal bzrlib:
> /usr/lib/python2.7/dist-packages/bzrlib Bazaar configuration:
> /root/.bazaar Bazaar log file: /root/.bzr.log
>
> and
>
> Bazaar (bzr) 2.1.4 Python interpreter: /usr/bin/python 2.6.5 Python
> standard library: /usr/lib/python2.6 Platform:
> Linux-2.6.33.5-rscloud-x86_64-with-Ubuntu-10.04-lucid bzrlib:
> /usr/lib/python2.6/dist-packages/bzrlib
>
> ** Affects: bzr Importance: Undecided Status: New
>

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.13 (Cygwin)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlFOnTUACgkQJdeBCYSNAAPn7ACdEVZaPJQ8eyXitPhbTIde++cI
Aj4AoIJG9KUg+OwciAW4RnjYz9rv7wd9
=pZyq
-----END PGP SIGNATURE-----

Jelmer Vernooij (jelmer)
tags: added: check-for-breezy
Jelmer Vernooij (jelmer)
tags: removed: check-for-breezy
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.