2013-10-12 12:24:54 (312 KB/s) - '/usr/portage/distfiles/libtar-1.2.20.tar.gz' saved [63542] !!! Fetched file: libtar-1.2.20.tar.gz VERIFY FAILED! !!! Reason: Failed on SHA256 verification !!! Got: d8790291ed5acfeaaaf2ce3fa9fea024c1b553bbd1ceed5b5d6eb0b4cf6ccb7e !!! Expected: a6ad158585c0274496421dfa18f77e61de4889dd531ad9421f5eb639f79b983a
ebuild libtar-1.2.20.ebuild fetch Appending /newaches/gentoo/cvs/gentoo-x86 to PORTDIR_OVERLAY... >>> Downloading 'http://repo.or.cz/w/libtar.git/snapshot/v1.2.20.tar.gz' --2013-10-12 15:13:14-- http://repo.or.cz/w/libtar.git/snapshot/v1.2.20.tar.gz Resolving repo.or.cz (repo.or.cz)... 195.113.20.142 Connecting to repo.or.cz (repo.or.cz)|195.113.20.142|:80... connected. HTTP request sent, awaiting response... 200 OK Length: unspecified [application/x-gzip] Saving to: ‘/world/distfiles/libtar-1.2.20.tar.gz’ [ <=> ] 63,542 --.-K/s in 0.08s 2013-10-12 15:13:15 (758 KB/s) - ‘/world/distfiles/libtar-1.2.20.tar.gz’ saved [63542] !!! Fetched file: libtar-1.2.20.tar.gz VERIFY FAILED! !!! Reason: Failed on SHA256 verification !!! Got: e1c14394f92680979fd5326ccc940b5b2a55fc6c90c915f2192c13273f542ab7 !!! Expected: a6ad158585c0274496421dfa18f77e61de4889dd531ad9421f5eb639f79b983a Refetching... File renamed to '/world/distfiles/libtar-1.2.20.tar.gz._checksum_failure_.3ntmd1' !!! Couldn't download 'libtar-1.2.20.tar.gz'. Aborting.
fixed.
Well, it seems not fixed. I tried: rm Manifest && repoman manifest && repoman commit -m "$message" but it seems to not appear in the cvs. Now I'm trying to add a revision.
(In reply to Agostino Sarubbo from comment #3) > Well, it seems not fixed. > > I tried: rm Manifest && repoman manifest && repoman commit -m "$message" > > but it seems to not appear in the cvs. Now I'm trying to add a revision. @pinkbyte, it still fails, could you check it?
*** Bug 487884 has been marked as a duplicate of this bug. ***
this has been bothering me for a few days now. My guess is checksum in portage is wrong.
(In reply to C.J. Wijtmans from comment #6) > this has been bothering me for a few days now. My guess is checksum in > portage is wrong. The checksum from upstream is not constant, because the tarball is regenerated on request and contains a timestamp.
This bug is reply to me: 2013-10-14 14:26:53 (144 KB/s) - ‘/usr/portage/distfiles/libtar-1.2.20.tar.gz’ saved [63542] !!! Fetched file: libtar-1.2.20.tar.gz VERIFY FAILED! !!! Reason: Failed on SHA256 verification !!! Got: 20bc2b46a75c1b08c14f6995ec4143dd3b98f233639033cc702663c473e847d2 !!! Expected: ae5aa2092fdeb1124b83be498bac73e1a82dec52ef8374cc0815140d8e1b87bf Refetching... File renamed to '/usr/portage/distfiles/libtar-1.2.20.tar.gz._checksum_failure_.e5Wipj'
Oops, my mistake. 14 Oct 2013; Sergey Popov <pinkbyte@gentoo.org> -libtar-1.2.20.ebuild, -libtar-1.2.20-r1.ebuild, +libtar-1.2.20-r2.ebuild: Revision bump: put tarball with recent version on devspace, cause upstream URL contains dynamically regenerated file, which did not have constant checksum, bug #487776. Drop old revisions 14 Oct 2013; Sergey Popov <pinkbyte@gentoo.org> libtar-1.2.20-r2.ebuild: Restore amd64 stable keyword I have to do some tricks here, with Infra's help(thanks to tampakrap). Please, wait for at least 4 hours(our mirrors sync period), sync and try again, thanks.