unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Carlo Zancanaro <carlo@zancanaro.id.au>
Cc: help-guix@gnu.org
Subject: Re: Install `guix pull'ed Guix to target partition on system install
Date: Tue, 22 Dec 2020 14:06:14 +0100	[thread overview]
Message-ID: <86eeji7zy1.fsf@gmail.com> (raw)
In-Reply-To: <87r1nioy7o.fsf@zancanaro.id.au>

Hi Carlo,

On Tue, 22 Dec 2020 at 22:51, Carlo Zancanaro <carlo@zancanaro.id.au> wrote:

> On Tue, Dec 22 2020, zimoun wrote:
>> 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.
>
> Part of the issue here is that "guix system init" installs into 
> the system the version of Guix that the "guix" package refers to, 
> which is always older than the version that you are using to do 
> the installation. The "guix" package points to a specific commit 
> (4f621a2b003e85d480999e4d0630e9dc3de85bc3 in my current guix 
> version) which must have come prior to the commit of the guix that 
> is running (which for me is 
> 5795f566fae85023c6be86fe62388c29e6ac5c51).

We are describing the same issue but worded differently; or I am sorry
but I cannot express differently.  Well, IIUC, you are explaining why it
is not as I expect.  So bug?

(And if it is not, I am going to take a break because then I do not
understand what you and I are both saying.)

>>   (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.
>
> This expectation is wrong. The two "describe"s should return 
> different commits, and the second one should be earlier than the 
> first.

Your description is the current situation.  And that’s why the first
“guix pull” after the first log is so long.  It should not work like
that.  Because I did my homework, let reuse your own words ;-) «I don't
think "expected" is the right way to put this. I think "explainable" is
more accurate.»

Even if the second “describe” return an earlier commit than the first,
all the store items should be already in the final store because they are
in the live store.

Otherwise, the same substitutes are pulled twice.


> Unfortunately, I am not aware of a solution to the issue Pierre 
> has raised.

One way is to transfer the store items from the live store to the disk
store somehow via “guix archive --export -r” then “guix archive
--import”.  IMHO.


All the best,
simon


      reply	other threads:[~2020-12-22 13:06 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
2020-12-22 11:51       ` Carlo Zancanaro
2020-12-22 13:06         ` zimoun [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=86eeji7zy1.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=carlo@zancanaro.id.au \
    --cc=help-guix@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.
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).