"bzr pull :push" constructs a bad URL and fails

[Brad Crittenden]

My branch on LP had been changed on another computer. I wanted to get the changes. For my local branch, the LP repository is the 'push' destination. So I attempted 'bzr pull :push', which looks funny but is exactly what I wanted. The results are:

.../bac/canonical/lp-branches/bug-242994> bzr pull :push
bzr: ERROR: Not a branch: "/home/bac/canonical/lp-branches/bug-242994/lp:~bac/launchpad/bug-242994/".

As you can see, the URL used is relative to my local cwd, which is odd.

The related branches are:

.../bac/canonical/lp-branches/bug-242994> bzr info
Repository tree (format: 1.6)
Location:
  shared repository: /home/bac/canonical/lp-branches
  repository branch: .

Related branches:
  public branch: bzr+ssh://bazaar.launchpad.net/~bac/launchpad/bug-242994
    push branch: lp:~bac/launchpad/bug-242994
  parent branch: /home/bac/canonical/lp-branches/private-teams-p1
  submit branch: /home/bac/canonical/lp-branches/trunk

And the bzr version is:

.../bac/canonical/lp-branches/bug-242994> bzr version
Bazaar (bzr) 1.14.1
  Python interpreter: /usr/bin/python 2.6.2
  Python standard library: /usr/lib/python2.6
  bzrlib: /usr/lib/python2.6/dist-packages/bzrlib
  Bazaar configuration: /home/bac/.bazaar
  Bazaar log file: /home/bac/.bzr.log

[Vincent Ladeuil (vila)]

Weird.

What does 'bzr lp-open :push' says ?

I suspect you put 'lp:~bac/launchpad/bug-242994/' in your branch.conf manually ?

That may be the root cause, in which case, we may have to process the URLs from our configuration files as we process the ones from the command line or something (but that may conflict with the idea of resolving them at the latest possible time which could also address your problem).

[Brad Crittenden (bac)]

Here is the result of lp-open:

.../bac/canonical/lp-branches/bug-242994> bzr lp-open :push
bzr: ERROR: :push is not registered on Launchpad.

As to my branch.conf I assure you I did not edit it manually. Here are the contents:

.../bac/canonical/lp-branches/bug-242994> cat .bzr/branch/branch.conf
parent_location = ../private-teams-p1/
submit_branch = file:///home/bac/canonical/lp-branches/trunk/

[Vincent Ladeuil (vila)]

Wow, bugs, bugs all over the place ;-/

Ok, so the push branch displayed by 'bzr info' should come from locations.conf then ?

The rest of my initial comment still applies though, there are inconsistencies in the way we process the URLs.

To workaround the bug(s) you have to find the place were the lp:~bac/launchpad URL was first introduced and expand it there (but I suppose you have pushed your branch long ago now :-/).