Comment 1 for bug 177874

Here is the problem:

Most of inventories in bzr.dev have root IDs "TREE_ROOT", but a branch starting from "<email address hidden>" has inventories with root ID "tree_root-20070410133226-3795pjcs6oz73ncz-1". This branch was merged to bzr.dev without a common ancestry in revision "<email address hidden>". But that means that one parent of "<email address hidden>" points to the versioned file "%54%52%45%45_%52%4f%4f%54", the other one to "tree_root-20070410133226-3795pjcs6oz73ncz-1".

I'm not sure what is the right solution here: either can be repositories that don't support rich roots normalized to ROOT_ID, or can be parents of "<email address hidden>" added as ghosts, but I think this will break other things. What I'm wondering about is how this could happen, though. I see that WorkingTree4 generates a new root ID only for repositories that do support rich roots.