From: "Ludovic Courtès" <ludo@gnu.org>
To: Leo Famulari <leo@famulari.name>
Cc: Greg Hogan <code@greghogan.com>, guix-devel <guix-devel@gnu.org>
Subject: Re: Guix release broken without substitutes on ungrafted openssl
Date: Wed, 22 Feb 2023 00:20:09 +0100 [thread overview]
Message-ID: <87fsaybo7q.fsf@gnu.org> (raw)
In-Reply-To: <Y+0lfqRsMf99uLVy@jasmine.lan> (Leo Famulari's message of "Wed, 15 Feb 2023 13:33:34 -0500")
Leo Famulari <leo@famulari.name> skribis:
> On Wed, Feb 15, 2023 at 12:15:21PM -0500, Greg Hogan wrote:
>> Installing guix from source fails on the build of openssl@1.1.1l. I
>> see the same error on my working system (log attached) when executing
>> the command below. The issue looks to be caused by OpenSSL's expired
>> test certs fixed in 1.1.1p [0]. Guix currently grafts openssl 1.1.1s
>> but it seems grafts are not part of the bootstrap process (substitutes
>> disabled).
>>
>> If this is the correct diagnosis then we should be ungrafting before
>> future releases any bootstrap dependencies relating to build failures
>> (not necessarily for security updates).
>>
>> My personal fix was to adapt my installation script to iteratively set
>> back then reset the clock, as openssl only builds in the past but
>> diffutils-boot0 then fails due to newly created files being older than
>> distributed files.
>
> Thanks for the notes.
>
> I do believe this has been discussed previously, to be found in the
> archives!
Here: https://issues.guix.gnu.org/58650
I think the most viable/easily feasible option would be to run OpenSSL’s
tests under ‘datefudge’, as discussed in the issue above.
Ludo’.
next prev parent reply other threads:[~2023-02-21 23:20 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
2023-02-22 13:48 ` Simon Tournier
2023-02-21 23:20 ` Ludovic Courtès [this message]
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=87fsaybo7q.fsf@gnu.org \
--to=ludo@gnu.org \
--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).