From: Simon Tournier <zimon.toutoune@gmail.com>
To: Leo Famulari <leo@famulari.name>, Greg Hogan <code@greghogan.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Guix release broken without substitutes on ungrafted openssl
Date: Thu, 16 Feb 2023 12:47:32 +0100 [thread overview]
Message-ID: <86cz69bzmz.fsf@gmail.com> (raw)
In-Reply-To: <Y+0lfqRsMf99uLVy@jasmine.lan>
Hi,
On Wed, 15 Feb 2023 at 13:33, Leo Famulari <leo@famulari.name> wrote:
> I'd guess it's happened 4 times in the last several years.
>
> It's one of several reasons that rebuilding old Guix releases actually
> approaches being a Hard Problem.
The issue is from the impure world. ;-)
Well, yeah it would probably be difficult to install from scratch Guix
v1.0 in some future.
However, the hope is that,
guix time-machine --commit=v1.0 -- <command>
using distant future Guix to run <command> from Guix v1.0. The distant
future Guix should be able to deal with the distant future impure world
and populate for the past <command> running inside a pure world.
For sure, it is a Hard Problem. As I like to say when presenting “guix
time-machine”, it is a real world experiment, probably unique, to know
what is the size of the time frame where reproducible time-travel is
possible. I try to explain that this reproducible time-travel requires
three conditions:
1. source code availability
2. Linux kernel compatibility
3. hardware compatibility
Now, I would add:
4. being able to communicate with the world via the network
Cheers,
simon
next prev parent reply other threads:[~2023-02-16 11:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-15 17:15 Guix release broken without substitutes on ungrafted openssl Greg Hogan
2023-02-15 18:33 ` Leo Famulari
2023-02-15 20:04 ` Greg Hogan
2023-02-16 11:47 ` Simon Tournier [this message]
2023-02-22 13:48 ` Simon Tournier
2023-02-21 23:20 ` Ludovic Courtès
2023-02-16 19:12 ` Aleksandr Vityazev
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=86cz69bzmz.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=code@greghogan.com \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).