Emerging neverball-1.4.0 fails because (I assume) the stored digest (md5) does not match the digest of the downloaded file >>> emerge (1 of 1) games-puzzle/neverball-1.4.0 to / !!! File is corrupt or incomplete. (Digests do not match) >>> our recorded digest: 2ea124706cf290027b44fc23f48f3096 >>> your file's digest: a6cd860f1c2b7d8cecbcfc05ff228ef0 !!! File does not exist: /usr/portage/distfiles//neverball-1.4.0.tar.gz Either the file on the download sever is corrupted or the stored digest needs updating (via emerge rsync).
stealth update from upstream. fixed.
It doesn't seem to be fixed at all. !!! File is corrupt or incomplete. (Digests do not match) >>> our recorded digest: a6cd860f1c2b7d8cecbcfc05ff228ef0 >>> your file's digest: c548435d3cb1c41a1c72e938d334d63e !!! File does not exist: /usr/portage/distfiles//neverball-1.4.0.tar.gz ...after removing /usr/portage/distfiles//neverball-1.4.0.tar.gz, emerge sync and remerging neverball (fetching from http://distro.ibiblio.org/pub/Linux/distributions/gentoo/distfiles/neverball-1.4.0.tar.gz)
The upstream digest is a6cd860f1c2b7d8cecbcfc05ff228ef0
I believe the file is corrupt on the mirrors.
OK, I downloaded the neverball-1.4.0.tar.gz from http://icculus.org/neverball/#download with firefox. Then I did `ebuild /usr/portage/games-puzzle/neverball/neverball-1.4.0.ebuild digest` The files/digest-neverball-1.4.0 wasn't updated correctly, so I manually edited it to read: MD5 a6cd860f1c2b7d8cecbcfc05ff228ef0 neverball-1.4.0.tar.gz 11314294 ...and then the emerge was successful.
I got the same problem and bad md5 as Peter Ruskin today (2004-10-02). I sync'd right before, so this bug is still happening. Shouldn't be marked resolved.
Looks like this bug has not been fixed. I will re-open.
The md5sum is correct in portage.
OK, it's working today.
I just removed my old neverball-1.4.0.tar.gz, synced at 9:30 CST and re-emerged. Portage downloaded http://mirrors.tds.net/gentoo/distfiles/neverball-1.4.0.tar.gz. and got this message !!! File is corrupt or incomplete. (Digests do not match) >>> our recorded digest: a6cd860f1c2b7d8cecbcfc05ff228ef0 >>> your file's digest: c548435d3cb1c41a1c72e938d334d63e !!! File does not exist: /usr/portage/distfiles//neverball-1.4.0.tar.gz If it helps, this was on the neverball website: "Yes, two different 1.4.0 packages were uploaded on September 15 and 16. There was a trivial mistake that I didn't feel warranted a patch number bump. However, I realize now that many people check MD5 sums and noted the swap. Sorry!" I noticed that two different md5 sums have been reported in this bug. Maybe both versions of the package are in portage?