From: Vagrant Cascadian <vagrant@debian.org>
To: Adriano Peluso <randomlooser@riseup.net>, help-guix <help-guix@gnu.org>
Subject: Re: updating the daemon on Debian 11
Date: Thu, 09 Sep 2021 11:54:58 -0700 [thread overview]
Message-ID: <87o891pojh.fsf@yucca> (raw)
In-Reply-To: <905ed7a6a5daabb6e208e88dda9872398d180976.camel@riseup.net>
[-- Attachment #1: Type: text/plain, Size: 1298 bytes --]
On 2021-09-09, Adriano Peluso wrote:
> I learned that in Debian 11 one can install Guix through apt
apt install guix
That *should* start the daemon, enable substitutes, create the build
users, etc. You shouldn't have to do anything manually. It will, of
course, be a relatively old version of guix (1.2 in bullseye/stable, 1.3
in unstable/experimental) but you can update guix in the typical ways...
It is pretty similar to a foreign distro install from guix's binary
releases, for the differences, see /usr/share/doc/guix/README.Debian*
> What about updating the daemon ?
The short of it is, the daemon doesn't get updated. It shouldn't need to
most of the time... If there are daemon-relevent security updates, then
you get updates via "apt update && apt upgrade".
You can of course override that and manually configure guix-daemon that
you build in, say, root's profile if you want and need some new features
in the daemon.
> What's the procedure for a Guix installed through apt ?
apt install guix
> And what's the procedure for updating a user profile ?
Same as on any guix installation:
guix pull
guix upgrade
To some extent, it just provides a trust path from Debian to getting a
guix that you then update through the normal guix mechanisms...
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2021-09-09 18:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-09 16:46 updating the daemon on Debian 11 Adriano Peluso
2021-09-09 18:34 ` jbranso
2021-09-09 18:54 ` Vagrant Cascadian [this message]
2021-09-10 12:43 ` Adriano Peluso
2021-09-09 21:57 ` jbranso
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=87o891pojh.fsf@yucca \
--to=vagrant@debian.org \
--cc=help-guix@gnu.org \
--cc=randomlooser@riseup.net \
/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.
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).