unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Simon Tournier <zimon.toutoune@gmail.com>
To: "Ludovic Courtès" <ludovic.courtes@inria.fr>
Cc: Vagrant Cascadian <vagrant@debian.org>, 72135@debbugs.gnu.org
Subject: bug#72135: Debian ‘guix’ package lacks zstd support
Date: Thu, 18 Jul 2024 12:23:18 +0200	[thread overview]
Message-ID: <87jzhjknhl.fsf@gmail.com> (raw)
In-Reply-To: <87y15zxizs.fsf@inria.fr>

Hi,

On Thu, 18 Jul 2024 at 09:21, Ludovic Courtès <ludovic.courtes@inria.fr> wrote:

>> That said, after “apt install guix”, does the guix-daemon update work?
>> Somehow if “guix pull” as root fails after a fresh install via APT, then
>> it’s a bug on Guix side, else it’s a bug on Debian side tracked by
>> 1072918. :-)
>
> Upgrading guix-daemon when it was originally installed with apt is
> tricky: you need to modify /etc/systemd/system/guix-daemon.service so
> that it refers to the one in /var/guix/….  So I think few people upgrade
> the daemon on Debian.

Indeed.  Even, let note that the default configuration provided by Guix
seems patched by Debian [1].

So yeah the only way is to modify
/etc/systemd/system/guix-daemon.service  and restart the service.

> I’m not sure how to improve on that; we could document it under
> “Upgrading Guix” at least.

Well, yes the documentation on our side is a good start. :-)

Then, I do not know either how to improve on that.  I mean a typical
Debian cycle is 3-5 years for a release – oldstable Debian (Bulleye)
provides guix-daemon version 1.2.0 – then it would mean we must support
backward compatibility for substitutes to this all range; as Vagrant
warned in [2]. :-)

Well, patches could be accepted for fixing security in guix-daemon but I
am not convinced patches for some new/deprecated features would be
accepted.

Maybe we could provide some patches for oldstable Debian that modify
guix-daemon.service and friends.  Vagrant wrote [3]:

        It is of course possible to configure to use an updated guix-daemon from
        a user's profile (e.g. as recommended with guix-binary installation on a
        foreign distro), but out-of-the-box it uses the guix-daemon shipped in
        the package, which, at least with my Debian hat on, is how it should be.

So I do not know what would be the best here. :-)


Cheers,
simon


1: https://salsa.debian.org/debian/guix/-/blob/b1d0628cbedea22f175a463f4c4935d02601bf93/debian/patches/guix-services-from-usr-bin

2: Re: Are gzip-compressed substitutes still used?
Vagrant Cascadian <vagrant@debian.org>
Wed, 17 Mar 2021 11:08:38 -0700
id:87o8fhwt3t.fsf@yucca
https://lists.gnu.org/archive/html/guix-devel/2021-03
https://yhetil.org/guix/87o8fhwt3t.fsf@yucca

3: Re: Are gzip-compressed substitutes still used?
Vagrant Cascadian <vagrant@debian.org>
Thu, 18 Mar 2021 09:00:20 -0700
id:87eegcwiy3.fsf@yucca
https://lists.gnu.org/archive/html/guix-devel/2021-03
https://yhetil.org/guix/87eegcwiy3.fsf@yucca




      reply	other threads:[~2024-07-18 11:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-16  8:41 bug#72135: Debian ‘guix’ package lacks zstd support Ludovic Courtès
2024-07-17 17:18 ` Simon Tournier
2024-07-18  7:21   ` Ludovic Courtès
2024-07-18 10:23     ` Simon Tournier [this message]

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=87jzhjknhl.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=72135@debbugs.gnu.org \
    --cc=ludovic.courtes@inria.fr \
    --cc=vagrant@debian.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).