| 1 |
Jack wrote: |
| 2 |
> On 2/28/21 4:53 PM, Dale wrote: |
| 3 |
>> Howdy, |
| 4 |
>> |
| 5 |
>> For the past couple weeks, this package has failed to update because it |
| 6 |
>> is the wrong size. This is from the logs for today. |
| 7 |
>> |
| 8 |
>> |
| 9 |
>> 2021-02-22 07:20:45 (96.2 KB/s) - |
| 10 |
>> ‘/var/cache/portage/distfiles/asciidoc-9.0.5.tar.gz.__download__’ saved |
| 11 |
>> [1119288] |
| 12 |
>> |
| 13 |
>> !!! Fetched file: asciidoc-9.0.5.tar.gz VERIFY FAILED! |
| 14 |
>> !!! Reason: Filesize does not match recorded size |
| 15 |
>> !!! Got: 1119288 |
| 16 |
>> !!! Expected: 1119318 |
| 17 |
>> Refetching... File renamed to |
| 18 |
>> '/var/cache/portage/distfiles/asciidoc-9.0.5.tar.gz._checksum_failure_.ngu5ov57' |
| 19 |
>> |
| 20 |
>> |
| 21 |
>> !!! Couldn't download 'asciidoc-9.0.5.tar.gz'. Aborting. |
| 22 |
>> |
| 23 |
>> |
| 24 |
>> I found a bug that I think addresses this issue. It appears it should |
| 25 |
>> be fixed but I've synced twice since then and it still fails. Here's |
| 26 |
>> the bug. |
| 27 |
>> |
| 28 |
>> https://bugs.gentoo.org/770841 |
| 29 |
>> |
| 30 |
>> I've also tried different versions with no change. Any one else running |
| 31 |
>> into this? Is something wrong on my end that is preventing the fix from |
| 32 |
>> reaching me? Am I missing something else? |
| 33 |
>> |
| 34 |
>> Thanks. |
| 35 |
>> |
| 36 |
>> Dale |
| 37 |
> |
| 38 |
> I just installed asciidoc-9.0.4 and then 9.0.5 with no problems. |
| 39 |
> However, something seems odd, since those ebuilds are dated 2/14, so |
| 40 |
> not recently updated. That bug looks like they identified the |
| 41 |
> necessary fixes, but didn't actually apply them yet. I think what |
| 42 |
> happened is that upstream made those changes talked about in the bug, |
| 43 |
> but the new tarballs have not hit all the mirrors yet. If you happen |
| 44 |
> to hit a mirror with the old files, the emerge will work OK. If you |
| 45 |
> hit a mirror with the new tarballs, you'll get the failure you got. |
| 46 |
> Since you already have the new tarball, maybe you just need to |
| 47 |
> manually edit the ebuild per the bug, and rerun "ebuild |
| 48 |
> path/to/file.ebuild manifest" to manually update the hash for the |
| 49 |
> tarball, if you trust the tarball you have. |
| 50 |
> |
| 51 |
> Jack |
| 52 |
> |
| 53 |
> |
| 54 |
> |
| 55 |
|
| 56 |
|
| 57 |
That makes sense. It explains why the bug says it is fixed but I'm not |
| 58 |
getting the results. So, I did the manifest thing to force it to build |
| 59 |
and install anyway. Now I get this: |
| 60 |
|
| 61 |
|
| 62 |
>>> Verifying ebuild manifests |
| 63 |
>>> Emerging (1 of 1) app-text/asciidoc-9.0.5::gentoo |
| 64 |
>>> Failed to emerge app-text/asciidoc-9.0.5, Log file: |
| 65 |
>>> '/var/log/portage/app-text:asciidoc-9.0.5:20210301-003627.log' |
| 66 |
>>> Jobs: 0 of 1 complete, 1 failed Load avg: 10.9, |
| 67 |
10.6, 10.7 |
| 68 |
* Package: app-text/asciidoc-9.0.5 |
| 69 |
* Repository: gentoo |
| 70 |
* Maintainer: marcec@×××.de proxy-maint@g.o |
| 71 |
* USE: abi_x86_64 amd64 elibc_glibc kernel_linux |
| 72 |
python_single_target_python3_8 userland_GNU |
| 73 |
* FEATURES: network-sandbox preserve-libs sandbox userpriv usersandbox |
| 74 |
* Using python3.8 to build |
| 75 |
>>> Unpacking source... |
| 76 |
>>> Unpacking asciidoc-9.0.5.tar.gz to |
| 77 |
/var/tmp/portage/app-text/asciidoc-9.0.5/work |
| 78 |
>>> Source unpacked in /var/tmp/portage/app-text/asciidoc-9.0.5/work |
| 79 |
* ERROR: app-text/asciidoc-9.0.5::gentoo failed (prepare phase): |
| 80 |
* The source directory |
| 81 |
'/var/tmp/portage/app-text/asciidoc-9.0.5/work/asciidoc-py3-9.0.5' |
| 82 |
doesn't exist |
| 83 |
* |
| 84 |
* Call stack: |
| 85 |
* ebuild.sh, line 762: Called __ebuild_main 'prepare' |
| 86 |
* phase-functions.sh, line 1050: Called __dyn_prepare |
| 87 |
* phase-functions.sh, line 384: Called die |
| 88 |
* The specific snippet of code: |
| 89 |
* die "The source directory '${S}' doesn't exist" |
| 90 |
* |
| 91 |
* If you need support, post the output of `emerge --info |
| 92 |
'=app-text/asciidoc-9.0.5::gentoo'`, |
| 93 |
* the complete build log and the output of `emerge -pqv |
| 94 |
'=app-text/asciidoc-9.0.5::gentoo'`. |
| 95 |
* The complete build log is located at |
| 96 |
'/var/log/portage/app-text:asciidoc-9.0.5:20210301-003627.log'. |
| 97 |
* For convenience, a symlink to the build log is located at |
| 98 |
'/var/tmp/portage/app-text/asciidoc-9.0.5/temp/build.log'. |
| 99 |
* The ebuild environment file is located at |
| 100 |
'/var/tmp/portage/app-text/asciidoc-9.0.5/temp/environment'. |
| 101 |
* Working directory: '/var/tmp/portage/app-text/asciidoc-9.0.5/homedir' |
| 102 |
* S: '/var/tmp/portage/app-text/asciidoc-9.0.5/work/asciidoc-py3-9.0.5' |
| 103 |
* |
| 104 |
* The following package has failed to build, install, or execute postinst: |
| 105 |
* |
| 106 |
* (app-text/asciidoc-9.0.5:0/0::gentoo, ebuild scheduled for merge), |
| 107 |
Log file: |
| 108 |
* '/var/log/portage/app-text:asciidoc-9.0.5:20210301-003627.log' |
| 109 |
* |
| 110 |
root@fireball / # |
| 111 |
|
| 112 |
|
| 113 |
It seems the ebuild or the tarball I'm getting isn't right. By the way, |
| 114 |
when I look, that directory is there. I'm not sure why it says it |
| 115 |
doesn't exist. It seems this is a much bigger problem or I need to sync |
| 116 |
and get tarballs from somewhere else. Something fishy somewhere. |
| 117 |
|
| 118 |
Thanks for the help. Will try changing server sources next. |
| 119 |
|
| 120 |
Dale |
| 121 |
|
| 122 |
:-) :-) |
Archives