[ERROR] AssertionError: 110 != 116

[Andrew Lambe]

The fix worked perfectly, even better than I expected.
I thought "bzr pull --overwrite ." would overwrite the changes in my working tree.
However, "bzr pull --overwrite ." only rewrote the history.
Just what I needed, thanks.

I did find your note on Bug #91725 which covers this issue.
I think the status of this bug should at least be changed to confirmed.

I vote for automatic re-normalization under these conditions.
Otherwise, I suggest having a "bzr normalize-history" command, which is essentially an alias for "bzr pull --overwrite ." and give a better error message such as:

 Cannot commit changes to non-normalized branch history.
 Versions of bzr prior to 0.15 may have left this condition.
 To normalize the branch history use the command, bzr normalize-history
-- 

Andrew Lambe
Systems Programmer
Information Technology
Oral Roberts University
Tulsa, Oklahoma 

>>> On 5/11/2007 at 6:18 pm, in message <4644F9B7.2060904 at arbash-meinel.com>, John
Arbash Meinel <john at arbash-meinel.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Andrew Lambe wrote:
>> I get the following error when trying to commit:
>> 
>> bzr: ERROR: exceptions.AssertionError: 110 != 116
> 
> You have a non-normalized history. Presumably you have had this branch
> for a long time.
> 
> Doing "bzr pull --overwrite ." should fix your revision-history file.
> 
> John
> =:->
> 
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.7 (Darwin)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org 
> 
> iD8DBQFGRPm3JdeBCYSNAAMRAtSqAJ0bAmZUIR6CH+m0zN4VT8QqCsQnHgCg0vFP
> 8H7NllFqsdoWPdp3IaAS8hk=
> =Xhmy
> -----END PGP SIGNATURE-----