The k3b-0.11.24.tar.bz2 file (required for k3b) is corrupted in the ftp://ftp.rnl.ist.utl.pt/pub/gentoo mirror (poruguese). The file size is slightly bigger and the md5sum doesn't match the digest. It can also be on other mirrors from the same university, like http://darkstar.ist.utl.pt/gentoo (but i havent tested them..) After trying other mirrors no problem occurred. Reproducible: Always Steps to Reproduce: 1.emerge k3b 2. 3. Actual Results: portage complaint abot filesize. If the filesize is manually corrected on the digest, it then complains about md5sum. Expected Results: It should have passed the portage security test.
Race condition where our master mirror is syncing at the same time as the file is being uploaded to the staging mirror. Problem usually fixes itself on the next sync. I just tested and works fine for me.
Nop. I just tested again and it didn't work. I deleted the working file (from another server) and restored my old server list, and the fetched file was bad (wrong filesize). Please check that you have the most recent portage security check enabled.. The filesize is still different, even though it may not be really corrupted, so if the filesize check isn't made it still can emerge. Also, I'm talking about the ~x86 version of k3b and not the stable one.
I can confirm this issue. Freshly emerge sync'd as well. ebuild k3b-0.11.24.ebuild digest corrects the problem (tarball has changed) new MD5 appears to be: cf1111472487e4da87c649525e5987f6 sunyata k3b # ACCEPT_KEYWORDS="~x86" emerge k3b Calculating dependencies ...done! >>> emerge (1 of 1) app-cdr/k3b-0.11.24 to / >>> md5 files ;-) k3b-0.12_beta2.ebuild >>> md5 files ;-) k3b-0.12_beta1.ebuild >>> md5 files ;-) k3b-0.11.24.ebuild >>> md5 files ;-) ChangeLog >>> md5 files ;-) k3b-0.11.23-r2.ebuild >>> md5 files ;-) metadata.xml >>> md5 files ;-) files/digest-k3b-0.12_beta1 >>> md5 files ;-) files/digest-k3b-0.12_beta2 >>> md5 files ;-) files/digest-k3b-0.11.23-r2 >>> md5 files ;-) files/k3b-0.11.17-noarts.patch >>> md5 files ;-) files/digest-k3b-0.11.24 >>> md5 files ;-) files/k3b-dvdrip-transcode.patch !!! Digest verification Failed: !!! /usr/portage/distfiles/k3b-0.11.24.tar.bz2 !!! Reason: Filesize does not match recorded size sunyata k3b # ebuild k3b-0.11.24.ebuild digest >>> Downloading http://gentoo.osuosl.org/distfiles/k3b-i18n-0.11.tar.bz2 --20:02:08-- http://gentoo.osuosl.org/distfiles/k3b-i18n-0.11.tar.bz2 => `/usr/portage/distfiles/k3b-i18n-0.11.tar.bz2' 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,738,463 [application/x-tar] 100%[==================================================================================================================>] 2,738,463 298.77K/s ETA 00:00 20:02:17 (302.33 KB/s) - `/usr/portage/distfiles/k3b-i18n-0.11.tar.bz2' saved [2738463/2738463] >>> Generating digest file... <<< k3b-0.11.24.tar.bz2 <<< k3b-i18n-0.11.tar.bz2 >>> Generating manifest file... <<< k3b-0.12_beta2.ebuild <<< k3b-0.12_beta1.ebuild <<< k3b-0.11.24.ebuild <<< ChangeLog <<< k3b-0.11.23-r2.ebuild <<< metadata.xml <<< files/digest-k3b-0.12_beta1 <<< files/digest-k3b-0.12_beta2 <<< files/digest-k3b-0.11.23-r2 <<< files/k3b-0.11.17-noarts.patch <<< files/digest-k3b-0.11.24 <<< files/k3b-dvdrip-transcode.patch >>> Computed message digests. sunyata k3b # ACCEPT_KEYWORDS="~x86" emerge k3b Calculating dependencies ...done! >>> emerge (1 of 1) app-cdr/k3b-0.11.24 to / >>> md5 files ;-) k3b-0.12_beta2.ebuild >>> md5 files ;-) k3b-0.12_beta1.ebuild >>> md5 files ;-) k3b-0.11.24.ebuild >>> md5 files ;-) ChangeLog >>> md5 files ;-) k3b-0.11.23-r2.ebuild >>> md5 files ;-) metadata.xml >>> md5 files ;-) files/digest-k3b-0.12_beta1 >>> md5 files ;-) files/digest-k3b-0.12_beta2 >>> md5 files ;-) files/digest-k3b-0.11.23-r2 >>> md5 files ;-) files/k3b-0.11.17-noarts.patch >>> md5 files ;-) files/digest-k3b-0.11.24 >>> md5 files ;-) files/k3b-dvdrip-transcode.patch >>> md5 src_uri ;-) k3b-0.11.24.tar.bz2 >>> Unpacking source... >>> Unpacking k3b-0.11.24.tar.bz2 to /var/tmp/portage/k3b-0.11.24/work * Applying k3b-0.11.17-noarts.patch ... [ ok ] . . . sunyata k3b # cat files/digest-k3b-0.11.24 MD5 cf1111472487e4da87c649525e5987f6 k3b-0.11.24.tar.bz2 3202909 MD5 80d1ac1766ad8a8cdadca5f4273f2d95 k3b-i18n-0.11.tar.bz2 273846
Jeffrey: Source of the problem is that upstream released a revised tarball without changing the file name shortly after I added the ebuild to the tree. # new MD5 appears to be: cf1111472487e4da87c649525e5987f6 No, that is the old one.
Looks like a duplicate of bug 92490.
Don't want to see the bug again because of some outdated mirror, so I renamed the tarball before marking stable.
