Tree synced on Fri May 13 09:06:37 UTC 2005 >>> emerge (5 of 5) app-cdr/k3b-0.11.24 to / >>> md5 files ;-) ChangeLog >>> md5 files ;-) metadata.xml >>> md5 files ;-) k3b-0.11.23-r2.ebuild >>> md5 files ;-) k3b-0.11.24.ebuild >>> md5 files ;-) k3b-0.12_beta1.ebuild >>> md5 files ;-) files/k3b-0.11.17-noarts.patch >>> md5 files ;-) files/digest-k3b-0.11.23-r2 >>> md5 files ;-) files/k3b-dvdrip-transcode.patch >>> md5 files ;-) files/digest-k3b-0.11.24 >>> md5 files ;-) files/digest-k3b-0.12_beta1 !!! Digest verification Failed: !!! /usr/portage/distfiles/k3b-0.11.24.tar.bz2 !!! Reason: Failed on MD5 verification Reproducible: Always Steps to Reproduce: 1. 2. 3.
thanks for the report, upstream silently issued a new tarball, the fixed digest just hit cvs
Carlo said: "upstream silently issued a new tarball" I hope you realise how pungent that sounds ;) Thanks for the fix.
Saying I like that would be a lie. Fetching the new tarball and diffing with the other one to know what happened takes a couple of minutes more then reading news, let the box build a new version and having a look if the app installs correctly and runs fine.
s/then/than
*** Bug 92536 has been marked as a duplicate of this bug. ***
*** Bug 92641 has been marked as a duplicate of this bug. ***
There's still a problem in the digest file. I just resynced the portage tree, and k3b is still failing to emerge properly: !!! Digest verification Failed: !!! /usr/portage/distfiles/k3b-0.11.24.tar.bz2 !!! Reason: Filesize does not match recorded size Bugzilla will not allow me to reopen this bug, but if I try to create a new bug, as I did earlier today, it will just get marked as a duplicate of this one, so I don't know how to proceed.
the MD5 digest line for k3b 0.11.24 should look like this: MD5 d30fe0bc321e1f8aeebda80c82ee3dfb k3b-0.11.24.tar.bz2 3202929
Your tarball is incorrect.
