Parcival
11-23-2004, 04:18 AM
Recently I have repeatedly experienced the problem that
emerge <insert-program-name-here>
would terminate after the download with the error message that the md5 check failed. Usually I solve this problem by removing the downloaded archive and emerge the whole thing a couple days later again. However, right now I have several times tried for the last week to emerge OpenOffice 1.1.3 to put it on a friends box, but it keeps failing the check.
So here my questions:
[list=1]
Anyone out there experiencing the same problems?
Does this problem only concern my mirror (ftp://mirror.switch.ch/mirror/gentoo/) or is it a general error in all portage packages all over the world?
I haven't been able to locate the md5 files in /usr/portage/distfiles nor on the server, so where do they actually reside? Could it be that the md5 mismatch got fixed and I still have the old md5 file sitting somewhere on my disk, thus automatically failing the test after redownloading the whole archive?
If the last question is true, how come it did work earlier when I just deleted the archive and emerged the whole package again? I think portage does the md5 check before untarring the archive, which really does make sense, but where does it get the md5 checksum file since it's not provided together with the archive in distfiles?
[/list=1]
Thanks for enlightening me. :)
emerge <insert-program-name-here>
would terminate after the download with the error message that the md5 check failed. Usually I solve this problem by removing the downloaded archive and emerge the whole thing a couple days later again. However, right now I have several times tried for the last week to emerge OpenOffice 1.1.3 to put it on a friends box, but it keeps failing the check.
So here my questions:
[list=1]
Anyone out there experiencing the same problems?
Does this problem only concern my mirror (ftp://mirror.switch.ch/mirror/gentoo/) or is it a general error in all portage packages all over the world?
I haven't been able to locate the md5 files in /usr/portage/distfiles nor on the server, so where do they actually reside? Could it be that the md5 mismatch got fixed and I still have the old md5 file sitting somewhere on my disk, thus automatically failing the test after redownloading the whole archive?
If the last question is true, how come it did work earlier when I just deleted the archive and emerged the whole package again? I think portage does the md5 check before untarring the archive, which really does make sense, but where does it get the md5 checksum file since it's not provided together with the archive in distfiles?
[/list=1]
Thanks for enlightening me. :)