fresh emerge --sync this date. emerge hal fails on unpack with 'Failed on MD5 verification" Reproducible: Always Steps to Reproduce: 1.emerge hal 2. 3. Actual Results: Logged bug report :-)
what hal version are you trying to emerge? please include full name with r* number. Also provide the direct error message that you are getting. The md5's in the Manifest match the ebuilds md5sums for me.
thanks as per the title it says hal-0.4.7 when doing an emerge but looks to fail on the MD5 check of digest-hal-0.4.8 as below output from emerge hal: 22:35:23 (458.51 KB/s) - `/usr/portage/distfiles/hal-0.4.7.tar.gz' saved [1,349,064/1,349,064] >>> md5 files ;-) ChangeLog >>> md5 files ;-) hal-0.4.5-r2.ebuild >>> md5 files ;-) hal-0.4.7-r2.ebuild >>> md5 files ;-) hal-0.4.8.ebuild >>> md5 files ;-) metadata.xml >>> md5 files ;-) files/digest-hal-0.4.5-r2 >>> md5 files ;-) files/digest-hal-0.4.7-r2 >>> md5 files ;-) files/hald >>> md5 files ;-) files/hal-0.4.1-old_storage_policy.patch >>> md5 files ;-) files/hal-0.4.5-gentoo_gphoto2_usermap.patch >>> md5 files ;-) files/hal-0.4.5-net_lockup.patch >>> md5 files ;-) files/hal-0.4.5-vat_ntfs_labels.patch >>> md5 files ;-) files/hal-0.4.7-device_info_leak.patch >>> md5 files ;-) files/hal-0.4.7-dont_add_device_twice-r1.patch >>> md5 files ;-) files/hal-0.4.7-sys_floppy_detection.patch >>> md5 files ;-) files/hal-0.4.7-vfat_mount_utf8.patch >>> md5 files ;-) files/hal-0.4.8-fix_dvdram.patch >>> md5 files ;-) files/digest-hal-0.4.8 !!! Digest verification Failed: !!! /usr/portage/distfiles/hal-0.4.7.tar.gz !!! Reason: Failed on MD5 verification
its actually failing on /usr/portage/distfiles/hal-0.4.7.tar.gz try doing: rm /usr/portage/sys-apps/hal/files/digest-hal-0.4.7-r2 and re-syncing. if this doesn't work, please post: "cat /usr/portage/sys-apps/hal/Manifest" and "md5sum /usr/portage/distfiles/hal-0.4.7.tar.gz" and "cat /usr/portage/sys-apps/hal/files/digest-hal-0.4.7-r2" Thanks!
ok - rm'd/emerge --sync as requested - no joy. Manifest: MD5 fa5a9ba83581180fd4f3bc3736ae1e4b hal-0.4.7-r2.ebuild 3490 MD5 3305724319ca1a9b454eb5dc7565ba13 hal-0.4.8.ebuild 3375 MD5 0d714f805453baef6cc52afc9bc5465d hal-0.4.5-r2.ebuild 3152 MD5 8183e8996ff9ceb8ef2049fdfb825398 ChangeLog 5396 MD5 731695e9263a5a2e1eeba290b36078d5 metadata.xml 219 MD5 192112dfb678a9795a93d3cdcc50bb95 files/hald 543 MD5 64253ef1f2dcf68b2d82429026280085 files/hal-0.4.7-dont_add_device_twice-r1.patch 691 MD5 442da36fd75002bb8300b0fcb65a1371 files/hal-0.4.5-vat_ntfs_labels.patch 2874 MD5 c1624c9456f164c1b611e3ab22fb105d files/hal-0.4.7-device_info_leak.patch 2203 MD5 ada3b2801b82813b4f10fd6f6caf9d6f files/digest-hal-0.4.5-r2 62 MD5 3031a9fe74f43859c313d5f3076e68cd files/digest-hal-0.4.7-r2 62 MD5 a4d2c4884a3dedf2450cf37508d3c122 files/hal-0.4.7-vfat_mount_utf8.patch 670 MD5 2bbbb519c89110dfec96cf63cf541afc files/digest-hal-0.4.8 62 MD5 e3ecbfe57c0833d32f0ea57a0de58aee files/hal-0.4.8-fix_dvdram.patch 465 MD5 b0e12a62ce698e1eb2a32139498330cd files/hal-0.4.5-gentoo_gphoto2_usermap.patch 817 MD5 f3ba6ada28cf947f8a7b7ec8fdd708ba files/hal-0.4.5-net_lockup.patch 2429 MD5 58ed07e2de5e898a1e4eeedf595ddb06 files/hal-0.4.7-sys_floppy_detection.patch 568 MD5 a0ce1c268e0b7d0967ec7b8e0d0d26d2 files/hal-0.4.1-old_storage_policy.patch 1216 md5sum hal-0.4.7.tar.gz: a4e6c35ec2fd76562ce69e86fa258fbc /usr/portage/distfiles/hal-0.4.7.tar.gz digest-hal: MD5 3386817a6811cce803bcfa8a20b05c51 hal-0.4.7.tar.gz 1349064
heres my md5sum of the fetched file ( does match the one in your manifest ) MD5 3386817a6811cce803bcfa8a20b05c51 hal-0.4.7.tar.gz 1349064 can you try switching your mirror ( in make.conf ) and trying again? ( you can just do rm /usr/portage/distfiles/hal-0.4.7.tar.gz and then emerge hal again ) Thanks for the quick responses.
no - thank you for the support. Yes this did the trick. For future reference - how can this happen? I would have thought that hal-0.4.7 would be the same on both mirrors? Please close this off.
sometimes a mirror ends up with a corrupt version of the file. did you happen to note or know which mirror were you using? Thanks!
first in the list is ftp://ftp.jetstreamgames.co.nz/dist/gentoo (didn't see any timeouts/fallback in the sync)
Euan, What other mirrors do you have listed in GENTOO_MIRRORS? ftp://ftp.jetstreamgames.co.nz/dist/gentoo doesn't appear to be a valid mirror. Thanks.
Looks like a momentary blip, looks fine for me. >>> hal-0.4.7.tar.gz size ;-) >>> hal-0.4.7.tar.gz MD5 ;-)
*** Bug 94445 has been marked as a duplicate of this bug. ***
Hi there. I got this same bug from HAL on the pacificinternet.com.au mirror. Date downloaded: 20/06/2005