Package: runit Version: 2.1.2-50 Severity: important Partially related to #1022837. run_sysv_scripts is invoked in stage 1 to run boot scripts (initscripts); however it skip the sysv script when a runit service with the same name exists. This is wrong for early boot tasks and it can break the boot sequence. For example one can have a /etc/sv/udev longrun that will replace the sysv instance in stage 2, but still need to run /etc/init.d/udev during eraly boot.
-- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') merged-usr: no Architecture: amd64 (x86_64) Kernel: Linux 5.7.0-1-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash Init: runit (via /run/runit.stopit) LSM: AppArmor: enabled Versions of packages runit depends on: ii libc6 2.36-3 ii runit-helper 2.15.0 ii sysuser-helper 1.3.7+really1.4.1 Versions of packages runit recommends: ii runit-init 2.1.2-50 Versions of packages runit suggests: ii socklog 2.1.0+repack-4+b1 pn zsh <none> -- Configuration Files: /etc/default/runit changed [not included] /etc/runit/ctrlaltdel changed [not included] /etc/runit/runsvdir/single/sulogin/run [Errno 2] No such file or directory: '/etc/runit/runsvdir/single/sulogin/run' -- no debconf information
