From mboxrd@z Thu Jan 1 00:00:00 1970 From: Vagrant Cascadian Subject: Re: #850644: RFP: Guix in Debian Date: Tue, 28 May 2019 11:15:54 -0700 Message-ID: <87v9xu4f8l.fsf@yucca> References: <87y3gjtair.fsf@aikidev.net> <87sgte2ml5.fsf@yucca> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([209.51.188.92]:51098) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hVgdz-0006go-5r for guix-devel@gnu.org; Tue, 28 May 2019 14:16:16 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hVgdx-0001Zk-7V for guix-devel@gnu.org; Tue, 28 May 2019 14:16:15 -0400 Received: from cascadia.aikidev.net ([2600:3c01:e000:267:0:a171:de7:c]:52252) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hVgdv-0001Ru-9P for guix-devel@gnu.org; Tue, 28 May 2019 14:16:13 -0400 In-Reply-To: <87sgte2ml5.fsf@yucca> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: 850644@bugs.debian.org Cc: guix-devel@gnu.org --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Control: block 850644 by 902174 Status update: technically working package! Needs more work within Debian to actually include it... On 2019-05-16, Vagrant Cascadian wrote: > On 2018-05-16, Vagrant Cascadian wrote: >> The main build/runtime dependencies missing from Debian appear to be >> guile-git, and possibly a recommends on guile-ssh: >> >> https://www.gnu.org/software/guix/manual/html_node/Building-from-Git.h= tml >> https://www.gnu.org/software/guix/manual/html_node/Requirements.html > > Apparently, guix has grown a few additional dependencies since then... > > So in a bit of a focused run of packaging, I've been chasing the > dependency chain necessary to get guix building on Debian: > > * guile-gnutls needs to be (re)enabled in libgnutls*: > > https://salsa.debian.org/vagrant/gnutls Proposed a patch to re-enable: https://bugs.debian.org/905272#29 > * guile-json needs to be updated to version 1.2.0 (3.x is incompatible), > and I've pushed wip branches updating packaging for new upstream > versions: > > https://salsa.debian.org/debian/guile-json Updated to 1.2.0 in Debian experimental. A little awkward not updating to the newest upstream version, but hopefully that won't last forever... > * I've gotten some packaging for guile-git, guile-gcrypt, guile-ssh and > guile-sqlite3 which need some more polish and then uploading to > Debian: > > https://salsa.debian.org/vagrant/guile-gcrypt > https://salsa.debian.org/vagrant/guile-sqlite3 Uploaded and waiting in NEW for review: https://ftp-master.debian.org/new/guile-gcrypt_0.1.0-1.html https://ftp-master.debian.org/new/guile-sqlite3_0.1.0-1.html > https://salsa.debian.org/vagrant/guile-git Waiting for guile-bytestructures to get through NEW. > https://salsa.debian.org/vagrant/guile-ssh This is WIP, packaging needs some policy compliance issues addressed. > * guile-git required scheme-bytestructures, which I've packaged, and > needs to be uploaded before guile-git can be: > > https://salsa.debian.org/vagrant/scheme-bytestructures Uploaded and waiting in NEW for review: https://ftp-master.debian.org/new/scheme-bytestructures_1.0.5-1.html > After all that, I did get to the point where I could at least try to > compile guix: > > https://salsa.debian.org/vagrant/guix With local builds of the above packages, I've got a working guix package! It still needs a way to get the bootstrap binaries (bash, mkdir, tar and xz) from Guix; right now they're binaries shipped in the source! Ludovic Court=C3=A8s worked on a patch that would in theory download those = at run-time, but that is not yet working... I tried with using symlinks to the host's bash, mkdir tar and xz, but that resulted in the symlink getting copied into the store, which meant that the package build environment only ended up included a dead symlink and failed to build. Additionally, not using the exact same bootstrap binaries means that Guix's substitute servers would produce different results for all packages, and so substitutes wouldn't be able to be very useful. Bootstrapping the system with MES is also WIP in Guix, and it might be possible to build identical bootstrap binaries using MES in Debian at some point: https://bugs.debian.org/902174 The guix packaging for Debian also has a small number of test failures, at least one of which simply needs to be disabled because it accesses the network (which violates Debian policy). Also needs some updates to the packaging to get the guix-daemon running out of the box, for which there's a provided systemd service, and adding some guixbuild users, which shouldn't be too hard. So, still a lot to be done, but considerable progress! live well, vagrant --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iHUEARYKAB0WIQRlgHNhO/zFx+LkXUXcUY/If5cWqgUCXO162gAKCRDcUY/If5cW qu6QAPwLL43eaibpjNb0vH+raqzVH+0cigtbE4mH6F74eGK6AwEAyXn1JdoiL+yd 3O47LYRXgUgVYVgopLhN6UQ4H6MzFA8= =IZrz -----END PGP SIGNATURE----- --=-=-=--