Comment 4 for bug 295161

I think we have seen similar problems before and had thought they were caused by a one-off error such as a memory bit error rather than a bug in bzr. If they have created a new revision with this problem and especially if this can be done reproducibly that would indicate a problem writing the data.

If it's an unreproducible glitch then it may be reasonable to have bzrlib be a bit defensive if it's unable to read them, and give a warning rather than an exception.