unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Csepp <raingloom@riseup.net>
To: Csepp <raingloom@riseup.net>
Cc: 64196@debbugs.gnu.org, Josselin Poiret <dev@jpoiret.xyz>
Subject: bug#64196: Can't boot due to discrepancy between reconfigure and init
Date: Thu, 27 Jul 2023 00:42:45 +0200	[thread overview]
Message-ID: <87o7jy9tra.fsf@riseup.net> (raw)
In-Reply-To: <874jmwzqiy.fsf@riseup.net>


Csepp <raingloom@riseup.net> writes:

> Josselin Poiret <dev@jpoiret.xyz> writes:
>
>> [[PGP Signed Part:Undecided]]
>> Hi,
>>
>> Csepp <raingloom@riseup.net> writes:
>>>> I don't think there is, the biggest difference is that `guix system
>>>> init` will copy stuff into the target store and initialize the basic
>>>> directories for Guix, whereas reconfigure will just build everything in
>>>> the current store.
>>>>
>>>> Best,
>>>
>>> I mean, that's the theory, but either Guix or GRUB seems to get the
>>> incorrect UUID from *somewhere*.
>>
>> You can manually check that the generated grub.cfg file contains the
>> expected UUID after the reconfigure, it should be in
>> /boot/grub/grub.cfg.
>>
>> Best,
>
> I did, I think I already wrote that it wasn't coming from there, but
> I'll check again when I next try it.

This is still happening.  Couldn't figure out a decent way to transfer
my system with btrfs send.
I checked the generated bootloader installer script that gets run, it
seems to refer to the correct device, but somehow the UUID of the booted
partition still gets accessed.
I guess I'll have to strace it.




      reply	other threads:[~2023-07-26 23:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-20 18:38 bug#64196: Can't boot due to discrepancy between reconfigure and init Csepp
2023-06-21  7:45 ` Josselin Poiret via Bug reports for GNU Guix
2023-06-21 22:08   ` Csepp
2023-06-22  7:35     ` Josselin Poiret via Bug reports for GNU Guix
2023-06-24 18:01       ` Csepp
2023-07-26 22:42         ` Csepp [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=87o7jy9tra.fsf@riseup.net \
    --to=raingloom@riseup.net \
    --cc=64196@debbugs.gnu.org \
    --cc=dev@jpoiret.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.
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).