From: Greg Hogan <code@greghogan.com>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Guix release broken without substitutes on ungrafted openssl
Date: Wed, 15 Feb 2023 15:04:43 -0500 [thread overview]
Message-ID: <CA+3U0Z=iHNLEMg6bLz5gxnFmz1CHZYh7NgusWW+hJ+akNcRb=A@mail.gmail.com> (raw)
In-Reply-To: <Y+0lfqRsMf99uLVy@jasmine.lan>
On Wed, Feb 15, 2023 at 1:33 PM Leo Famulari <leo@famulari.name> wrote:
>
> It only really affects distros like Guix or Nix, so it's our problem to
> fix.
I forgot to mention that I also needed to switch the pull url from
https to http, otherwise git would fail on certificate verification. I
believe this is secure with Guix handling the git authentication.
I see the same openssl@1.1.1l error when building with the system
clock set to 2022/12/19, the date of the 1.4.0 release, so it appears
that the release was never bootstrappable without hijinks.
For the general case perhaps there could be a way to describe the
build environment similar to the manifest and channels. Could a build
date be specified and faketime used similar to how Guix makes use of
fakeroot? Perhaps this has already been proposed in the archive.
Greg
next prev parent reply other threads:[~2023-02-15 20:05 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 [this message]
2023-02-16 11:47 ` Simon Tournier
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='CA+3U0Z=iHNLEMg6bLz5gxnFmz1CHZYh7NgusWW+hJ+akNcRb=A@mail.gmail.com' \
--to=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).