From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp2 ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms11 with LMTPS id sJz6EnK3rV/1bwAA0tVLHw (envelope-from ) for ; Thu, 12 Nov 2020 22:30:10 +0000 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp2 with LMTPS id uNrCDnK3rV83OgAAB5/wlQ (envelope-from ) for ; Thu, 12 Nov 2020 22:30:10 +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 076249406F7 for ; Thu, 12 Nov 2020 22:30:09 +0000 (UTC) Received: from localhost ([::1]:58318 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kdL6W-0006ey-QC for larch@yhetil.org; Thu, 12 Nov 2020 17:30:08 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]:34184) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kdKRA-0008Qp-57 for guix-devel@gnu.org; Thu, 12 Nov 2020 16:47:24 -0500 Received: from dustycloud.org ([2600:3c02::f03c:91ff:feae:cb51]:49842) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kdKR7-0003g9-Pd for guix-devel@gnu.org; Thu, 12 Nov 2020 16:47:23 -0500 Received: from twig (localhost [127.0.0.1]) by dustycloud.org (Postfix) with ESMTPS id 6DDD226650; Thu, 12 Nov 2020 16:46:32 -0500 (EST) References: <875z6atqic.fsf@yucca> User-agent: mu4e 1.4.13; emacs 27.1 From: Christopher Lemmer Webber To: Vagrant Cascadian Subject: Re: Guix now in Debian experimental! In-reply-to: <875z6atqic.fsf@yucca> Date: Thu, 12 Nov 2020 16:46:03 -0500 Message-ID: <87tutumep0.fsf@dustycloud.org> MIME-Version: 1.0 Content-Type: text/plain Received-SPF: pass client-ip=2600:3c02::f03c:91ff:feae:cb51; envelope-from=cwebber@dustycloud.org; helo=dustycloud.org X-detected-operating-system: by eggs.gnu.org: No matching host in p0f cache. That's all we know. X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action 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: ns3122888.ip-94-23-21.eu Authentication-Results: aspmx1.migadu.com; dkim=none; dmarc=none; 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.01 X-TUID: SBJauQrpwQIu This! Is! Awesome! I think Guix in Debian could be huge and help both massively. Well, I've said so more than once in the past. I believe it! What's easy to package in one tends to be easy to package in the other. Just imagine if we encouraged more developers using Debian as their host OS to use "guix environment" (or eventually "guix shell") for their development environments instead of one million incompatible language package managers! Vagrant Cascadian writes: > It's been a long haul getting all the build dependencies of guix into > Debian, but it has finally paid off: > > https://tracker.debian.org/pkg/guix > > So now you can install guix from Debian's experimental distribution! > > It is not well tested, in fact, I had to disable many tests, because in > Debian it is a policy violation to download from the network during a > build, but unlike guix, the policy is not necessarily enforced in any > technical way! > > Many of the tests call out to the network in one way or another... So, > this lead to: > > Support GUIX_DISABLE_NETWORK_TESTS environment variable > https://issues.guix.gnu.org/44491 > > Though I since learned about RES_OPTIONS=attempts:0 to disable name > resolution in glibc instead, still working on refactoring tests/*.sh to > make use of some common functions. > > > There are many tests that make use of bootstrap binaries which attempt > to download them during running the tests, despite networking not being > available. I have patched these tests to also not run when the network > is unreachable: > > https://salsa.debian.org/debian/guix/-/tree/debian/devel/debian/patches > > My guess is these bootstrap binaries are available as inputs during the > guix package builds of guix? > > > I've also patched out a few tests that seemed non-deterministic, and a > few that were simply inscrutible as to why they failed. Probably need to > file bugs about those at some point... :) > > > I also switched the packages to only run the tests in series, just in > case parallelism was triggering issues with the tests: > > https://issues.guix.gnu.org/21097 > > > In all, this ends up disabling about 200 out of 1100 tests in the Debian > packages. I will explore another option to run those tests outside of > the build, where network can be used, against the installed package > using: > > https://ci.debian.net > > > It actually builds on both amd64 and i386 with some of the above > mentioned tests disabled: > > https://buildd.debian.org/status/package.php?p=guix&suite=experimental > > On armhf (ARMv7), it successfully built, but failed some test suites > that passed on amd64/i386. > > On armel (ARMv4t?), where it probably shouldn't even attempt to build, > it failed in the same way it failed on armhf... > > On arm64, guile-gnutls isn't available for guile-3.0, so it cannot > build: > > https://bugs.debian.org/966714 > > An alternative would be to build guix against guile-2.2, which has > guile-gnutls, although I did manage to find... more test suite failures > on guile-2.2 (tests/lint.scm), including one which seemed to run > indefinitely(tests/swh.scm), an infinitely thorough test! > > If the guile-gnutls issues do not get sorted out soon, building against > guile-2.2 is a plausible backup plan for getting guix 1.2 into the next > Debian release (speculated to be released mid 2021)... > > > For other architectures, it would require considerably more courage, > though there has been work on a few of those architectures in guix > recently (e.g. hurd-i386, mips64el, powerpc, ppc64, ppc64el, and even > talk of riscv64). Would it be interesting to run guix on one of the > more exotic architectures, Debian GNU/kFreeBSD? :) > > > Well, thanks for reading the status update from your entirely unofficial > Debian-Guix or Guix-Debian ambassador. > > > live well, > vagrant