unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Jan Nieuwenhuizen <janneke@gnu.org>
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: Sun, 1 Oct 2017 16:42:37 -0400	[thread overview]
Message-ID: <20171001204237.GA11804@jasmine.lan> (raw)
In-Reply-To: <87wp4e8yk5.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1294 bytes --]

On Sun, Oct 01, 2017 at 09:20:42PM +0200, Jan Nieuwenhuizen wrote:
> Jan Nieuwenhuizen writes:
> 
> The changing of the libgit-0.26.0 checksum was already reported about 3
> weeks ago (github seems to only show relative dates)
> 
>     https://github.com/libgit2/libgit2/issues/4343
> 
> and the bug is still open.  It seems to be a github thing.  As I
> understand it, currently our options are to update the hash and pray it
> won't happen again or host libgit2 tarballs ourselves.

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.
2) This is the relevant code change:
https://git.kernel.org/pub/scm/git/git.git/commit/?id=22f0dcd9634a818a0c83f23ea1a48f2d620c0546

In the meantime, we can add this to the list of reasons that
reproducibility is difficult in the long term.

I don't have any solutions in mind besides keeping substitutes available
for as long as possible and, for users, using substitutes. We might also
petition upstream projects to offer a "real" release tarball.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2017-10-01 20:44 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 [this message]
2017-10-01 21:05     ` ng0
2017-10-02 14:57     ` Ludovic Courtès
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=20171001204237.GA11804@jasmine.lan \
    --to=leo@famulari.name \
    --cc=28659@debbugs.gnu.org \
    --cc=janneke@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 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).