This only occurs if the old version of framework-2.4.tar.gz is left in the distfiles directory. Removing this file and emerging fixes the issue, but it would be nice if this was detected automatically... outernet ~ # emerge metasploit Calculating dependencies ...done! >>> emerge (1 of 1) net-analyzer/metasploit-2.4-r1 to / * Adjusting permissions on ccache in /home/scratch/ccache >>> md5 files ;-) metasploit-2.4-r1.ebuild >>> md5 files ;-) metasploit-2.3-r2.ebuild >>> md5 files ;-) files/digest-metasploit-2.4-r1 >>> md5 files ;-) files/msfweb.initd >>> md5 files ;-) files/digest-metasploit-2.3-r2 >>> md5 files ;-) files/msfweb.confd !!! Digest verification Failed: !!! /usr/portage/distfiles/framework-2.4.tar.gz !!! Reason: Failed on MD5 verification Reproducible: Always Steps to Reproduce: 1.Go to a system with metasploit-2.4 installed 2. Sync and emerge metasploit 3. Watch the MD5 sum fail on the previously downloaded file Actual Results: Digest verification Failed: Expected Results: Successful merge If anything, this is my fault for not changing the file name on the updated package, still annoying though :-) Is there a way in portage to say "this file and not that file" with the same name in the distfiles cache?
There's nothing that can be done automatically. The md5sum check is there for your protection. You need to remove the file that fails the check and continue.
