unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: znavko@disroot.org
To: help-guix <help-guix@gnu.org>
Subject: Why reproducibility is breaking by metadata?
Date: Wed, 03 Jul 2019 04:05:02 +0000	[thread overview]
Message-ID: <71aab7b233f9f6df36e0248c86b5e020@disroot.org> (raw)

Hello, Guix Help! I am translating Guix manual and found that the author is entirely given to reproducibility. It leads to such phrases that metadata breaks reproducibility when he describes '--save-provenance' flag of 'guix pack' command here:

'This option is not enabled by default because, like timestamps, provenance information contributes nothing to the build process. In other words, there is an infinity of channel URLs and commit IDs that can lead to the same pack. Recording such “silent” metadata in the output thus potentially breaks the source-to-binary bitwise reproducibility property. '

I did not expected such a categorical statement. I think, it does not actually break reproducibility but only complicates checks. If we have to talk about reproducibility to ignoramus, saying 'this option breaks reproducibility option' have to have remark 'simply put' or 'plainly'.

             reply	other threads:[~2019-07-03  4:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-03  4:05 znavko [this message]
2019-07-03  6:13 ` Why reproducibility is breaking by metadata? Julien Lepiller
2019-07-03  6:39 ` Konrad Hinsen
2019-07-06  9:52   ` Giovanni Biscuolo
2019-07-08  7:51     ` Konrad Hinsen

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=71aab7b233f9f6df36e0248c86b5e020@disroot.org \
    --to=znavko@disroot.org \
    --cc=help-guix@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.
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).