From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp0 ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms11 with LMTPS id AJvhLfelhV+ZLAAA0tVLHw (envelope-from ) for ; Tue, 13 Oct 2020 13:04:55 +0000 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp0 with LMTPS id YPO+KfelhV/faAAA1q6Kng (envelope-from ) for ; Tue, 13 Oct 2020 13:04:55 +0000 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 0D4AB9402A7 for ; Tue, 13 Oct 2020 13:04:54 +0000 (UTC) Received: from localhost ([::1]:51560 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kSJz3-0003nB-11 for larch@yhetil.org; Tue, 13 Oct 2020 09:04:53 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:36554) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kSJyV-0003lG-G9 for guix-devel@gnu.org; Tue, 13 Oct 2020 09:04:19 -0400 Received: from fencepost.gnu.org ([2001:470:142:3::e]:35117) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kSJyU-0006F4-JK; Tue, 13 Oct 2020 09:04:18 -0400 Received: from [2001:660:6102:320:e120:2c8f:8909:cdfe] (port=44096 helo=ribbon) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1kSJyU-0002wD-79; Tue, 13 Oct 2020 09:04:18 -0400 From: =?utf-8?Q?Ludovic_Court=C3=A8s?= To: Danny Milosavljevic Subject: Re: Problem bootstrapping Guix - "make update-guix-package" result: no code for module (gcrypt hash) References: <20200924174705.572790b1@scratchpost.org> <87blhg27bb.fsf@gnu.org> <20201012102225.309e50c5@scratchpost.org> X-URL: http://www.fdn.fr/~lcourtes/ X-Revolutionary-Date: 22 =?utf-8?Q?Vend=C3=A9miaire?= an 229 de la =?utf-8?Q?R=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: Tue, 13 Oct 2020 15:04:15 +0200 In-Reply-To: <20201012102225.309e50c5@scratchpost.org> (Danny Milosavljevic's message of "Mon, 12 Oct 2020 10:22:25 +0200") Message-ID: <87y2kajn00.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-BeenThere: guix-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: guix-devel@gnu.org Errors-To: guix-devel-bounces+larch=yhetil.org@gnu.org Sender: "Guix-devel" X-Scanner: scn0 Authentication-Results: aspmx1.migadu.com; dkim=none; dmarc=pass (policy=none) header.from=gnu.org; spf=pass (aspmx1.migadu.com: domain of guix-devel-bounces@gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=guix-devel-bounces@gnu.org X-Spam-Score: -1.51 X-TUID: XhlP5WaEAYcA Hi Danny, Danny Milosavljevic skribis: > I'm doing a project for Heads where we are trying to switch over their bu= ild > system to something that makes their builds more reproducible (for example > Guix). > > They are using github and gitlab test runners for a lot of things, so one= of > the ways we are trying to do continuous integration is to do the followin= g: > > (1) Have guix-the-package-manager be built and published on > repository.gitlab.com. It eventually does "./pre-inst-env guix pack guix" > and then puts the result into a new docker container. I can't see how to= do that > after a guix pull. Note that I don't want to also carry garbage (this en= tire > thing has to be verified for security eventually, so...). Currently, guix > is being bootstrapped from Alpine, and I don't want Alpine to remain in t= here. Why not just run =E2=80=9Cguix pack guix=E2=80=9D with a =E2=80=9Cguix pull= =E2=80=9D-provided Guix? You=E2=80=99d benefit from transparency and provenance tracking, the reduced binary seeds, etc., which is very different from what you get by building on top of Alpine. If you need a specific Guix commit, you can also run: guix pack guix \ --with-commit=3Dguix=3Da2ed00f79fd5bf69c6cca3fa7bdc62726bf848fa \ --with-git-url=3Dguix=3Dhttps://git.savannah.gnu.org/git/guix.git You can still get test failures if there=E2=80=99s a problem on that commit= , as we=E2=80=99ve seen before, but apart from that it looks like what you need = no? (The =E2=80=98--with-git-url=E2=80=99 is only necessary because the default= URL uses the =E2=80=9Cdumb=E2=80=9D transparent, which libgit2 apparently dislikes.) > (2) Use the result in order to build boards using tiny Dockerfiles > which would just say > > FROM repository.gitlab.com/guix-on-docker > RUN guix build heads-kgpe-d16 > > and throw away the derivation (or publish it, too?)--but keep the log file > and exit status. Then again, why even go through Docker? You could just as well in one go do: guix time-machine --commit=3Da2ed00f79fd5bf69c6cca3fa7bdc62726bf848fa -- \ build heads-kgpe-d16 I=E2=80=99ve used Guix with GitLab-CI for instance, and it makes absolutely= no sense to me to resort to Docker if you already have Guix running. > Note that (1) should pin a specific Guix commit for a long time since Hea= ds > does not want to build on a moving target since they do hash verification > on bootup, and firmware is hard to keep working (i.e. someone has to > manually verify, on real hardware, whether stuff still works after an > update of the toolchain). And Heads basically is ONLY security-relevant > stuff. An additional reason to avoid hopping through Alpine=E2=80=A6 HTH! Ludo=E2=80=99.