From: Vagrant Cascadian <vagrant@debian.org>
To: 850644@bugs.debian.org
Cc: guix-devel@gnu.org
Subject: Re: #850644: RFP: Guix in Debian
Date: Tue, 28 May 2019 11:15:54 -0700 [thread overview]
Message-ID: <87v9xu4f8l.fsf@yucca> (raw)
In-Reply-To: <87sgte2ml5.fsf@yucca>
[-- Attachment #1: Type: text/plain, Size: 3840 bytes --]
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.html
>> 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ès 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
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next parent reply other threads:[~2019-05-28 18:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87y3gjtair.fsf@aikidev.net>
[not found] ` <87sgte2ml5.fsf@yucca>
2019-05-28 18:15 ` Vagrant Cascadian [this message]
[not found] ` <ef7a0d08649202ebb5617ef3974a5711@openmailbox.org>
2019-05-31 21:58 ` Bug#850644: #850644: RFP: Guix in Debian Ludovic Courtès
2019-06-14 21:42 ` Ludovic Courtès
2019-11-13 4:43 ` Vagrant Cascadian
2019-11-13 7:58 ` Jan Nieuwenhuizen
2019-11-13 8:07 ` Christopher Baines
2019-11-13 17:34 ` Diane Trout
2019-11-16 22:30 ` Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87v9xu4f8l.fsf@yucca \
--to=vagrant@debian.org \
--cc=850644@bugs.debian.org \
--cc=guix-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).