From: Matthieu Haefele <matthieu.haefele@cnrs.fr>
To: zimoun <zimon.toutoune@gmail.com>
Cc: "Ludovic Courtès" <ludovic.courtes@inria.fr>,
58149-done@debbugs.gnu.org, 58149@debbugs.gnu.org
Subject: bug#58149: guix pull error
Date: Thu, 6 Oct 2022 17:15:35 +0200 [thread overview]
Message-ID: <8c72d04d-2ea1-849f-38d3-fc6bce6f7aec@cnrs.fr> (raw)
In-Reply-To: <CAJ3okZ0iHbr-4jKfHK9SqK4ifACBqH1UkYzDQkt18TA3mWjHkw@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 2309 bytes --]
Hi,
Le 06/10/2022 à 15:56, zimoun a écrit :
>
> Well, what do you think that could be helpful?
>
Personally, when I installed guix for the first time, I had very few clues on what it was, how it was working and I guess that's
the case for most people following the "installation" section of the doc. So I went for the "recommended way" with the shell
installer script, and as it did the job, when I arrived to the paragraph starting with "If you prefer to perform the installation
steps manually or want to tweak them", I just stopped reading and switched to examples using guix.
But I got the information that `guix pull` updates my guix installation. I understood later that a guix daemon was running and
actually executing in root space things I was asking. When I realised this, I did not realise that `guix pull` as simple user was
not updating the daemon. Thinking of it now, it looks obvious, but as a guix newbie, there is some much other things to absorb, it
is very easy to overlook it.
I would do at least the two following things :
1. If it is technically possible, depending on the difference between the current installed and the latest available versions of
the daemon, I would print at the end of a `guix pull`, a message asking for the upgrade of the guix daemon going from the notice
of these versions to a critical warning.
2. in the documentation, in "2 Installation", right after "Once installed, Guix can be updated by running guix pull (see Invoking
guix pull). ", I would add something like "From time to time it is needed to upgrade your guix installation (see Upgrading Guix)".
HTH !
More generally, the guix doc is very well written, compact and informative, but it is like an encyclopedia. You have to read it
almost entirely and extract the basics from large amounts of advanced features to get started. I totally agree with Konrad
Hinsen's comment on the documentation at the last 10 years birthday conference, some first level / tutorials like documentation is
missing. I took some notes during my guix learning process and I started to put them on this wiki page
<https://gitlab.inria.fr/fuentes/guix4n00bs/-/wikis/home> (well, in French...). I can try to find some time to go on with this
exercise ... if you find it relevant of course.
Best,
Mat
[-- Attachment #1.2: Type: text/html, Size: 2996 bytes --]
[-- Attachment #2: Signature cryptographique S/MIME --]
[-- Type: application/pkcs7-signature, Size: 4270 bytes --]
next prev parent reply other threads:[~2022-10-06 15:53 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
2022-10-06 12:14 ` Matthieu Haefele
2022-10-06 13:56 ` zimoun
2022-10-06 15:15 ` Matthieu Haefele [this message]
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=8c72d04d-2ea1-849f-38d3-fc6bce6f7aec@cnrs.fr \
--to=matthieu.haefele@cnrs.fr \
--cc=58149-done@debbugs.gnu.org \
--cc=58149@debbugs.gnu.org \
--cc=ludovic.courtes@inria.fr \
--cc=zimon.toutoune@gmail.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.
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).