unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: 54483@debbugs.gnu.org, Mathieu Othacehe <othacehe@gnu.org>
Subject: bug#54483: ‘guix system image’ chokes on host's /var
Date: Thu, 07 Apr 2022 18:45:30 +0200	[thread overview]
Message-ID: <87h774etat.fsf@gnu.org> (raw)
In-Reply-To: <7f383e57e329486509d4059b31695cfd@tobias.gr> (Tobias Geerinckx-Rice's message of "Sun, 20 Mar 2022 20:26:51 +0100")

Hi!

Tobias Geerinckx-Rice <me@tobias.gr> skribis:

> I can't build the older installer image I want, ostensibly because my
> installed system is too new (anno-post-apteryx-versioning; no time to 
> further investigate I'm afraid).
>
> I expect a self-contained system not to care and certainly not to crash.
>
> ~/guix ⌥  v1.3.0-15828-gd5b4ca4445 λ ./pre-inst-env guix system image
> -t iso9660 gnu/system/install.scm
> guix system: warning: unrecognized boot parameters at
> '/var/guix/profiles/system-8-link/parameters'
> Backtrace:
> In ice-9/boot-9.scm:
>     152:2 19 (with-fluid* _ _ _)
> In unknown file:
>           18 (_ #<procedure 72f633d9b280 at ice-9/eval.scm:330:13 ()>

The ugly backtrace is gone with
47960b55268220ca1cb7d2fed41c53873181d816.

However, fundamentally, ‘guix system image’ shouldn’t be reading
/run/current-system/parameters because it has not use for it.

Mathieu, do you happen to have an idea where to remove that
‘read-boot-parameters-file’ call?  :-)

Thanks,
Ludo’.




  parent reply	other threads:[~2022-04-07 16:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-20 19:26 bug#54483: ‘guix system image’ chokes on host's /var Tobias Geerinckx-Rice via Bug reports for GNU Guix
2022-03-20 19:57 ` Maxime Devos
2022-03-20 20:01   ` Maxime Devos
2022-04-07 16:45 ` Ludovic Courtès [this message]
2022-08-12 14:33   ` Mathieu Othacehe

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=87h774etat.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=54483@debbugs.gnu.org \
    --cc=me@tobias.gr \
    --cc=othacehe@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. 
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).