From debbugs-submit-bounces@debbugs.gnu.org Fri Feb 19 10:34:00 2021 Received: (at 44559) by debbugs.gnu.org; 19 Feb 2021 15:34:00 +0000 Received: from localhost ([127.0.0.1]:50176 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1lD7n5-0006tq-SP for submit@debbugs.gnu.org; Fri, 19 Feb 2021 10:34:00 -0500 Received: from eggs.gnu.org ([209.51.188.92]:55422) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1lD7n3-0006td-SU for 44559@debbugs.gnu.org; Fri, 19 Feb 2021 10:33:58 -0500 Received: from fencepost.gnu.org ([2001:470:142:3::e]:50722) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lD7my-0005vm-HC; Fri, 19 Feb 2021 10:33:52 -0500 Received: from [2001:660:6102:320:e120:2c8f:8909:cdfe] (port=49938 helo=ribbon) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1lD7mx-0004f5-FF; Fri, 19 Feb 2021 10:33:51 -0500 From: =?utf-8?Q?Ludovic_Court=C3=A8s?= To: Carl Dong Subject: Re: bug#44559: References: <87d00los2d.fsf@cbaines.net> X-URL: http://www.fdn.fr/~lcourtes/ X-Revolutionary-Date: 1 =?utf-8?Q?Vent=C3=B4se?= an 229 de la =?utf-8?Q?R?= =?utf-8?Q?=C3=A9volution?= X-PGP-Key-ID: 0x090B11993D9AEBB5 X-PGP-Key: http://www.fdn.fr/~lcourtes/ludovic.asc X-PGP-Fingerprint: 3CE4 6455 8A84 FDC6 9DB4 0CFB 090B 1199 3D9A EBB5 X-OS: x86_64-pc-linux-gnu Date: Fri, 19 Feb 2021 16:33:48 +0100 In-Reply-To: (Carl Dong's message of "Tue, 16 Feb 2021 16:00:11 -0500") Message-ID: <87lfbkkr6r.fsf@gnu.org> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Spam-Score: -0.7 (/) X-Debbugs-Envelope-To: 44559 Cc: 44559@debbugs.gnu.org, Mathieu Othacehe , Christopher Baines X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.7 (-) Hi Carl, Carl Dong skribis: > As bitcoin core begins the planning to officially transition to Guix-base= d releases, I've had many community members build guix v1.2.0 from source a= nd afterward attempt `--bootstrap --no-substitutes` builds. As you may imag= ine, they are getting stuck on this gnutls problem and cannot proceed furth= er. Yeah. :-/ > I'm wondering: > > 1. Is there a workaround that does not involve changing the system time? = We have attempted several flags: > 1. --with-graft=3Dgnutls=3Dgnutls@3.6.14 > 2. --without-tests=3Dgnutls > 3. --with-input=3Dgnutls=3Dgnutls@3.6.14 > These attempts all failed to work around this bug, and I=E2=80=99m curio= us 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? =E2=80=98--without-tests=E2=80=99 should work, but you need to pass the rig= ht version number I guess? > 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 poten= tial bootstrap problems) fixed? (Happy to discuss in separate thread if mor= e appropriate) I agree it=E2=80=99s a problem, and yes, it would probably be a good idea to release 1.2.1 with the upgraded GnuTLS we now have in =E2=80=98master=E2=80= =99. Longer-term, we need to find a way to address or avoid this issue. A brute-force approach would be to have the build machines at ci.guix run with a clock ten years ahead. That should generally be fine since the only place where timestamps matter are unmodified upstream tarballs. In all other cases, mtime is set to 1. Perhaps we could start by testing this hypothesis on a separate build farm. Chris, Mathieu, WDYT? Thanks, Ludo=E2=80=99.