Your message dated Mon, 27 Nov 2023 19:17:23 +0000 with message-id <[email protected]> and subject line Re: Bug#1056363: initscripts: Backport 3.08 to stable (bookworm) for udev init script has caused the Debian Bug report #1056363, regarding initscripts: Backport 3.08 to stable (bookworm) for udev init script to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 1056363: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056363 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: initscripts Version: 3.08-3 Severity: important Dear Maintainer, initscripts 3.08 needs to be backported to bookworm, as the systemd version that removed the udev init script and forced initscripts to take over it was already backported. Anyone (such as me) running sysvinit and upgraded the systemd related packages to bookworm-backports will end up with no running udev, breaking things like persistent device naming and automatic loading of device driver modules. * What led up to the situation? systemd package removed the init script for udev, and in #1042082 it was suggestedd that initscripts take it over. Both changes were merged and pushed to unstable. New version of systemd was backported to bookworm. initscripts was not backported. * What exactly did you do (or not do) that was effective (or ineffective)? I upgraded systemd related packages to 254 from bookworm-backports. I run sysvinit instead of systemd. * What was the outcome of this action? udev daemon no longer runs after reboot. Consistent device naming and device driver module autoloading no longer works. * What outcome did you expect instead? udev daemon should still be run. I grabbed the udev init script from https://salsa.debian.org/systemd-team/systemd/-/blob/6e720b91dd837b71dd81c1d959b21f1b0a48ae29/debian/udev.init and installed it manually for now, but this kind of surprise shouldn't happen. -- System Information: Debian Release: 12.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'oldstable-updates'), (500, 'oldstable-security'), (500, 'stable'), (500, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 6.5.0-0.deb12.1-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=zh_TW.UTF-8, LC_CTYPE=zh_TW.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: sysvinit (via /sbin/init) Versions of packages initscripts depends on: ii sysv-rc 3.06-4 ii sysvinit-utils 3.06-4 Versions of packages initscripts recommends: ii e2fsprogs 1.47.0-2 ii psmisc 23.6-1 initscripts suggests no packages. -- no debconf information
--- End Message ---
--- Begin Message ---Version: 3.08-3~bpo12+1 On Wed, Nov 22, 2023 at 11:07:00AM +0000, Mark Hindley wrote: > I have uploaded src:sysvinit 3.08-3~bpo12+1. It is waiting in backports-new[1] Now accepted into bookworm-backports, closing. Mark
--- End Message ---
