pushing branch6/packs5 to location with default stacking policy creates broken branch

Bug #291046 reported by Michael Hudson-Doyle
4
Affects Status Importance Assigned to Milestone
Bazaar
Fix Released
High
Andrew Bennetts

Bug Description

Similarly to bug 259275, if you push a branch with a repository that supports stacking but a branch format that does not to a location that supplies a default stacking location (eg launchpad) Bazaar only uploads the new revisions but doesn't/cant set the stacked-on location, resulting in a broken branch.

More fun with sprout/clone...

Revision history for this message
Andrew Bennetts (spiv) wrote :

I've sent a fix for this to the mailing list.

Changed in bzr:
assignee: nobody → spiv
importance: Undecided → High
milestone: none → 1.11rc1
status: New → Fix Committed
Revision history for this message
Andrew Bennetts (spiv) wrote :

Merged in bzr.dev r3910. It'll be part of 1.11.

Changed in bzr:
status: Fix Committed → Fix Released
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.