Hi, Thanks for forwarding this, Mark.
Daniel, I'm not particularly charmed by the retitling to show note about missing boot integration for non-systemd I have a few runit-init based systems with mdadm that run testing, which, thankfully, still has 4.2-5. The version in sid is old enough to migrate to testing but is still waiting on autopkgtest results before it migrates. Other than that there is nothing that prevents 4.2+20230508-2 from migrating and hit unsuspecting mdadm users *without* any message at all. These users will not be able to reboot their system after upgrading. Just image the pain of having this happen to a system in a remote location. Please consider bumping this bug to a Severity that keeps it from migrating to testing/trixie until this is resolved. # I'll be putting mdadm on hold on my systems for the time being. Thanks in advance, -- Olaf Meeuwissen
