Yes, I believe that is what happened. I live in a rural area and have a flaky but fairly fast internet connection (given my distance from the exchange 150kb is fast) and I often see this kind of error or worse when I attempt an upgrade.
Sometimes it takes quite a few attempts (I repeated the mysql server deb download this morning and its worked). This time the consequences were not serious because the failure appears to have been 'clean' but on many occasions the attempt to load the corrupt file results in system corruption that can sometimes be a real headache to fix. A built in checksum on the deb files before an attempt is made to load them (ideally with the higher level applications like synaptic giving the option to reload the deb) would eliminate this problem. I don't know but I am willing to bet there are an awful lot of bugs raised because of this problem. I know I get the "submit a bug" option so often because of it that I rarely file it. This one was particularly frustrating (I depend on mysql-server a lot and it was a big file) so I thought I'd flag it again. If its coming to the wrong group then perhaps the reporting process for bugs can be changed so that corrupt downloaded file errors are caught and punted somewhere else? -- package mysql-server-5.0 5.1.30really5.0.75-0ubuntu10.2 failed to install/upgrade: corrupted filesystem tarfile - corrupted package archive https://bugs.launchpad.net/bugs/520170 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
