From: ludo@gnu.org (Ludovic Courtès)
To: Leo Famulari <leo@famulari.name>
Cc: 28659@debbugs.gnu.org
Subject: bug#28659: v0.13: guix pull fails; libgit2-0.26.0 and 0.25.1 content hashes fail
Date: Mon, 02 Oct 2017 16:57:38 +0200 [thread overview]
Message-ID: <87vajxoavx.fsf@gnu.org> (raw)
In-Reply-To: <20171001204237.GA11804@jasmine.lan> (Leo Famulari's message of "Sun, 1 Oct 2017 16:42:37 -0400")
Hi!
Leo Famulari <leo@famulari.name> skribis:
> I contacted GitHub about this issue a few weeks ago and they said that:
>
> 1) They do not guarantee bit-reproducibility of the snapshots they
> generate automatically for each release tag, and they wish that people
> would not rely on them as we do. However, since people *are* relying on
> them, they are discussing this issue internally.
Oh?! Then we’re in trouble.
Perhaps we should start using ‘git-fetch’ more, with Software Heritage
as a fallback content-addressed mirror? Though again the difficulty is
that SWH uses Git’s method to hash directory contents, so we’d end up
having to provide both a Nix hash and a Git hash in ‘origin’. :-/
> In the meantime, we can add this to the list of reasons that
> reproducibility is difficult in the long term.
Heh.
Ludo’.
next prev parent reply other threads:[~2017-10-02 14:58 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-01 10:16 bug#28659: v0.13: guix pull fails; libgit2-0.26.0 and 0.25.1 content hashes fail Jan Nieuwenhuizen
2017-10-01 19:20 ` Jan Nieuwenhuizen
2017-10-01 20:42 ` Leo Famulari
2017-10-01 21:05 ` ng0
2017-10-02 14:57 ` Ludovic Courtès [this message]
2017-10-02 18:19 ` Leo Famulari
2017-10-02 22:47 ` Maxim Cournoyer
2017-10-03 12:31 ` Ludovic Courtès
2017-10-03 14:24 ` Leo Famulari
2017-10-04 4:22 ` Maxim Cournoyer
2017-10-04 16:54 ` Leo Famulari
2017-10-04 23:53 ` Maxim Cournoyer
2017-10-05 4:52 ` Maxim Cournoyer
2017-10-05 6:08 ` Jan Nieuwenhuizen
2017-10-02 15:09 ` Ludovic Courtès
2017-10-02 17:05 ` Jan Nieuwenhuizen
2017-10-02 18:22 ` Leo Famulari
2017-10-02 20:00 ` Ludovic Courtès
2017-10-02 20:22 ` Jan Nieuwenhuizen
2017-10-02 20:29 ` Leo Famulari
2017-10-03 12:30 ` Ludovic Courtès
2017-10-20 21:17 ` Leo Famulari
2017-11-28 13:30 ` Ludovic Courtès
2017-12-14 16:53 ` Ludovic Courtès
2017-12-15 9:30 ` bug#28659: Always enable substitutes for fixed-output derivations Ludovic Courtès
2022-02-03 2:58 ` bug#28659: Content-addressed mirror is not used upon invalid hash zimoun
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87vajxoavx.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=28659@debbugs.gnu.org \
--cc=leo@famulari.name \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).