[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Install `guix pull'ed Guix to target partition on system install

From: zimoun
Subject: Re: Install `guix pull'ed Guix to target partition on system install
Date: Tue, 22 Dec 2020 01:29:22 +0100

Hi Pierre,

Re-reading all the thread.

On Sun, 20 Dec 2020 at 10:12, Pierre Neidhardt <> 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:


If you really did:

   guix pull
   guix system init …
   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.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]