Why does 'emerge -f' remove fetched file when its digest does not match? Next time I would be happy, if the just fetched file remains in the distfiles directory. Please, implement this functionality. Thanks a lot. Reproducible: Always Steps to Reproduce: I downloaded eclipse-sourceBuild-srcIncluded-3.0RC3.zip with prozgui-2.0.5. However the MD5 checksum of that file did not match with the digest. The file seemed correct and I did not want to wait for the digest record correction. So I regenerated the digest with ebuild and start emerge. A lot of errors about bad ZIP file offset during decompression appeared. Ok, the file was really corrrupted I deleted it from the distfiles directory and fetched it again, but now with 'emerge -f'. You can imagine my face when I saw this message: :-)) 16:30:55 (5.35 KB/s) - `/usr/portage/distfiles/eclipse-sourceBuild-srcIncluded-3 .0RC3.zip' ulo
Why does 'emerge -f' remove fetched file when its digest does not match? Next time I would be happy, if the just fetched file remains in the distfiles directory. Please, implement this functionality. Thanks a lot. Reproducible: Always Steps to Reproduce: I downloaded eclipse-sourceBuild-srcIncluded-3.0RC3.zip with prozgui-2.0.5. However the MD5 checksum of that file did not match with the digest. The file seemed correct and I did not want to wait for the digest record correction. So I regenerated the digest with ebuild and start emerge. A lot of errors about bad ZIP file offset during decompression appeared. Ok, the file was really corrrupted I deleted it from the distfiles directory and fetched it again, but now with 'emerge -f'. You can imagine my face when I saw this message: :-)) 16:30:55 (5.35 KB/s) - `/usr/portage/distfiles/eclipse-sourceBuild-srcIncluded-3 .0RC3.zip' uloeno [52915397/52915397] !!! Fetched file: eclipse-sourceBuild-srcIncluded-3.0RC3.zip MD5 FAILED! Removin g corrupt distfile... !!! Couldn't download eclipse-sourceBuild-srcIncluded-3.0RC3.zip. Aborting. !!! Fetch for /usr/portage/dev-util/eclipse-sdk/eclipse-sdk-3.0.0_rc3.ebuild fai led, continuing... !!! Some fetch errors were encountered. Please see above for details.
Prozilla is a multi threaded download program iirc. You may be experiencing some byte corruptions of some sort due to this. Try using wget instead and see what happens.
> Prozilla is a multi threaded download program iirc. > You may be experiencing some byte corruptions of some sort due to this. > Try using wget instead and see what happens. >> ... and fetched it again, but now with 'emerge -f'. This was with standard FETCHCOMMAND (wget). Yes, it is my fault, that I used a multithreaded downloader for the first download, but I do not know why the just downloaded file with bad MD5 checksum has been deleted from the distfiles directory. If it is a portage feature, I think, it should be removed.
It's not a bug, it's a feature :-) That feature was apparently added to make it easier for people with unstable connections, and to ensure people didn't just update the digest and possibly compromise their systems. Besides, if a file is corrupted, you don't want to be messing with it unless you're a developer. And if you're a developer, you know what to do in order to work around this "issue" ...
Not a bug.
