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 11:46:34 +0100 [thread overview]
Message-ID: <86r1ni86et.fsf@gmail.com> (raw)
In-Reply-To: <87h7oekwf0.fsf@ambrevar.xyz>
Hi Pierre,
On Tue, 22 Dec 2020 at 10:44, Pierre Neidhardt <mail@ambrevar.xyz> wrote:
>> 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's not a contradiction.
It is. If you do:
(live) guix pull
(live) guix system init
then it appears expected to install what the system describes *and* the
current guix used to install them. Therefore, after reboot, the first
“guix pull” will not fetch all the substitutes Guix requires, because
you already did.
Other said,
(live) guix pull
(live) guix describe
(live) guix system init
(live) reboot
(real) login as root
(real) guix describe
The 2 ’describe’ should be the same commit and apparently they are not.
>> In conclusion, the problem here does not seem cloning the repo, but
>> fetching all the substitutes twice.
>
> There is a misunderstanding: the Guix live system is not the same OS
> (nor the same store) as the installed system.
I do not see where there is a misunderstanding.
If you really did:
(live) guix pull
(live) guix system init …
(live) reboot
(real) login as regular user
(real) guix pull
Then the issue is not the cloning part (’git clone
https://git.savannah.gnu.org/git/guix.git’) displaying «Updating channel
'guix' from Git repository at
'https://git.savannah.gnu.org/git/guix.git'...» but the fact that you
are downloading twice the substitutes used by “guix pull”.
Please re-read these messages:
<https://yhetil.org/guix/86y2hq90sm.fsf@gmail.com>
<https://yhetil.org/guix/86tuse8yzh.fsf@gmail.com>
Cheers,
simon
next prev parent reply other threads:[~2020-12-22 10:54 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
2020-12-22 9:44 ` Pierre Neidhardt
2020-12-22 10:46 ` zimoun [this message]
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=86r1ni86et.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).