From: "Ludovic Courtès" <ludo@gnu.org>
To: Christoph Weiss <weiss@wsoptics.de>
Cc: 54770@debbugs.gnu.org
Subject: bug#54770: Non-root LUKS devices unusable after Shepherd upgrade
Date: Mon, 11 Apr 2022 14:39:06 +0200 [thread overview]
Message-ID: <874k2zkd5h.fsf@gnu.org> (raw)
In-Reply-To: <7bc7e9a1-6bd4-2350-4389-d08ec072b3e3@wsoptics.de> (Christoph Weiss's message of "Sat, 9 Apr 2022 16:51:35 +0200")
Hi Christoph,
Christoph Weiss <weiss@wsoptics.de> skribis:
> I ran into the same issue (no prompt but instead about 32 times the
> message "Nothing to read on input.")
>
> I bisected this issue myself (starting before the fix was pushed) and
> arrived at 400c9ed3d779308e56038305d40cd93acb496180 as the culprit.
>
> However, even with the current master
> (aa5716703fd4603dd89ce9b55f555b7aa85f4c9b), the issue has not been
> fixed for me.
It’s definitely fixed for me and the new ‘separate-home-os’ system test
agrees¹.
Did you reconfigure after pulling? What does ‘guix system describe’
report?
Thanks,
Ludo’.
¹ https://ci.guix.gnu.org/search?query=spec%3Atests+separate-home
next prev parent reply other threads:[~2022-04-11 12:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-07 16:33 bug#54770: Non-root LUKS devices unusable after Shepherd upgrade Ludovic Courtès
2022-04-08 9:32 ` Ludovic Courtès
2022-04-08 13:34 ` Ludovic Courtès
2022-04-08 16:18 ` Ludovic Courtès
2022-04-09 14:51 ` Christoph Weiss
2022-04-11 12:39 ` Ludovic Courtès [this message]
2022-04-11 17:07 ` bug#54770: (no subject) Christoph Weiss
2022-04-12 8:41 ` bug#54770: Non-root LUKS devices unusable after Shepherd upgrade Ludovic Courtès
2022-04-12 17:00 ` Christoph Weiss
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=874k2zkd5h.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=54770@debbugs.gnu.org \
--cc=weiss@wsoptics.de \
/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).