From: Ricardo Wurmus <rekado@elephly.net>
To: 58149@debbugs.gnu.org
Subject: bug#58149: Unable to pull when using a pre-lzip version of guix-daemon
Date: Mon, 03 Oct 2022 22:47:52 +0200 [thread overview]
Message-ID: <8735c4pr20.fsf@elephly.net> (raw)
In-Reply-To: <b879f48c-fb1d-e341-6cc5-af486739e24f@cnrs.fr>
I’d just like to note what I do when I’m finding myself in a situation
where I’m tempted to run “guix pull” from a very old version of Guix:
1. visit https://ci.guix.gnu.org and select the “guix” jobset.
2. select a recent successful evaluation, e.g. https://ci.guix.gnu.org/eval/686692
3. select a build for your architecture, e.g. https://ci.guix.gnu.org/build/1565155/details
4. copy the derivation, e.g. /gnu/store/z0zhkvvmnjaji1i6lan0gxdqxhkr59as-guix-17134b9ec.drv
5. run “guix build /gnu/store/z0zhkvvmnjaji1i6lan0gxdqxhkr59as-guix-17134b9ec.drv”; this very noisily substitutes
the derivation and eventually prints “/gnu/store/pl3vs9a35mb0zmmpqimsxvl8ddl1bn41-guix-17134b9ec”
You now have an inconveniently named, but very recent Guix!
If your guix-daemon is too old you can replace it with
/gnu/store/pl3vs9a35mb0zmmpqimsxvl8ddl1bn41-guix-17134b9ec/bin/guix-daemon;
then you run /gnu/store/pl3vs9a35mb0zmmpqimsxvl8ddl1bn41-guix-17134b9ec/bin/guix pull, which upgrades
your Guix at ~/.config/guix/current.
Hope this helps!
--
Ricardo
prev parent reply other threads:[~2022-10-03 21: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
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 ` 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=8735c4pr20.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=58149@debbugs.gnu.org \
/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).