← Back to team overview

registry team mailing list archive

[Bug 681431] [NEW] confusing error when original stacked branch becomes invalid later

 

You have been subscribed to a public bug:

I did the following:

$ bzr co lp:vmbuilder
$ cd vmbuilder
$ bzr merge lp:~mvo/vmbuilder/add-natty
bzr: ERROR: Not a branch: "bzr+ssh://bazaar.launchpad.net/~ubuntu-virt/vmbuilder/0.12/".

This is rather confusing as I have no idea where this references to 0.12 comes from.
Fortuantely jelmer in #bzr gave me the hint that the stacked branch 0.12 might have been
renamed or disappeared and this may cause the error. 

The other interessting bit is that I pushed my local "add-natty" branch as lp:~mvo/vmbuilder/add-natty2:
$ bzr push lp:~mvo/vmbuilder/add-natty2
Using default stacking branch /~vmbuilder-dev/vmbuilder/0.12 at lp-57748368:///~mvo/vmbuilder
Created new stacked branch referring to /~vmbuilder-dev/vmbuilder/0.12.        

*but* that branch I was able to merge into lp:vmbuilder.

** Affects: bzr
     Importance: Medium
         Status: Confirmed

** Affects: null
     Importance: Undecided
         Status: New

-- 
confusing error when original stacked branch becomes invalid later
https://bugs.edge.launchpad.net/bugs/681431
You received this bug notification because you are a member of Registry Administrators, which is the registrant for NULL Project.