The digest entry for profuse-0.15.tar.bz2 appears to be incorrect. The entry is: MD5 2f5b3b896a3bbe2eb516cc5031e5d5d5 profuse-0.15.tar.bz2 17556 The actual profuse-0.15.tar.bz2 file retrieved from libconf.net (and at least one of itsmirrors) is 17545 bytes in length with an MD5 sum of 221be54a1f54850eb62bf59343be244b The size mismatch causes portage to attempt to retrieve the "missing" 11 bytes, which of course fails.
Can confirm what, locally > ebuild profuse-0.15.ebuild digest fixes that...
Yes, running ebuild "/usr/portage/app-portage/profuse/profuse-0.15.ebuild digest" will generate a correct digest file that allows profuse to be emerged: MD5 221be54a1f54850eb62bf59343be244b profuse-0.15.tar.bz2 17545 This needs to be updated in the portage tree, though, otherwise the next "emerge sync" will replace the digest file with the broken one.
corrected