Emerging kde-base/kjsembed-3.4.2, portage downloaded kdebindings-3.4.2.tar.bz2 but the downloaded file had digest MD5 1ee2348e03b0af625679d0bb2c8aad2b kdebindings-3.4.2.tar.bz2 7214122 while 6 files in /usr/portage/kde-*/*/files/digest-* all state MD5 e00c0a974b8e50899c8e6e031277deba kdebindings-3.4.2.tar.bz2 721370 I had the same problem yesterday, and I did a sync just now. Is the information in the portage tree incorrect, did KDE change the file on the server, has some server been hacked, or is someone hacking my network connection? 12:36:08 (6.56 KB/s) - `/usr/portage/distfiles/kdebindings-3.4.2.tar.bz2' saved [7,214,122] !!! Fetched file: kdebindings-3.4.2.tar.bz2 VERIFY FAILED! !!! Reason: Filesize does not match recorded size Removing corrupt distfile... >>> Downloading ftp://ftp.kde.org/pub/kde/stable/3.4.2/src/kdebindings-3.4.2.tar.bz2
several days later, this is still happening.
Yep, it's getting pretty annoying... Looks like a lot of ebuilds use a bogus MD5. Want me to draw up a list of all the offending ebuilds?
It was number two: KDE changed the file on the server. Should be fixed now.