From: Arnout Vandecappelle via buildroot <buildroot@buildroot.org>
To: Julien Olivain <ju.o@free.fr>
Cc: Arnout Vandecappelle <arnout@rnout.be>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/4] support/testing: ddrescue: use dmsetup from lvm2
Date: Wed, 7 Jan 2026 18:49:37 +0100 [thread overview]
Message-ID: <20260107174937.225414-1-arnout@rnout.be> (raw)
In-Reply-To: <20251219210957.556930-1-ju.o@free.fr>
In reply of:
> The ddresue runtime test is using the `dmsetup` command provided by the
> dmraid package. This package is outdated and will be removed. This
> command is also provided by the lvm2 package, which is still maintained.
>
> This commit replaces the dmraid package by lvm2 in the test config.
>
> Signed-off-by: Julien Olivain <ju.o@free.fr>
Applied to 2025.02.x and 2025.11.x. Thanks
> ---
> support/testing/tests/package/test_ddrescue.py | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/support/testing/tests/package/test_ddrescue.py b/support/testing/tests/package/test_ddrescue.py
> index 989abc8f01..042431eb7b 100644
> --- a/support/testing/tests/package/test_ddrescue.py
> +++ b/support/testing/tests/package/test_ddrescue.py
> @@ -9,7 +9,7 @@ class TestDdrescue(infra.basetest.BRTest):
> # - A kernel config fragment enables loop blk dev and device
> # mapper dm-dust, which are used to simulate a failing storage
> # block device.
> - # - dmraid user space package is needed to configure dm-dust
> + # - lvm2 user space package is needed to configure dm-dust with dmsetup
> config = \
> """
> BR2_aarch64=y
> @@ -23,7 +23,7 @@ class TestDdrescue(infra.basetest.BRTest):
> BR2_LINUX_KERNEL_CONFIG_FRAGMENT_FILES="{}"
> BR2_LINUX_KERNEL_NEEDS_HOST_OPENSSL=y
> BR2_PACKAGE_DDRESCUE=y
> - BR2_PACKAGE_DMRAID=y
> + BR2_PACKAGE_LVM2=y
> BR2_TARGET_ROOTFS_CPIO=y
> BR2_TARGET_ROOTFS_CPIO_GZIP=y
> # BR2_TARGET_ROOTFS_TAR is not set
> --
> 2.52.0
>
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2026-01-07 17:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-19 21:09 [Buildroot] [PATCH 1/4] support/testing: ddrescue: use dmsetup from lvm2 Julien Olivain via buildroot
2025-12-19 21:09 ` [Buildroot] [PATCH 2/4] support/testing: ddrescue: bump test kernel to 6.18.2 Julien Olivain via buildroot
2025-12-19 21:09 ` [Buildroot] [PATCH 3/4] support/testing: ddrescue: use f-string for test config Julien Olivain via buildroot
2026-01-07 17:49 ` Arnout Vandecappelle via buildroot
2025-12-19 21:09 ` [Buildroot] [PATCH 4/4] package/ddrescue: bump version to 1.29.1 Julien Olivain via buildroot
2025-12-27 23:40 ` [Buildroot] [PATCH 1/4] support/testing: ddrescue: use dmsetup from lvm2 Thomas Petazzoni via buildroot
2026-01-07 17:49 ` Arnout Vandecappelle via buildroot [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260107174937.225414-1-arnout@rnout.be \
--to=buildroot@buildroot.org \
--cc=arnout@rnout.be \
--cc=ju.o@free.fr \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox