Am 12.07.23 um 18:11 schrieb Josh Triplett:
My understanding was that that error happens *unconditionally* whether
there's a RAID device on the system or not, and that that bug is fixed
by depending on libblockdev-mdraid3 (which seems fine). But if I'm
understanding the upstream issue correctly, libblockdev-mdraid3 doesn't
actually need the mdadm binary *unless* the user's system actually has a
RAID device on it, in which case they would more likely want to have
mdadm installed. So, I *think* removing the Depends on mdadm would mean
that the only users getting an error message are those who have a RAID
device and *don't* have mdadm installed, which seems like exactly the
set of users who *should* get an error message.

I was pondering the question myself and came to a similiar conclusion.
A user with RAID devices most likely has mdadm installed anyway, so demoting it to Suggests seems ok, as we wouldn't generate error messages for users without RAID devices.


Michael

Attachment: OpenPGP_signature
Description: OpenPGP digital signature

Reply via email to