!!! File is corrupt or incomplete. (Digests do not match) >>> our recorded digest: d7830bdf1e05d8395794f75097d291be >>> your file's digest: 8a2c4a256c8d4a8dfa373b16cceccba9 !!! File does not exist: /usr/portage/distfiles//atk-1.4.1.tar.bz2 The fetched tarball is not broken, but I wonder if this could have something to do with the gnome.org intrusion, lately. Reproducible: Always Steps to Reproduce: 1. 2. 3.
Master mirror has the following digest: eagle distfiles # md5sum atk-1.4.1.tar.bz2 2ad7c7d6921446226f687bd935df5be5 atk-1.4.1.tar.bz2 which is "none of the above" Doesn't appear to be a security problem and I don't *think* it's a mirror problem -- kicking over to gnome team for now. Carlo -- can you post some more info? What source mirror are you pulling from, what were you emerging at the time, etc.
lcars just informed me that the file, when pulled directly from ftp.gnome.org, matches the recorded digest in the ebuild. That doesn't match the digest of the file on our master mirror, however, nor does it match the digest that Carlo reported when he d/l'ed the file. Gnome team -- can you verify that there's no funkiness with the tarball? Given the recent compromise of ftp.gnome.org, I'd rather be extra cautious. Once you've blessed it, assign to mirror-admins and we'll take care of replacing the file on the master mirror with the corrected version.
it was ftp.sunet.se - fetched only the one ebuild, a second try (ftp.no.gnome.org) and the checksums matched. >which is "none of the above" you're sure portage prints the correct checksum? ;)
no this is alright, the ebuild even contains nomirror so that it should only fetch the gnome.org one for this reason. In theory it shouldn't differ between gnome servers, but thats hard to verify.
Fetched the tarball from ftp.sunet.se again, this time it was correct. Sorry for the false alert.
