From: zimoun <zimon.toutoune@gmail.com>
To: Matthieu Haefele <matthieu.haefele@cnrs.fr>
Cc: "Ludovic Courtès" <ludovic.courtes@inria.fr>, 58149@debbugs.gnu.org
Subject: bug#58149: guix pull error
Date: Thu, 6 Oct 2022 12:30:39 +0200 [thread overview]
Message-ID: <CAJ3okZ2_d_kZC=ASYSHun9q2ZFD2xbrNTwNAUUnfODFF8vTw3Q@mail.gmail.com> (raw)
In-Reply-To: <5b41d671-5d7c-b4dc-c91f-ce65fd6180cf@cnrs.fr>
Hi Matthieu,
On Thu, 6 Oct 2022 at 12:10, Matthieu Haefele <matthieu.haefele@cnrs.fr> wrote:
> Victory !!
\o/
> 1. What am I doing wrong to have stuck to this old guix daemon all this time ? Shall I run this `sudo -i guix pull` regularly to
> keep my daemon up to date ? But then it looks like I am the only one who faced this issue, weird, no ? And problems should have
> started back in February, but I intensively worked on guix this summer, including some `guix pull`... If reasons are not too
> complicated, I am interested in getting some insights.
When you run "guix pull" as a regular user, you just update the
profile ~/.config/guix/current which provides the 'guix' command used
by the user. Note that several users on the same machine can have
different versions.
When a regular user run 'guix <subcommand>', this talks with
'guix-daemon' and process many actions (store management etc.). Here
'guix-daemon' is usually provided by the profile
'/root/.config/guix/current' . Well, it is configured by systemd (or
any others), for instance see [1] considering 'readlink
/root/.config/guix/current' returns
/var/guix/profiles/per-user/root/current-guix.
Therefore, to update the guix-daemon which runs (started by systemd),
you need to update the profile /root/.config/guix' which is done by
running "guix pull" as root.
1: https://git.savannah.gnu.org/cgit/guix.git/tree/etc/guix-daemon.service.in#n9
Personally, I run "guix pull" as root (update the daemon) each every
while. ;-) Usually, at each new release and/or when I read (guix pull
--news; as regular user) something important.
> 2. We have tried out several things. If I have a colleague in a similar situation, could you confirm the following procedure:
>
> /var/guix/profiles/per-user/root/current-guix/bin/guix-daemon --version
> # should answer something like "guix-daemon (GNU Guix) 1.0.1"
>
> guix build \
> /gnu/store/n8vdar2f60mvq62g7mngpqwykbm9rw1q-guix-1.2.0rc2-1.0d4b1af
>
> sudo -i guix package --bootstrap -p /root/.config/guix/current \
> -r guix -i /gnu/store/n8vdar2f60mvq62g7mngpqwykbm9rw1q-guix-1.2.0rc2-1.0d4b1af
>
> systemctl restart guix-daemon
>
> /var/guix/profiles/per-user/root/current-guix/bin/guix-daemon --version
> # should answer "guix-daemon (GNU Guix) 1.2.0rc2-1.0d4b1af"
>
> sudo -i guix pull
>
> systemctl restart guix-daemon
>
> /var/guix/profiles/per-user/root/current-guix/bin/guix-daemon --version
> # should answer something like "guix-daemon (GNU Guix) 1.3.0-30.17134b9"
Well, I cannot confirm the store name as
/gnu/store/n8vdar2f60mvq62g7mngpqwykbm9rw1q-guix-1.2.0rc2-1.0d4b1af.
Personally, I also miss how Ludo found these items. :-)
Ludo, do you think it would be worth to implement a transition plan
for this kind of situation?
Cheers,
simon
PS: Feel free to reply to 58149-done@debbugs.gnu.org if you consider
the bug is now fixed. :-)
next prev parent reply other threads:[~2022-10-06 10:32 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-28 15:47 bug#58149: guix pull error Matthieu Haefele
2022-09-28 22:06 ` zimoun
2022-09-29 13:37 ` Ludovic Courtès
2022-09-29 15:04 ` Matthieu Haefele
2022-09-29 15:15 ` Ludovic Courtès
2022-09-29 15:35 ` Matthieu Haefele
2022-09-29 17:55 ` Maxime Devos
2022-09-30 6:09 ` Matthieu Haefele
2022-09-30 7:59 ` Ludovic Courtès
2022-09-30 9:42 ` Matthieu Haefele
2022-10-03 9:04 ` bug#58149: Letting clients warn about old daemons Ludovic Courtès
2022-10-03 15:12 ` Maxim Cournoyer
2022-10-03 9:17 ` bug#58149: guix pull error Ludovic Courtès
2022-10-03 9:33 ` Matthieu Haefele
2022-10-03 14:03 ` Ludovic Courtès
2022-10-03 14:49 ` Matthieu Haefele
2022-10-04 10:11 ` Ludovic Courtès
2022-10-04 13:01 ` Matthieu Haefele
2022-10-05 9:34 ` Ludovic Courtès
2022-10-05 10:47 ` Matthieu Haefele
2022-10-05 10:52 ` Matthieu Haefele
2022-10-05 15:02 ` zimoun
2022-10-05 15:08 ` Matthieu Haefele
2022-10-06 8:47 ` Ludovic Courtès
2022-10-06 10:10 ` Matthieu Haefele
2022-10-06 10:30 ` zimoun [this message]
2022-10-06 12:14 ` Matthieu Haefele
2022-10-06 13:56 ` zimoun
2022-10-06 15:15 ` Matthieu Haefele
2022-10-06 15:38 ` zimoun
2022-10-06 16:00 ` Maxime Devos
2022-10-06 16:01 ` Ludovic Courtès
2022-10-06 10:57 ` Maxime Devos
2022-10-06 12:08 ` Matthieu Haefele
2022-10-06 15:56 ` Maxime Devos
2022-10-06 15:58 ` Ludovic Courtès
2022-10-05 14:36 ` Matthieu Haefele
2022-10-07 2:40 ` bokr
2022-10-14 12:19 ` zimoun
2022-10-03 20:47 ` bug#58149: Unable to pull when using a pre-lzip version of guix-daemon Ricardo Wurmus
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='CAJ3okZ2_d_kZC=ASYSHun9q2ZFD2xbrNTwNAUUnfODFF8vTw3Q@mail.gmail.com' \
--to=zimon.toutoune@gmail.com \
--cc=58149@debbugs.gnu.org \
--cc=ludovic.courtes@inria.fr \
--cc=matthieu.haefele@cnrs.fr \
/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).