[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#44559:
From: |
Carl Dong |
Subject: |
bug#44559: |
Date: |
Tue, 16 Feb 2021 16:00:11 -0500 |
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)
Cheers,
Carl Dong
contact@carldong.me
"I fight for the users"