Merge lp:~jml/bzr/default-stacking-bug-385132 into lp:~bzr/bzr/trunk-old
Proposed by
Jonathan Lange
Status: | Merged |
---|---|
Merged at revision: | not available |
Proposed branch: | lp:~jml/bzr/default-stacking-bug-385132 |
Merge into: | lp:~bzr/bzr/trunk-old |
Diff against target: | 165 lines |
To merge this branch: | bzr merge lp:~jml/bzr/default-stacking-bug-385132 |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Andrew Bennetts | Approve | ||
Review via email: mp+7330@code.launchpad.net |
To post a comment you must log in.
Bazaar 1.15 added a verb for initialize_ex which broke certain default stacking policies, notably the one that Launchpad uses. This patch attempts to fix this regression by returning relative URLs when the stacking policy itself has a relative URL.
There are two interesting cases. One is where the policy looks like: stack_on= /foo/bar/ baz
default_
and the other where it looks like: stack_on= trunk
default_
Current versions of Bazaar send these as ('/foo/bar/baz', 'chroot- 123124: ///') and ('trunk', 'chroot-15245:///). This patch changes them to be sent as ('/foo/bar/baz', '.') and ('trunk', '..').
Note that the fix touches both client and server side. That means that 1.15 clients will forever be broken when pushing new branches to Launchpad. This sucks, can we do something about it?
I think the rest of the patch is fairly simple: it adds some tests, trying to be as direct as possible; it changes the client to handle relative final_stack_pwd; it changes the server to generate relative final_stack & final_stack_pwd; it cleans up some lint & spelling mistakes found along the way.
This bug is blocking the 1.16rc1 release. I would greatly appreciate a swift review.
Thanks,
jml