Bugzilla Bug 70449

I got 
!!! Digest verification Failed:
!!!    /usr/portage/distfiles/fp-linux-ws-4.4.7.tar.gz
!!! Reason: Filesize does not match recorded size
upon trying to emerge f-prot. I downloaded the source from another computer, and checked MD5 sums, they are self consistant, but different to the ones in the Manifest for f-prot.

Have the sources changed without the version number changing? Or am I getting download errors?

Reproducible: Always
Steps to Reproduce:
1.emerge f-prot
2.
3.

Actual Results:  
!!! Digest verification Failed:
!!!    /usr/portage/distfiles/fp-linux-ws-4.4.7.tar.gz
!!! Reason: Filesize does not match recorded size

OK, I have compared package downloaded from f-prot.com and one living on gentoo
mirrors, and they only differ in virus definition files:

$ diff -burN f-prot.mirror/ f-prot.orig/        
Files f-prot.mir/MACRO.DEF and f-prot.orig/MACRO.DEF differ
Files f-prot.mir/SIGN.DEF and f-prot.orig/SIGN.DEF differ
Files f-prot.mir/SIGN2.DEF and f-prot.orig/SIGN2.DEF differ

I assume Frisk software updated virus definitions in the tarball, probably to
be synced with yesterday's release of f-prot for Solaris SPARC
(http://www.f-prot.com/news/gen_news/041008_release_sol_sparc.html).

I have just committed new digest for 4.4.7 into CVS portage. It should hit
portage mirrors in few hours. In the meantime, safe digest is:

e1871c0c0c8481f121fdbc1adbd2ce2b  fp-linux-ws-4.4.7.tar.gz

Thanks for reporting this, Anthony.

I'm not entirely sure, but this sounds like the same problem...

When doing 'emerge f-prot' I get:

Calculating dependencies ...done!
>>> emerge (1 of 1) app-antivirus/f-prot-4.4.7 to /
>>> Downloading http://gentoo.osuosl.org/distfiles/fp-linux-ws-4.4.7.tar.gz
--12:44:13--  http://gentoo.osuosl.org/distfiles/fp-linux-ws-4.4.7.tar.gz
           => `/usr/portage/distfiles/fp-linux-ws-4.4.7.tar.gz'
Resolving gentoo.osuosl.org... 140.211.166.134
Connecting to gentoo.osuosl.org[140.211.166.134]:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 2,744,938 [application/x-gzip]

100%[===============================================>] 2,744,938     59.95K/s    ETA 00:00

12:44:41 (97.31 KB/s) - `/usr/portage/distfiles/fp-linux-ws-4.4.7.tar.gz' saved [2744938/2744938]


!!! Digest verification Failed:
!!!    /usr/portage/distfiles/fp-linux-ws-4.4.7.tar.gz
!!! Reason: Failed on MD5 verification

'md5sum /usr/portage/distfiles/fp-linux-ws-4.4.7.tar.gz' gives:
9cde7ca8ce6862de640f3f88379897b2  /usr/portage/distfiles/fp-linux-ws-4.4.7.tar.gz

Just to be sure I tried a few different mirrors, but they all give the same error.

Looks like mirrors refuse to update the tarball from upstream site. I'll look
into it, thanks.

For now, I have put RESTRICT="nomirror" to the 4.4.7 ebuild, so portage always
fetches it from upstream site. I'll try to get the invalid tarball off our
mirrors.

This has been done already, forgot to close.