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 14:14:02 +0200 [thread overview]
Message-ID: <6e1eb933-bb44-1337-3e04-e803c39b947f@cnrs.fr> (raw)
In-Reply-To: <CAJ3okZ2_d_kZC=ASYSHun9q2ZFD2xbrNTwNAUUnfODFF8vTw3Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1101 bytes --]
Le 06/10/2022 à 12:30, zimoun a écrit :
> On Thu, 6 Oct 2022 at 12:10, Matthieu Haefele <matthieu.haefele@cnrs.fr> wrote:
>
>
>> 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.
>
> 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.
Thanks for the explaination, it confirms what I understood. Maybe the three lines above should be part of some best practise or
documentation, especially for people like me running guix on a foreign distro without using the distro's package manager. I do not
remember having seen such recommendation.
Thanks again
Best,
Mat
[-- Attachment #2: Signature cryptographique S/MIME --]
[-- Type: application/pkcs7-signature, Size: 4270 bytes --]
next prev parent reply other threads:[~2022-10-06 12:52 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 [this message]
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=6e1eb933-bb44-1337-3e04-e803c39b947f@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).