digest-emul-linux-x86-xlibs-7.0-r1 contains the following details for emul-linux-x86-xlibs-7.0-r1.tar.bz2: MD5 0b4050967f6e0d50dfafe00c8d3bb3e3 emul-linux-x86-xlibs-7.0-r1.tar.bz2 3232719 RMD160 ba99f0ba6e1e24dac60d6f4c12bdd7b4a33fefc5 emul-linux-x86-xlibs-7.0-r1.tar.bz2 3232719 The downloaded file (only available at the gentoo.osuosl.org mirror at time of writing) is only 3208380 bytes long; portage tries to continue the download, but eventually runs out of mirrors to try. The file appears to be complete (tar extracts the contents without errors), so it doesn't appear to be an incomplete upload of the file to the mirror. # emerge -f emul-linux-x86-xlibs [snip] >>> Downloading http://gentoo.oregonstate.edu/distfiles/emul-linux-x86-xlibs-7.0-r1.tar.bz2 --06:36:41-- http://gentoo.oregonstate.edu/distfiles/emul-linux-x86-xlibs-7.0-r1.tar.bz2 => `/usr/portage/distfiles/emul-linux-x86-xlibs-7.0-r1.tar.bz2' Resolving gentoo.oregonstate.edu... 64.50.236.52, 64.50.238.52 Connecting to gentoo.oregonstate.edu|64.50.236.52|:80... connected. HTTP request sent, awaiting response... 301 Moved Permanently Location: http://gentoo.osuosl.org/distfiles/emul-linux-x86-xlibs-7.0-r1.tar.bz2 [following] --06:36:41-- http://gentoo.osuosl.org/distfiles/emul-linux-x86-xlibs-7.0-r1.tar.bz2 => `/usr/portage/distfiles/emul-linux-x86-xlibs-7.0-r1.tar.bz2' Resolving gentoo.osuosl.org... 64.50.236.52, 64.50.238.52 Reusing existing connection to gentoo.oregonstate.edu:80. HTTP request sent, awaiting response... 200 OK Length: 3,208,380 (3.1M) [application/x-tar] 100%[====================================>] 3,208,380 492.34K/s ETA 00:00 06:36:49 (432.22 KB/s) - `/usr/portage/distfiles/emul-linux-x86-xlibs-7.0-r1.tar.bz2' saved [3208380/3208380] >>> Resuming download... [snip]
Same here, excpet mirrors.acm.cs.rpi.edu claims the file is 3,232,719 bytes long, as opposed to gentoo.osuosl.org (and mirror.datapipe.net) claiming 3,208,380 bytes. !!! Digest verification Failed: !!! /usr/portage/distfiles/emul-linux-x86-xlibs-7.0-r1.tar.bz2 !!! Reason: Failed on RMD160 verification !!! Got: 6a8256bde25859d86444b286a8913b30f4d642dd !!! Expected: ba99f0ba6e1e24dac60d6f4c12bdd7b4a33fefc5
Really not sure what happended there tbh. Checked the file on a couple of different mirrors this morning and everything seems fine, digests match. Re-download the file if you have to.
*** Bug 127058 has been marked as a duplicate of this bug. ***