From: Leo Famulari <leo@famulari.name>
To: Hartmut Goebel <h.goebel@crazy-compilers.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Wrong hashes for libgit2 archives
Date: Sun, 8 Oct 2017 13:40:57 -0400 [thread overview]
Message-ID: <20171008174057.GC26253@jasmine.lan> (raw)
In-Reply-To: <7406420b-121a-29d8-5f23-d9233f4b148d@crazy-compilers.com>
[-- Attachment #1: Type: text/plain, Size: 1228 bytes --]
On Sun, Oct 08, 2017 at 06:46:04PM +0200, Hartmut Goebel wrote:
> Hi,
>
> I'm currently stuck with building kde-frameworks due to mismatching
> hashes for libgit2:
>
> @ build-failed
> /gnu/store/mgh4yjxkxfyqmc7c61vwq4vs8v837602-libgit2-0.26.0.tar.gz.drv -
> 1 sha256 hash mismatch for output path
> `/gnu/store/53lj4z9cavl7n27r89zjnvyd8fk854kj-libgit2-0.26.0.tar.gz'
> expected: 1fdk9yhwvl1w1z71ykzcvgh4nsf8scxcbclz5anh98zpplmhmisa
> actual: 1b3figbhp5l83vd37vq6j2narrq4yl9pfw6mw0px0dzb1hz3jqka
>
> I tried downgrading to v0.25.1 (by reverting 58dce7bf), but that failed
> with the same error:
>
> @ build-failed
> /gnu/store/h8vrairp09vg239d9vpli12661vrv9d3-libgit2-0.25.1.tar.gz.drv -
> 1 sha256 hash mismatch for output path
> `/gnu/store/c3npgqn9ag2ypi9bda1g779wwwlcqqrf-libgit2-0.25.1.tar.gz'
> expected: 1cdwcw38frc1wf28x5ppddazv9hywc718j92f3xa3ybzzycyds3s
> actual: 0ywcxw1mwd56c8qc14hbx31bf198gxck3nja3laxyglv7l57qp26
The auto-generated GitHub snapshots, which is what we use for libgit2,
are not created deterministically:
https://bugs.gnu.org/28659
https://github.com/libgit2/libgit2/issues/4343
For now, the workaround is to get the tarball from a substitute server.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-10-08 17:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-08 16:46 Wrong hashes for libgit2 archives Hartmut Goebel
2017-10-08 17:40 ` Leo Famulari [this message]
2017-10-09 7:26 ` Hartmut Goebel
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=20171008174057.GC26253@jasmine.lan \
--to=leo@famulari.name \
--cc=guix-devel@gnu.org \
--cc=h.goebel@crazy-compilers.com \
/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.