From: Marius Bakke <mbakke@fastmail.com>
To: 40073@debbugs.gnu.org
Subject: bug#40073: Checksum mismatch on python-llvmlite patch
Date: Sun, 15 Mar 2020 13:25:43 +0100 [thread overview]
Message-ID: <87v9n5ls8o.fsf@devup.no> (raw)
[-- Attachment #1: Type: text/plain, Size: 1393 bytes --]
Hello,
python-llvmlite fails to build because it tries to download a patch that
has the wrong checksum.
Starting download of /gnu/store/hb3kk3d4nngxglfdflf99incbhmbw14h-D47188-svml-VF.patch
From https://raw.githubusercontent.com/numba/llvmlite/v0.30.0/conda-recipes/D47188-svml-VF.patch...
downloading from https://raw.githubusercontent.com/numba/llvmlite/v0.30.0/conda-recipes/D47188-svml-VF.patch...
D47188-svml-VF.patch 73KiB 1.5MiB/s 00:00 [##################] 100.0%
sha256 hash mismatch for /gnu/store/hb3kk3d4nngxglfdflf99incbhmbw14h-D47188-svml-VF.patch:
expected hash: 0wxhgb61k17f0zg2m0726sf3hppm41f8jar2kkg2n8sl5cnjj9mr
actual hash: 0dlr2kmzjrif0wgqql1s3f6pmmsa8fjwjpm08ni68wwvjjx2lcli
hash mismatch for store item '/gnu/store/hb3kk3d4nngxglfdflf99incbhmbw14h-D47188-svml-VF.patch'
build of /gnu/store/vgni0s5mqdyc8pijaz1pdb6pirqd7ddh-D47188-svml-VF.patch.drv failed
This is likely a regression from
6608727262f45d351c55cd1ae40414db7768a374 and would go unnoticed if you
already had the previous patch in your store with the expected checksum.
I tried to simply update the patch, but the updated patch fails to apply
on LLVM 7, and the *other* patch fails to apply if I change to LLVM 8.
There is a new version of python-llvmlite out too, but no changes to the
patches.
Not sure what to do from here, help wanted!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next reply other threads:[~2020-03-15 12:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-15 12:25 Marius Bakke [this message]
2020-11-30 4:35 ` bug#40073: Checksum mismatch on python-llvmlite patch Maxim Cournoyer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87v9n5ls8o.fsf@devup.no \
--to=mbakke@fastmail.com \
--cc=40073@debbugs.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.