From: zimoun <zimon.toutoune@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: unexpected reproducibility of reproducible blog post?
Date: Wed, 29 Apr 2020 15:12:34 +0200 [thread overview]
Message-ID: <CAJ3okZ32F2E_P9iN4+PzcPKgkhvFXpqJfvv0ZLrRX2HCsYeeWg@mail.gmail.com> (raw)
In-Reply-To: <87a72ujwbq.fsf@elephly.net>
Hi Ricardo,
On Wed, 29 Apr 2020 at 14:44, Ricardo Wurmus <rekado@elephly.net> wrote:
>
>
> Konrad Hinsen <konrad.hinsen@fastmail.net> writes:
>
> > One question I have been wondering about is the possibility of grafts
> > being an obstacle to reproducibility. Grafts are something I don't
> > really understand yet, so I cannot answer this question. In particular,
> > does a grafted package get a different hash from a package built with
> > grafting disabled?
>
> Yes.
>
> A grafted package is a copy of the original package but with all
> references to /gnu/store/AAAAAA-… replaced with /gnu/store/BBBBBB-….
> This is done recursively starting with the direct users of the
> replaced package and for all users of those users.
Could the grafts explain the mismatch reported before?
Cheers,
simon
next prev parent reply other threads:[~2020-04-29 13:17 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
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 [this message]
-- 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=CAJ3okZ32F2E_P9iN4+PzcPKgkhvFXpqJfvv0ZLrRX2HCsYeeWg@mail.gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=guix-devel@gnu.org \
--cc=rekado@elephly.net \
/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.