bzr upgrade should accept a --stacked-on parameter

Bug #682719 reported by Vincent Ladeuil
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

I wanted to push some changes on lp:~bzr-core/bzr/devnotes and discovered it was still using the 1.9 format.

No problem thought I, let's just upgrade it !

Ha ha.

The upgrade failed successfully: a new '.bzr' was created in 2a format but still stacked on /~bzr/bzr/trunk our old beloved trunk

The solution was to create a branch.conf containing:

parent_location = lp-hosted:///~bzr-core/bzr/devnote
stacked_on_location = /~bzr-pqm/bzr/

and upload it with lftp.

As jelmer said on IRC: "This is too hard for somebody not familiar with the internals though :-/"

Adding a --stacked-on parameter to upgrade should address this case.

Some sanity check should be performed to ensure the new stacked-on repo contains the necessary (hand-waving) revisions.

If the upgrade branch contains ghosts though, this may be tricky (or require more thought than I want to put in this report).

Also, upgrade without this parameter shouldn't succeed at all as the branch was left in a broken state.

Revision history for this message
Vincent Ladeuil (vila) wrote :

For the record:

lftp s
cd ok, cwd=~bzr-core/bzr/devnotes
lftp> ls
drwxr-xr-x 5 1001 1005 4096 Nov 29 15:34 .bzr
drwxr-xr-x 5 1001 1005 4096 Nov 29 15:34 backup.bzr.~1~
drwxr-xr-x 5 1001 1005 4096 Nov 29 15:18 backup.bzr.~2~

~1~ should still contain the branch and repo before upgrade
~2~ is a first attempt and contain a 2a branch and repo

Jelmer Vernooij (jelmer)
tags: added: stacking
Jelmer Vernooij (jelmer)
tags: added: check-for-breezy
Jelmer Vernooij (jelmer)
Changed in brz:
status: New → Triaged
importance: Undecided → High
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.