Package: systemd
Version: 252.4-1
Severity: grave
So do kexec-tools if a user has chosen to use it for
reboots during package configuration.
Either of the following can cause fs corruption (to the point one has to use
`fsck -y`):
a) the procedure described in https://wiki.archlinux.org/title/Kexec#Manually
1. `kexec -l /boot/vmlinuz-6.0.0-6-amd64 --initrd=/boot/initrd-6.0.0-6-amd64
--reuse-cmdline`
2. `systemctl kexec`
b) Just choosing to use kexec for reboots when installing it, and then
rebooting.
-- Package-specific info:
-- System Information:
Debian Release: bookworm/sid
Architecture: amd64 (x86_64)
Kernel: Linux 6.0.0-6-amd64 (SMP w/4 CPU threads; PREEMPT)
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages systemd depends on:
ii libacl1 2.3.1-2
ii libaudit1 1:3.0.7-1.1+b2
ii libblkid1 2.38.1-4
ii libc6 2.36-8
ii libcap2 1:2.66-3
ii libcryptsetup12 2:2.6.0-2
ii libfdisk1 2.38.1-4
ii libgcrypt20 1.10.1-3
ii libkmod2 30+20221128-1
ii liblz4-1 1.9.4-1
ii liblzma5 5.4.0-0.1
ii libmount1 2.38.1-4
ii libp11-kit0 0.24.1-2
ii libseccomp2 2.5.4-1+b2
ii libselinux1 3.4-1+b4
ii libssl3 3.0.7-1
ii libsystemd-shared 252.4-1
ii libsystemd0 252.4-1
ii libzstd1 1.5.2+dfsg2-3
ii mount 2.38.1-4
Versions of packages systemd suggests:
ii libfido2-1 1.12.0-2
ii libqrencode4 4.1.1-1
ii libtss2-esys-3.0.2-0 3.2.1-2
ii libtss2-mu0 3.2.1-2
ii libtss2-rc0 3.2.1-2
ii policykit-1 122-1
ii polkitd 122-1
pn systemd-boot <none>
pn systemd-container <none>
pn systemd-homed <none>
ii systemd-resolved 252.4-1
pn systemd-userdbd <none>
Versions of packages systemd is related to:
ii dbus-user-session 1.14.4-1
ii dracut <none>
pn initramfs-tools 0.142
pn libnss-systemd <none>
ii libpam-systemd 252.4-1
ii udev 252.4-1
-- no debconf information
