Jack wrote: > 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 > > >
That makes sense. It explains why the bug says it is fixed but I'm not getting the results. So, I did the manifest thing to force it to build and install anyway. Now I get this: >>> Verifying ebuild manifests >>> Emerging (1 of 1) app-text/asciidoc-9.0.5::gentoo >>> Failed to emerge app-text/asciidoc-9.0.5, Log file: >>> '/var/log/portage/app-text:asciidoc-9.0.5:20210301-003627.log' >>> Jobs: 0 of 1 complete, 1 failed Load avg: 10.9, 10.6, 10.7 * Package: app-text/asciidoc-9.0.5 * Repository: gentoo * Maintainer: [email protected] [email protected] * USE: abi_x86_64 amd64 elibc_glibc kernel_linux python_single_target_python3_8 userland_GNU * FEATURES: network-sandbox preserve-libs sandbox userpriv usersandbox * Using python3.8 to build >>> Unpacking source... >>> Unpacking asciidoc-9.0.5.tar.gz to /var/tmp/portage/app-text/asciidoc-9.0.5/work >>> Source unpacked in /var/tmp/portage/app-text/asciidoc-9.0.5/work * ERROR: app-text/asciidoc-9.0.5::gentoo failed (prepare phase): * The source directory '/var/tmp/portage/app-text/asciidoc-9.0.5/work/asciidoc-py3-9.0.5' doesn't exist * * Call stack: * ebuild.sh, line 762: Called __ebuild_main 'prepare' * phase-functions.sh, line 1050: Called __dyn_prepare * phase-functions.sh, line 384: Called die * The specific snippet of code: * die "The source directory '${S}' doesn't exist" * * If you need support, post the output of `emerge --info '=app-text/asciidoc-9.0.5::gentoo'`, * the complete build log and the output of `emerge -pqv '=app-text/asciidoc-9.0.5::gentoo'`. * The complete build log is located at '/var/log/portage/app-text:asciidoc-9.0.5:20210301-003627.log'. * For convenience, a symlink to the build log is located at '/var/tmp/portage/app-text/asciidoc-9.0.5/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/app-text/asciidoc-9.0.5/temp/environment'. * Working directory: '/var/tmp/portage/app-text/asciidoc-9.0.5/homedir' * S: '/var/tmp/portage/app-text/asciidoc-9.0.5/work/asciidoc-py3-9.0.5' * * The following package has failed to build, install, or execute postinst: * * (app-text/asciidoc-9.0.5:0/0::gentoo, ebuild scheduled for merge), Log file: * '/var/log/portage/app-text:asciidoc-9.0.5:20210301-003627.log' * root@fireball / # It seems the ebuild or the tarball I'm getting isn't right. By the way, when I look, that directory is there. I'm not sure why it says it doesn't exist. It seems this is a much bigger problem or I need to sync and get tarballs from somewhere else. Something fishy somewhere. Thanks for the help. Will try changing server sources next. Dale :-) :-)
