Package: mdadm
Version: 4.2-5
Severity: serious
Tags: d-i
Justification: breaks d-i
X-Debbugs-Cc: debian-b...@lists.debian.org, debian-cd@lists.debian.org
[ X-D-Cc: -boot@ and -cd@ for awareness. ]
Hi,
Spotted by Steve while testing tentative Trixie Alpha 1 images: mdadm is
broken, with a systemd-related problem.
This part of the .config script doesn't seem to work:
# if system has root on md
if findmnt / 2>/dev/null | grep -qs \/dev\/md && \
# and system is not a container
! grep -qs ':cpuset:/$' /proc/1/cgroup && \
# and system is not a chroot
[ "$(stat -c %d/%i /)" != "$(stat -Lc %d/%i /proc/1/root 2>/dev/null)" ] &&
\
# and systemd is not running
[ -z "$(pidof systemd)" ]
then
db_input high mdadm/init-system-not-systemd || true
db_go
fi
The chroot test seems inverted (compared to the intent/comment):
- On my laptop I'm getting this: 64770/2 == 64770/2
- In my sid devel schroot I'm getting: 64774/1196038 != 64770/2
I'm awaiting some feedback from the images team to see if my plan would
work for them, but my initial reaction would be to confirm the trivial
bugfix (if it's easy enough to test, within the installer's environment)
then upload + fast-track mdadm into testing, before respinning images.
Cheers,
--
Cyril Brulebois (k...@debian.org) <https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant
