[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Time travel accident
From: |
Simon Tournier |
Subject: |
Re: Time travel accident |
Date: |
Fri, 07 Apr 2023 19:26:49 +0200 |
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
- Re: Time travel accident, (continued)
- Re: Time travel accident, Josselin Poiret, 2023/04/07
- Re: Time travel accident, Julien Lepiller, 2023/04/07
- Re: Time travel accident, Konrad Hinsen, 2023/04/07
- Re: Time travel accident, Julien Lepiller, 2023/04/07
- Re: Time travel accident, Konrad Hinsen, 2023/04/11
- Re: Time travel accident, Konrad Hinsen, 2023/04/12
- Re: Time travel accident, Simon Tournier, 2023/04/12
- Re: Time travel accident, Konrad Hinsen, 2023/04/13
- Re: Time travel accident, Simon Tournier, 2023/04/12
- Re: Time travel accident, Konrad Hinsen, 2023/04/12
Re: Time travel accident,
Simon Tournier <=
Re: Time travel accident, Ludovic Courtès, 2023/04/17