This is not exactly building confidence- bzr now aborts in this way for *every* remove of a tree structure. I added a trivial script to illustrate the problem:
jal@odeon:~$ ./trivial
Created a standalone tree (format: 2a)
adding a
adding a/b
adding a/b/c
adding a/b/c/d
adding a/b/c/d/file
Committing to: /home/jal/test/a/
added a
added a/b
added a/b/c
added a/b/c/d
added a/b/c/d/file
Missing checkcommit.jar, not checking commits.
Committed revision 1.
Committing to: /home/jal/test/a/
missing a/b
modified a/b
missing a/b/c
modified a/b/c
missing a/b/c/d
modified a/b/c/d
missing a/b/c/d/file
modified a/b/c/d/file
Missing checkcommit.jar, not checking commits.
bzr: ERROR: exceptions.KeyError: 'c-20100223092848-lv5tl8m8u8au91dd-3'
*** Bazaar has encountered an internal error. This probably indicates a
bug in Bazaar. You can help us fix it by filing a bug report at https://bugs.launchpad.net/bzr/+filebug
attaching the crash file /home/jal/.cache/crash/bzr-20100223092848-27410.crash
and including a description of the problem.
The crash file is plain text and you can inspect or edit it to remove
private information.
This is not exactly building confidence- bzr now aborts in this way for *every* remove of a tree structure. I added a trivial script to illustrate the problem: KeyError: 'c-201002230928 48-lv5tl8m8u8au 91dd-3'
jal@odeon:~$ ./trivial
Created a standalone tree (format: 2a)
adding a
adding a/b
adding a/b/c
adding a/b/c/d
adding a/b/c/d/file
Committing to: /home/jal/test/a/
added a
added a/b
added a/b/c
added a/b/c/d
added a/b/c/d/file
Missing checkcommit.jar, not checking commits.
Committed revision 1.
Committing to: /home/jal/test/a/
missing a/b
modified a/b
missing a/b/c
modified a/b/c
missing a/b/c/d
modified a/b/c/d
missing a/b/c/d/file
modified a/b/c/d/file
Missing checkcommit.jar, not checking commits.
bzr: ERROR: exceptions.
*** Bazaar has encountered an internal error. This probably indicates a /bugs.launchpad .net/bzr/ +filebug
/home/ jal/.cache/ crash/bzr- 20100223092848- 27410.crash
bug in Bazaar. You can help us fix it by filing a bug report at
https:/
attaching the crash file
and including a description of the problem.
The crash file is plain text and you can inspect or edit it to remove
private information.