Downloading from download.virtualbox.org: $ ls -l VirtualBox-4.2.8.tar.bz2 -rw-r--r-- 1 christophe christophe 76412088 Feb 28 11:22 VirtualBox-4.2.8.tar.bz2 $ sha256sum VirtualBox-4.2.8.tar.bz2 f336af12244db74e6564dc22e438bbcba70f994aaf0d117fdf70caca9fab1b78 VirtualBox-4.2.8.tar.bz2 Downloading from distfiles.g.o: $ ls -l /usr/portage/distfiles/VirtualBox-4.2.8.tar.bz2 -rw-rw-r-- 1 portage portage 76420670 Feb 27 21:50 /usr/portage/distfiles/VirtualBox-4.2.8.tar.bz2 $ sha256sum /usr/portage/distfiles/VirtualBox-4.2.8.tar.bz2 bc9185e0c300d61e2a6c8ac48b4bea6a0a456c9ba11d1fbadf2d1e6ca063f2b4 /usr/portage/distfiles/VirtualBox-4.2.8.tar.bz2 I noticed this when yesterday, distfiles.g.o was not yet serving this file, resulting in a download from upstream and a digest failure. This would mean the current ebuild cannot be used when for some reason the Gentoo mirrors are down or stop serving these sources. Reproducible: Always
What I think happened here is that upstream changed the tarball after they released it. And this is why you get a different digest
(In reply to comment #1) > What I think happened here is that upstream changed the tarball after they > released it. And this is why you get a different digest That's exactly what happened. I'm woring on it (have to change more than just app-emulation/virtualbox ebuild -.-).
Thanks for your swift action :)
(In reply to comment #3) > Thanks for your swift action :) Thank you for reporting this issue :) + 01 Mar 2013; Lars Wendler <polynomial-c@gentoo.org> virtualbox-4.2.8.ebuild: + Upstream replaced the source tarball once again (bug #459842). Removed + useless code from ebuild. + Should be fixed now. Please wait a while until the mirrors have picked up the new tarball...