On 2/28/21 4:53 PM, Dale wrote:
Howdy,
For the past couple weeks, this package has failed to update because it
is the wrong size. This is from the logs for today.
2021-02-22 07:20:45 (96.2 KB/s) -
‘/var/cache/portage/distfiles/asciidoc-9.0.5.tar.gz.__download__’ saved
[1119288]
!!! Fetched file: asciidoc-9.0.5.tar.gz VERIFY FAILED!
!!! Reason: Filesize does not match recorded size
!!! Got: 1119288
!!! Expected: 1119318
Refetching... File renamed to
'/var/cache/portage/distfiles/asciidoc-9.0.5.tar.gz._checksum_failure_.ngu5ov57'
!!! Couldn't download 'asciidoc-9.0.5.tar.gz'. Aborting.
I found a bug that I think addresses this issue. It appears it should
be fixed but I've synced twice since then and it still fails. Here's
the bug.
https://bugs.gentoo.org/770841
I've also tried different versions with no change. Any one else running
into this? Is something wrong on my end that is preventing the fix from
reaching me? Am I missing something else?
Thanks.
Dale
I just installed asciidoc-9.0.4 and then 9.0.5 with no problems.
However, something seems odd, since those ebuilds are dated 2/14, so not
recently updated. That bug looks like they identified the necessary
fixes, but didn't actually apply them yet. I think what happened is
that upstream made those changes talked about in the bug, but the new
tarballs have not hit all the mirrors yet. If you happen to hit a
mirror with the old files, the emerge will work OK. If you hit a
mirror with the new tarballs, you'll get the failure you got. Since you
already have the new tarball, maybe you just need to manually edit the
ebuild per the bug, and rerun "ebuild path/to/file.ebuild manifest" to
manually update the hash for the tarball, if you trust the tarball you have.
Jack
