From: "Ludovic Courtès" <ludo@gnu.org>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: Simon Streit <simon@netpanic.org>, 48496@debbugs.gnu.org
Subject: bug#48496: Guix reconfigure fails to switch to new system
Date: Sat, 29 May 2021 23:01:41 +0200 [thread overview]
Message-ID: <87eedp5k5m.fsf@gnu.org> (raw)
In-Reply-To: <878s4bamf6.fsf@gnu.org> ("Ludovic Courtès"'s message of "Tue, 18 May 2021 21:09:49 +0200")
Hi Simon & Tobias,
Ludovic Courtès <ludo@gnu.org> skribis:
> Tobias Geerinckx-Rice <me@tobias.gr> skribis:
>
>> Simon Streit 写道:
>>> ice-9/boot-9.scm:1685:16: In procedure raise-exception:
>>> no code for module (system repl error-handling)
>>
>> Thank you for reporting this. With commit
>> 5fa46ca96da90ec19e32cc4d726f099d0979d60b on master, the system
>> tests that failed for me with this error no longer do.
>
> What system tests were failing?
>
> At first sight I don’t see how a67c00f4f7ee0a70fce14a7e1907cce332c85813
> led to this:
>
> activating system...
> Backtrace:
> In ice-9/boot-9.scm:
> 3422:24 19 (_)
> 222:29 18 (map1 (((gnu system accounts)) ((gnu build accounts)) …))
> 222:29 17 (map1 (((gnu build accounts)) ((gnu build #)) ((# …)) …))
> 222:17 16 (map1 (((gnu build linux-boot)) ((guix build utils)) # …))
> 3326:17 15 (resolve-interface (gnu build linux-boot) #:select _ # _ …)
> In ice-9/threads.scm:
> 390:8 14 (_ _)
> In ice-9/boot-9.scm:
> 3252:13 13 (_)
> In ice-9/threads.scm:
> 390:8 12 (_ _)
> In ice-9/boot-9.scm:
> 3536:20 11 (_)
> 2835:4 10 (save-module-excursion #<procedure 7f9a73ee5b70 at ice-…>)
> 3556:26 9 (_)
> In unknown file:
> 8 (primitive-load-path "gnu/build/linux-boot" #<procedure…>)
> In gnu/build/linux-boot.scm:
> 22:0 7 (_)
> In ice-9/boot-9.scm:
> 3409:4 6 (define-module* _ #:filename _ #:pure _ #:version _ # _ …)
> 3422:24 5 (_)
> 222:29 4 (map1 (((rnrs io ports)) ((system repl #)) ((srfi #)) …))
> 222:17 3 (map1 (((system repl error-handling)) ((srfi srfi-1)) …))
> 3329:6 2 (resolve-interface (system repl error-handling) #:select …)
> 1685:16 1 (raise-exception _ #:continuable? _)
> 1685:16 0 (raise-exception _ #:continuable? _)
>
> ice-9/boot-9.scm:1685:16: In procedure raise-exception:
> no code for module (system repl error-handling)
I’ve tried several system tests and manually running a system in a VM,
with a67c00f4f7ee0a70fce14a7e1907cce332c85813 reinstated, and cannot
reproduce the issue.
Do you know of a way to reproduce it?
The IRC log <https://logs.guix.gnu.org/guix/2021-05-18.log> suggests
that a couple of people experienced the issue on that day, but pastes
are no longer accessible.
TIA!
Ludo’.
next prev parent reply other threads:[~2021-05-29 21:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-18 11:18 bug#48496: Guix reconfigure fails to switch to new system Simon Streit
2021-05-18 14:49 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2021-05-18 18:19 ` Simon Streit
2021-05-18 19:09 ` Ludovic Courtès
2021-05-29 21:01 ` Ludovic Courtès [this message]
2021-05-31 19:36 ` Simon Streit
2021-06-01 17:05 ` Simon Streit
2021-06-03 20:47 ` Ludovic Courtès
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=87eedp5k5m.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=48496@debbugs.gnu.org \
--cc=me@tobias.gr \
--cc=simon@netpanic.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).