all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Konrad Hinsen <konrad.hinsen@fastmail.net>
To: zimoun <zimon.toutoune@gmail.com>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: unexpected reproducibility of reproducible blog post?
Date: Mon, 04 May 2020 15:50:29 +0200	[thread overview]
Message-ID: <m1pnbj4xne.fsf@khs-macbook.home> (raw)
In-Reply-To: <CAJ3okZ3YkYs4ieRmh0v42FUTNHJHQuVSHUnw4qmFNJTbNpQ-OQ@mail.gmail.com>

Hi Simon,

> I will add something overthere for tracking reproduciblity infos in
> the future.

It would actually be nice to have some external Guix reproducibility
surveillance. A few benchmark packages that will be rebuilt regularly,
using frozen commits via time-machine, and checked for bit-by-bit
identity explicitly, not relying on Guix' hash mechanism. Trust but
verify.

My example is perhaps not such a bad start. Building a Docker container
containing gcc exercises a lot of code in Guix.

I looked a bit at grafts. The documentation at

  https://guix.gnu.org/manual/en/html_node/Security-Updates.html

isn't very explicit about the reproducibility of grafts. In particular,
it doesn't say if a package containing patched binaries retains its
original hash, or receives a new unique one. With a unique hash, grafts
would just be a tweak in the build system, and no less reproducible than
standard builds. It looks like I have to dive into the source code to
find out!

Cheers,
  Konrad


  reply	other threads:[~2020-05-04 13:50 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-26 17:44 unexpected reproducibility of reproducible blog post? zimoun
2020-04-29  9:26 ` Konrad Hinsen
2020-04-29  9:49   ` zimoun
2020-04-29 16:00     ` Konrad Hinsen
2020-04-30 14:51       ` zimoun
2020-05-04 13:50         ` Konrad Hinsen [this message]
2020-05-04 14:25           ` zimoun
2020-05-05 10:06           ` Ludovic Courtès
2020-05-05 13:44             ` Konrad Hinsen
2020-04-29 12:44   ` Ricardo Wurmus
2020-04-29 13:12     ` zimoun
  -- strict thread matches above, loose matches on Subject: below --
2020-04-26 22:53 Leo Prikler
2020-04-27 10:05 ` zimoun
2020-04-27 15:28   ` Leo Prikler

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=m1pnbj4xne.fsf@khs-macbook.home \
    --to=konrad.hinsen@fastmail.net \
    --cc=guix-devel@gnu.org \
    --cc=zimon.toutoune@gmail.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.