Bazaar 2.0.0 released and bug 375013
David Ingamells
david.ingamells at mapscape.eu
Thu Oct 8 11:11:56 BST 2009
When I upgraded our site to version 2.0.0 we started hitting the problem
reported in
https://bugs.launchpad.net/bzr/+bug/375013
with every commit. In the short term I've had to go back to our previous
version: 1.7
The existing stacked branches (which number over 30, so the workarounds
suggested are not attractive) were all made with version 1.7 and we have
never encountered this problem before.
The stacked branches have version as reported by "bzr info":
Standalone tree (format: 1.9)
The parent has (it has no working tree):
Repository branch (format: 1.14 or 1.9)
I have some questions, the answers to which will help me decide how to
best get version 2.0 in use:
1) Does this problem exist if the stacked branch was made with version 2.0?
2) Will a fix be released for this in 2.0, if so when?
3) Is the problem related to repos format 2a vs non-2a?
4) Is there a sequence of format upgrades in the parent repos that will
help (given that to keep everyone working during the changes I must only
create formats that version 1.17 supports)?
Thanks in advance,
David.
More information about the bazaar
mailing list