"emerge mirroselect" --> Failed md5 verificatio

Message

scubacuda · Post by **scubacuda** » Thu Dec 09, 2004 7:05 am

Whenever I run "emerge mirrorselect," I get:

!!! Digest verification failed:
!!!     /usr/portage/distfiles/dialog_1.0-20040731.orig.tar.gz
!!!     Reason: Failed on MD5 verification

Any suggestions?

update: I fixed it; here's what worked

Code: Select all

#cd /usr/portage/distfiles/
#rm dialog_1.0-20040731.orig.tar.gz
#emerge -f mirrorselect
#emerge mirrorselect

BWoso · Post by **BWoso** » Thu Dec 09, 2004 7:34 am

emerge -f mirrorselect
emerge mirrorselect

The package was not downloaded properly and emerge -f will re-fetch the package then emerge will install (or whatever the proper word is) it.

Genone · Post by **Genone** » Thu Dec 09, 2004 8:09 am

BWoso wrote:emerge -f mirrorselect
emerge mirrorselect

The package was not downloaded properly and emerge -f will re-fetch the package then emerge will install (or whatever the proper word is) it.

wrong.
emerge -f will not refetch it if the file is already there, you have to delete it manually first, so the emerge -f is redundant.

scubacuda · Post by **scubacuda** » Thu Dec 09, 2004 8:13 am

Genone wrote:wrong. emerge -f will not refetch it if the file is already there, you have to delete it manually first, so the emerge -f is redundant.

So

Code: Select all

#cd /usr/portage/distfiles/
#rm dialog_1.0-20040731.orig.tar.gz

?

Genone · Post by **Genone** » Thu Dec 09, 2004 8:21 am

BWoso · Post by **BWoso** » Thu Dec 09, 2004 8:26 am

every time that I have gotten the error of a bad md5 sum doing emerge -f then emerge fixed the problem, so sorry if I was wrong, I was just stating what worked for me in the past.

Genone · Post by **Genone** » Thu Dec 09, 2004 8:27 am

sure you don't confuse emerge -f and emerge --sync ?

BWoso · Post by **BWoso** » Thu Dec 09, 2004 8:54 am

yes . . . I may just be confusing errors, the times when I would run the emerge -f command was when I got errors like this

Code: Select all

!!! File is corrupt or incomplete. (Digests do not match)
>>> our recorded digest: 8a2d8f1ed5a2909da04132fefa44905e
>>>  your file's digest: 326f95c3a6f759a7d6c6c19baffa9744

which may be different from a bad md5 sum. . . or maybe it has been updated in portage since the last time I got an error like this.

Lindsey · Post by **Lindsey** » Tue Jan 04, 2005 5:16 am

BWoso wrote:every time that I have gotten the error of a bad md5 sum doing emerge -f then emerge fixed the problem, so sorry if I was wrong, I was just stating what worked for me in the past.

Thanks, that did the trick for me in a similar situation.

gnac · Post by **gnac** » Tue Feb 08, 2005 2:37 am

doing an "emerge -f packagename" also helped resolve an md5 verification error I was having with museseq.

I had tried removing the tar file from /usr/portage/dirstfiles, but whenever I tried to emerge the package, emerge would grab the same file from the first mirror in /etc/make.conf.

emerge -f also retrieved the file from the first mirror, but when the md5 check determined that the package was bad, "emerge -f" went to the next mirror in my list, and then the third until it finally got a "valid" package.
A second call to emerge installed the package downloaded with the -f switch.

Thanks

Rusty_man · Post by **Rusty_man** » Thu Feb 10, 2005 5:57 pm

yeah emerge -f worked for me as well, same md5 verification error as well. So thanks for posting that solution.