Nilesh Patra writes: > This looks just... weird. Would someone know why this happens?
Someone uploaded a broken .changes file that had different sizes for the same file: +--- | Checksums-Sha256: | [...] | 209dda5709e1a67eab2762013136adc7c3b6977a17a7e3d8a12f5b2c27569875 156580 [...] | Files: | [...] | cda6f0841c01ae3ffb3f9584ba9c5f20 157910 science optional [...] +--- The error handling in the archive software is not very good for this error: it stops processing, thus all .changes files sorted after this one did not get processed. The file was now moved away. Anyway, people should *not* edit .changes files manually as it is too easy to refer to the wrong files, e.g., a different .orig tarball than was used to build the package. I suspect someone did manually edit the file here. Ansgar
