unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludovic.courtes@inria.fr>
To: Matthieu Haefele <matthieu.haefele@cnrs.fr>
Cc: 58149@debbugs.gnu.org, zimoun <zimon.toutoune@gmail.com>
Subject: bug#58149: guix pull error
Date: Thu, 06 Oct 2022 17:58:09 +0200	[thread overview]
Message-ID: <87czb5j65q.fsf@inria.fr> (raw)
In-Reply-To: <5b41d671-5d7c-b4dc-c91f-ce65fd6180cf@cnrs.fr> (Matthieu Haefele's message of "Thu, 6 Oct 2022 12:10:56 +0200")

Hi!

Matthieu Haefele <matthieu.haefele@cnrs.fr> skribis:

> Victory !!
>
>     (base) mhaefele@mdlspc113:tmp $ /var/guix/profiles/per-user/root/current-guix/bin/guix-daemon --version
>     guile: warning: failed to install locale
>     guix-daemon (GNU Guix) 1.3.0-30.17134b9
>
> And the `guix pull` runs smoothly now, thanks a lot  :)

Yay, who would have thought?!  :-)

Thanks for persevering.  At lease we have a shorter path now next time
someone hits the problem.

> Now it is fixed I have two questions:
> 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.

The daemon changes, gets bug fixes, new features, support for new
compression algorithms, optimizations, etc., but the client/daemon
interface is stable.  Thus, one rarely needs to upgrade the daemon, but
it’s a good idea to update it once in a while.

On Guix System, that happens automatically when you reconfigure your
system, but on other distros it’s easy to overlook that.  The idea of
having clients warn about old daemons was a good one, but the
implementation didn’t work in your situation.

In your case, your daemon supported nothing but gzip (and bzip2 I think)
for substitutes.  However, gzip was officially dropped a few months ago,
meaning that newer substitutes are not available as gzip from
ci.guix.gnu.org:

  https://guix.gnu.org/en/blog/2022/sunsetting-gzip-substitutes-availability/

Thus your daemon was unable to fetch substitutes for things that were
built after that time.


BTW, the gzip change was announced publicly through several channels,
but your experience demonstrates that this is not enough.

> 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"
>
> Agree ?

Yes.

Thanks again for your time!

Ludo’




  parent reply	other threads:[~2022-10-06 17:37 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
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 [this message]
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=87czb5j65q.fsf@inria.fr \
    --to=ludovic.courtes@inria.fr \
    --cc=58149@debbugs.gnu.org \
    --cc=matthieu.haefele@cnrs.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).