Hey Daniel. On Fri, 2023-05-19 at 13:54 +0200, Daniel Baumann wrote: > The problem you're describing sounds like #1031695 from > dh_installsystemd. However, when looking at the mdadm 4.2-5 .deb > file, > it's not affected by that. > > Installing it on a clean system (with and without merged-usr) works > both > as expected (no dangling symlinks; all systemd files in /lib/systemd, > not /usr/lib/systemd). > > Also I can't think of anything that would triggered that within the > mdadm.
Well I have seen it at least on 3 independent systems of mine... every time with mdadm-shutdown.service (via .../sysinit.target.wants/mdadm- shutdown.service) and also on one with fail2ban.service (via .../multi- user.target.wants) > In any way, nothing I can do something > about in mdadm, hence closing this bug. I'm quite confident that I didn't do anything manually to create those... and since you think that mdadm wouldn't have been affected by #1031695... shouldn't we perhaps rather reassign (and reopen) it to debhelper so that the debhelper experts can have a look whether any other possible issue remains? Thanks, Chris.
