From: zimoun <zimon.toutoune@gmail.com>
To: Konrad Hinsen <konrad.hinsen@fastmail.net>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: unexpected reproducibility of reproducible blog post?
Date: Thu, 30 Apr 2020 16:51:41 +0200 [thread overview]
Message-ID: <CAJ3okZ3YkYs4ieRmh0v42FUTNHJHQuVSHUnw4qmFNJTbNpQ-OQ@mail.gmail.com> (raw)
In-Reply-To: <m1mu6ujn97.fsf@fastmail.net>
On Wed, 29 Apr 2020 at 18:00, Konrad Hinsen <konrad.hinsen@fastmail.net> wrote:
> I have also opened an issue for this:
>
> https://github.com/khinsen/reproducibility-with-guix/issues/2
I will add something overthere for tracking reproduciblity infos in the future.
> > Grafts or maybe Guile 2 -> 3?
>
> With time-machine, you run the full Guix from back then, so you run
> Guile 2 if that's what it takes. What I am not so sure about is how the
> old Guix release is built. If the build uses the equivalent of "guix
> environment guix", it would start using Guile 3.
From [1] and assuming that the commit was the same, i.e.,
769b96b62e8c09b078f73adc09fb860505920f8f, there is also a mismatch
about the resulting binary.
Expected:
1be3c1b5d1e065017e4c56f725b1a692
Now:
2805a33e2e48f648307c6b913b69e41c
--8<---------------cut here---------------start------------->8---
guix describe # f03e5ca
guix time-machine \
--commit=769b96b62e8c09b078f73adc09fb860505920f8f \
-- environment --container --ad-hoc gcc-toolchain \
-- gcc pi.c -o pi-guix
--8<---------------cut here---------------end--------------->8---
[1] https://lists.gnu.org/archive/html/guix-devel/2020-01/msg00192.html
From f03e5ca, the time machine downloads the substitute:
https://ci.guix.gnu.org/nar/lzip/ij38zh495f81xpzmp4qzqz4fprczwck2-gcc-toolchain-9.2.0
> Time travelling is not as simple as it looks, but then we should have
> expected that!
I agree but it is annoying.
Because `in fine` the computations are not more reproducible than say
Debian if 3 months later we are not able to reproduce them bit-to-bit.
I do not know. Maybe it is about 'time-machine', maybe about the exact
commit used (most probable! :-)), maybe about the Guix build toolchain
(seed) used to travel back and restore the previous build toolchain.
Who knows? :-)
Well, I will try later with my desktop machine when I will be back at
the office; hoping that I did not garbage collected. :-)
Cheers,
simon
next prev parent reply other threads:[~2020-04-30 14:52 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 [this message]
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
-- 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=CAJ3okZ3YkYs4ieRmh0v42FUTNHJHQuVSHUnw4qmFNJTbNpQ-OQ@mail.gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=guix-devel@gnu.org \
--cc=konrad.hinsen@fastmail.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.