all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Simon Tournier <zimon.toutoune@gmail.com>
To: Konrad Hinsen <konrad.hinsen@fastmail.net>,
	Guix Devel <guix-devel@gnu.org>
Subject: Re: Time travel accident
Date: Fri, 07 Apr 2023 19:26:49 +0200	[thread overview]
Message-ID: <86zg7jk3hi.fsf@gmail.com> (raw)
In-Reply-To: <m1o7o0gml9.fsf@fastmail.net>

Hi Konrad,

On Fri, 07 Apr 2023 at 09:47, Konrad Hinsen <konrad.hinsen@fastmail.net> wrote:

> That fails, due to a build failure in OpenSSL:

Yeah, time bomb!

Somehow, it is a know issue: https://issues.guix.gnu.org/58650

As Julien pointed, replacing the date of the host system can fix such
issue.  Somehow, one idea is to use ‘datefudge’ to detect such time
bomb and/or maybe fake an older time to pass some tests… but I am not
aware of any attempt to tackle these time bomb.

Aside, from my point of view, the 4 assumptions for time traveling with
Guix are:

 1. source code availability
 2. Linux kernel compatibility
 3. hardware compatibility
 4. no time bomb

and a lot of work remains for insuring a kind of validity of these.

Cheers,
simon


  parent reply	other threads:[~2023-04-07 17:27 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-07  7:47 Time travel accident Konrad Hinsen
2023-04-07  8:30 ` Josselin Poiret
2023-04-07 10:07   ` Julien Lepiller
2023-04-07 16:10   ` Konrad Hinsen
2023-04-07 17:39     ` Julien Lepiller
2023-04-11 15:20       ` Konrad Hinsen
2023-04-12 10:17         ` Konrad Hinsen
2023-04-12 14:09           ` Simon Tournier
2023-04-13  8:14             ` Konrad Hinsen
2023-04-12 11:03         ` Simon Tournier
2023-04-12 12:53           ` Konrad Hinsen
2023-04-07 17:26 ` Simon Tournier [this message]
2023-04-17 13:32 ` Ludovic Courtès
2023-04-17 17:50   ` Simon Tournier
2023-04-17 22:16     ` Vagrant Cascadian
2023-04-18  9:39       ` Simon Tournier

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=86zg7jk3hi.fsf@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.