From: zimoun <zimon.toutoune@gmail.com>
To: Pierre Neidhardt <mail@ambrevar.xyz>, help-guix@gnu.org
Subject: Re: Install `guix pull'ed Guix to target partition on system install
Date: Tue, 22 Dec 2020 01:29:22 +0100 [thread overview]
Message-ID: <86tuse8yzh.fsf@gmail.com> (raw)
In-Reply-To: <87ft403kol.fsf@ambrevar.xyz>
Hi Pierre,
Re-reading all the thread.
On Sun, 20 Dec 2020 at 10:12, Pierre Neidhardt <mail@ambrevar.xyz> wrote:
> I just installed Guix System on a new machine:
>
> - guix pull -C my-channels.scm
Did you really do this “guix pull”? Because it is…
> - guix system init ... /mnt
> - reboot
>
> Now on my fresh system, the only Guix available is the one from the USB
> stick, namely 1.2, and not the one from my channels.
…in contradiction with this. So bug?
It looks as you are doing:
guix system init … # use guix v1.2
so you download all the substitutes corresponding to this v1.2. Then
you reboot and log as regular user, run:
guix pull
This ’guix’ clones the repo and fetches all the substitutes at version
origin/version to be able to run the last ’guix’, i.e., create:
~/.config/guix/current
If you really did:
guix pull
guix system init …
reboot
login as regular user
guix pull
and it took twice half an hour (for each “guix pull”) in addition to all
required by your config, I miss something. Because, the second pull
should not be so long.
Well, one way to fix is, before the reboot, run “guix archive --export
-r $(readlink -f /path/to/default/guix/profile)” and then after the
login run “guix archive --import”. This should avoid to fetch twice the
same substitutes (used by Guix). I thought that something like that was
included by “guix system init”.
In conclusion, the problem here does not seem cloning the repo, but
fetching all the substitutes twice.
Cheers,
simon
next prev parent reply other threads:[~2020-12-22 0:39 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-20 9:12 Install `guix pull'ed Guix to target partition on system install Pierre Neidhardt
2020-12-21 11:57 ` zimoun
2020-12-21 12:26 ` Pierre Neidhardt
2020-12-21 13:07 ` zimoun
2020-12-21 13:33 ` Pierre Neidhardt
2020-12-21 13:56 ` zimoun
2020-12-21 14:47 ` Pierre Neidhardt
2020-12-21 16:26 ` zimoun
2020-12-21 16:49 ` Pierre Neidhardt
2020-12-21 17:06 ` zimoun
2020-12-21 17:12 ` Pierre Neidhardt
2020-12-21 17:53 ` zimoun
2020-12-21 19:39 ` Pierre Neidhardt
2020-12-21 23:50 ` zimoun
2020-12-22 12:28 ` Ricardo Wurmus
2020-12-22 13:16 ` zimoun
2020-12-22 0:29 ` zimoun [this message]
2020-12-22 9:44 ` Pierre Neidhardt
2020-12-22 10:46 ` zimoun
2020-12-22 11:51 ` Carlo Zancanaro
2020-12-22 13:06 ` zimoun
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=86tuse8yzh.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=help-guix@gnu.org \
--cc=mail@ambrevar.xyz \
/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.
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).