I've found an old discussion saying that there are major problems with the file server. Indeed on 2012-02-28, I got an error:
bunzip2: Data integrity error when decompressing. Input file = mpfr-0-8054.bz2, output file = (stdout) (when I tested bunzip2 manually, I think, but I'm not sure). However concerning the problem that occurred yesterday, I got no data integrity errors. Now, the way bunzip2 does integrity checking when decompressing is poorly documented: does bunzip2 guarantee that every byte from the stream is correct (e.g. integrity checking is done chunk by chunk, and a chunk is output only once CRC checking has been done on it) or does one need to wait for the decompression of the full file to detect a possible integrity error? If this is the latter, then the problem could come from the file server, because my own MD5 checking has detected the problem before the file has entirely been decompressed. In such a case, I would need to modify my script for better information on the failure. -- Vincent Lefèvre <vinc...@vinc17.net> - Web: <http://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <http://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
