From: Ricardo Wurmus <rekado@elephly.net>
To: znavko@tutanota.com
Cc: Help Guix <help-guix@gnu.org>
Subject: Re: guix-daemon is still of version 0.15.0
Date: Mon, 31 Dec 2018 23:14:53 +0100 [thread overview]
Message-ID: <87ef9xfin6.fsf@elephly.net> (raw)
In-Reply-To: <LV4c0y2--3-1@tutanota.com>
znavko@tutanota.com writes:
> - Why older version of guix can work with guix-daemon newer version?
> Can there be any conflicts? How does it work exactly?
The daemon has a limited role that is independent of package
definitions. Clients communicate with the daemon using a simple
protocol that has only seen very few changes over the years. The daemon
does not know anything about packages. It understands the format of
derivations, which is what Guix package definitions are “compiled” to.
As long as the derivation format doesn’t change, the daemon version
doesn’t really matter that much.
> The second question concerns guix-daemon in my system. I've discovered
> I still have guix-daemon-0.15.0 working process despite I've made
> `guix pull` from root and non-root user and using guix-0.16.0:
[…]
> - Why guix-daemon is still 0.15.0 while as root user has guix-0.16.0?
> How to upgrade it? Do I need something like `guix system upgrade`? -
> Manual has no such option.
Are you using GuixSD or do you use Guix on a foreign distribution? On
GuixSD you would periodically run “sudo -E guix system reconfigure
/etc/config.scm” to upgrade your system — including the daemon.
On a foreign distribution you need to check how the daemon is started –
via systemd or some other way? Maybe the service file references the
old daemon explicitly? To answer this we need a little more information
about how you installed Guix.
--
Ricardo
prev parent reply other threads:[~2019-01-01 10:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-31 18:56 guix-daemon is still of version 0.15.0 znavko
2018-12-31 22:14 ` Ricardo Wurmus [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=87ef9xfin6.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=help-guix@gnu.org \
--cc=znavko@tutanota.com \
/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).