Bazaar 2.0.0 released and bug 375013
david.ingamells at mapscape.eu
Fri Oct 9 06:53:58 BST 2009
John Arbash Meinel wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> David Ingamells wrote:
>> When I upgraded our site to version 2.0.0 we started hitting the problem
>> reported in
>> 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.
> So to mention, the reason we put the check into 2.0.0 is because commit
> to a stacked branch is actually slightly broken in all versions. It
> doesn't record enough information to guarantee that you can stream the
> data *out* of the stacked branch afterwards.
> So while I can understand it being a pain, it *is* a correctness thing.
So I can so see that, but that so doesn't help me now, does it?
That "correctness thing" is to prevent an underlying bug in bazaar from
possibly causing serious problems. However my interpretation is that
raising the error is a temporary precaution until that bug can be
solved: the sequence of doing a commit on a stacked branch should work
and that underlying bug needs to be fixed - otherwise the whole idea of
stacked branches would have to be scrapped.
More information about the bazaar