all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Carl Dong <contact@carldong.me>
Cc: 44559@debbugs.gnu.org
Subject: bug#44559:
Date: Tue, 16 Feb 2021 16:49:58 -0500	[thread overview]
Message-ID: <YCw+Bh1532zjxRRA@jasmine.lan> (raw)
In-Reply-To: <CF6115A8-8536-4087-BC71-F6BC05D74F4F@carldong.me>

On Tue, Feb 16, 2021 at 04:00:11PM -0500, Carl Dong wrote:
> Hi all,
> 
> As bitcoin core begins the planning to officially transition to Guix-based releases, I've had many community members build guix v1.2.0 from source and afterward attempt `--bootstrap --no-substitutes` builds. As you may imagine, they are getting stuck on this gnutls problem and cannot proceed further.
> 
> I'm wondering:
> 
> 1. Is there a workaround that does not involve changing the system time? We have attempted several flags:
> 	1. --with-graft=gnutls=gnutls@3.6.14
> 	2. --without-tests=gnutls
> 	3. --with-input=gnutls=gnutls@3.6.14
> 	These attempts all failed to work around this bug, and I’m curious as to why that would be. My guess would be that when we do `--bootstrap`, Guix bootstraps itself first without taking into account these flags?
> 
> 2. Since bootstrappability is one of the core tenets of Guix, might it be appropriate to cut a v1.2.1 release with this problem (and any other potential bootstrap problems) fixed? (Happy to discuss in separate thread if more appropriate)

You should see what the Guix maintainers say about this.

My personal opinion is that you should fork Guix your use case. If you
are building from the bootstrap, there is little added cost to making
minor adjustments like disabling this test. You can periodically re-sync
your fork with GNU Guix as convenient. And it's probably more in tune
with your threat model. [0]

This problem of "expiring software" has occurred several times in Guix's
history and I'm sure it will happen again. In general, users are
expected to use substitutes to work around it. They are no worse off
than with traditional binary distros in that case.

[0] Savannah is great but lacking the resources to devote to security.




  reply	other threads:[~2021-02-16 21:51 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-10 20:49 bug#44559: gnutls 3.6.12 fails to build: FAIL: status-request-revoked Christopher Baines
2020-11-12 21:06 ` Ludovic Courtès
2020-11-12 21:18   ` Marius Bakke
2020-11-15 11:05     ` Ludovic Courtès
2020-12-31  0:27 ` bug#44559: Solution jeremiah
2021-02-16 21:00 ` bug#44559: Carl Dong
2021-02-16 21:49   ` Leo Famulari [this message]
2021-02-19 15:33   ` bug#44559: Ludovic Courtès
2021-02-19 18:32     ` bug#44559: Maxime Devos
2021-02-20 13:46       ` bug#44559: Ludovic Courtès
2021-02-20 14:12         ` bug#44559: Detecting “expiring” builds Ludovic Courtès
2021-02-19 23:49     ` bug#44559: Carl Dong
2021-02-22 22:36     ` bug#44559: Christopher Baines
2021-02-23  8:41       ` bug#44559: Ludovic Courtès
2021-02-23  8:55         ` bug#44559: Christopher Baines
2022-07-13 15:03         ` bug#44559: gnutls 3.6.12 fails to build: FAIL: status-request-revoked Maxim Cournoyer
2022-07-15 13:17           ` Ludovic Courtès
2022-07-16  1:33             ` Maxim Cournoyer

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=YCw+Bh1532zjxRRA@jasmine.lan \
    --to=leo@famulari.name \
    --cc=44559@debbugs.gnu.org \
    --cc=contact@carldong.me \
    /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.