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: Wed, 29 Apr 2020 18:00:04 +0200	[thread overview]
Message-ID: <m1mu6ujn97.fsf@fastmail.net> (raw)
In-Reply-To: <CAJ3okZ1Fi5Jdpu5O_ddr8COC15wDaV8thy_yg0VQzbN_=O=F4g@mail.gmail.com>

zimoun <zimon.toutoune@gmail.com> writes:

> Argh! The author should watch the Fun MOOC about computational
> reproducibility. ;-)

That would probably help. I'll pass on the message ;-)

I have also opened an issue for this:

  https://github.com/khinsen/reproducibility-with-guix/issues/2

> 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.

Time travelling is not as simple as it looks, but then we should have
expected that!

Cheers,
  Konrad


  reply	other threads:[~2020-04-29 16:02 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 [this message]
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
  -- 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=m1mu6ujn97.fsf@fastmail.net \
    --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.