Comment 1 for bug 1343313

This is/was probably due to an incomplete bandersnatch sync. Bandersnatch should fix itself on the next run, but we can probably make it fail more gracefully when it notices md5sums don't match.

Its also possible that there were network bit flips and the md5sum check saved us from all kinds of nastyness. If that is the case I don't think there is much we can do about this bug.