Comment 2 for bug 489211

This bears some resemblance to bug 437626, but it appears to be a different bug because a) it happens with 2a repositories, and b) bug 437626 is fixed in bzr 2.0.2, which the reporter is using.

I'm pretty concerned that this is happening. Also, experience from bug 437626 suggests that it will be quite hard to reproduce and thus diagnose. Is it possible to get a tarball of the repository/repositories that we can use to reproduce the error? I see you say you've manually repaired the repository by fetching some revisions manually, if you don't have an unrepaired copy around that still reproduces, then tarball taken as soon as possible after the repair may still help.