Crash (and corruption?) after reverting an added directory

John Arbash Meinel john at
Mon Apr 27 15:54:55 BST 2009

Hash: SHA1

> # argh: just rm'ing the files did not remove them from bzr's radar, of
> course. duh.
> # rewind again.
> bzr revert .
> This last "revert" seems to be where everything goes off the rails.
> Specifically, the output from that command is
> -D  pkg/
> -   pkg/
> -   pkg/
> -   pkg/sub
> bzr: ERROR: An inconsistent delta was supplied involving 'pkg/sub',
> 'sub-20090426182712-gp9wgeideu9o5x1f-4'
> reason: The file id was deleted but its children were not deleted.
> That's a pretty inscrutable error message to a newbie like me.  But it
> gets worse:

^- it is inscrutable because it is an internal error. (aka, something
you should never see...)

Specifically, it looks like somehow we decided to remove 'pkg/sub' but
failed to remove 'pkg/sub/'

Now possibly the problem is just one of ordering. That we get to pkg/sub
*before* we get to pkg/sub/

However, I was pretty sure that 'apply_delta' was order agnostic, and we
only checked the correctness after applying the entire delta. (I could
be wrong.)

> Now this branch is hosed: most commands fail with the above stack
> trace.  "bzr check" blows up with
> Checking working tree at 'file:///tmp/bzr-fastimport/'.
> bzr: ERROR: exceptions.AssertionError: no parent entry for:
> fastimport/ in tree 0

^- I assume this is on the 'real' occurrence, and not the test one you
mentioned before :).

Anyway, this is probably the same delta issue as above. Somehow we
managed to remove 'fastimport/' the directory, without removing
'' from being tracked.

Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla -


More information about the bazaar mailing list