From: "Ludovic Courtès" <ludo@gnu.org>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: 39926@debbugs.gnu.org
Subject: bug#39926: Regression introduced by Shepherd 0.7.0 ('make check-system TESTS=btrfs-root-os' fails)
Date: Sat, 07 Mar 2020 22:36:50 +0100 [thread overview]
Message-ID: <878skbetjh.fsf@gnu.org> (raw)
In-Reply-To: <87d09ojt6z.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Sat, 07 Mar 2020 12:33:08 +0100")
Hi again!
Ludovic Courtès <ludo@gnu.org> skribis:
> The broken udev rule is ‘64-btrfs.rules’ in eudev:
>
> # reconsider pending devices in case when multidevice volume awaits
> ENV{ID_BTRFS_READY}=="1", RUN+="${exec_prefix}/bin/udevadm trigger -s block -p ID_BTRFS_READY=0"
>
> … where “${exec_prefix}” is expanded from “@bindir@”, a classical
> issue that we should report upstream. :-)
>
> In the meantime, the following patch should solve the problem. I’m
> running the test now, and if it passes and you’re fine with it, I’ll
> commit it.
I pushed the patch as 24a4a635fd76a91463c75cfe615929ec482cc2f6.
It doesn’t solve the “btrfs-root-os” bug though. :-/
I noticed that it’s the installation.drv that fails, not the basic.drv,
which is why we see “gnu” as the host name. The weird thing is that it
fails after ‘reboot’, so I’m not sure what that means. To be continued…
Thanks,
Ludo’.
next prev parent reply other threads:[~2020-03-07 21:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-05 14:23 bug#39926: Regression introduced by Shepherd 0.7.0 ('make check-system TESTS=btrfs-root-os' fails) Maxim Cournoyer
2020-03-05 17:22 ` Ludovic Courtès
2020-03-07 4:40 ` Maxim Cournoyer
2020-03-07 5:15 ` Maxim Cournoyer
2020-03-19 22:21 ` Ludovic Courtès
2020-03-20 14:23 ` Maxim Cournoyer
2020-03-21 13:44 ` Ludovic Courtès
2020-03-23 18:01 ` Maxim Cournoyer
2020-03-07 11:11 ` Ludovic Courtès
2020-03-07 11:33 ` Ludovic Courtès
2020-03-07 21:36 ` Ludovic Courtès [this message]
2020-03-17 3:07 ` Maxim Cournoyer
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=878skbetjh.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=39926@debbugs.gnu.org \
--cc=maxim.cournoyer@gmail.com \
/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).