confusing error when original stacked branch becomes invalid later
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Confirmed
|
Medium
|
Unassigned |
Bug Description
I did the following:
$ bzr co lp:vmbuilder
$ cd vmbuilder
$ bzr merge lp:~mvo/vmbuilder/add-natty
bzr: ERROR: Not a branch: "bzr+ssh:
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-
Created new stacked branch referring to /~vmbuilder-
*but* that branch I was able to merge into lp:vmbuilder.
affects: | bzr → launchpad-code |
Changed in bzr: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
tags: | added: stacking |
no longer affects: | null |
tags: | added: check-for-breezy |
I just reproduced my steps in /tmp and I can easily trigger the error about the 0.12 branch with lp:~mvo/vmbuilder/add-natty. Please let me know if you need more info.