Comment 6 for bug 239499

Perhaps you are confusing this bug with another one. I have never to my knowledge run `check' until trying to upgrade to rich-root-pack, which runs check for you. Now I realize that check fails. Probably it has been failing for some time, just that I didn't know. In the IRC log, jam suggests:

<jam> wingo-tp: so what it *could* be, is that at one point you did a conversion with a different amount of history
<jam> which caused the "last-modified" fields in the inventories to differ
<jam> at some point after that, the branches were merged together
<jam> and they didn't notice that the inventories they were referencing had a different text
<jam> and so they pulled across a delta which technically only applies to the *other* base
<jam> and thus when applied to this base, the sha-1 doesn't match
<jam> I would have thought you would encounter the error sooner rather than later
<jam> I probably can hack something together as a workaround, but a real fix is probably a bit involved.

This does appear to coincide with what I did, two years ago. Likely the bug was in the conversion tool (although given that it was a tla/baz import, you'd figure that those tools would be better than the rest). Anyway, I'm a bit stuck, and some way to fix my repo would be greatly appreciated.