Package: rsyslog Version: 8.2110.0-4 Severity: critical On systems still running sysvinit, the removal of /etc/init.d/rsyslog during upgrade of rsyslog causes complete data loss of critical system information that was intended to be logged after the next reboot.
I understand that many maintainers do not want to continue to maintain init scripts, but this case is different, as on sysvinit systems with rsyslog installed, this is _the_ system logging mechanism. At the very least, during postinst check if the system is running sysvinit and do something to prevent removal of the file, even if it stays around as a non-package-owned sysadmin file. ...Marvin -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (990, 'testing'), (500, 'stable-updates'), (500, 'stable-security'), (500, 'oldstable-updates'), (500, 'stable'), (500, 'oldstable'), (200, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.15.0-2-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) LSM: AppArmor: enabled Versions of packages rsyslog depends on: ii init-system-helpers 1.61 ii libc6 2.33-1 ii libestr0 0.1.10-2.1+b1 ii libfastjson4 0.99.9-1 ii liblognorm5 2.0.5-1.1 hi libsystemd0 238-5 ii libuuid1 2.37.2-4 ii zlib1g 1:1.2.11.dfsg-2 Versions of packages rsyslog recommends: ii logrotate 3.18.1-2 Versions of packages rsyslog suggests: pn rsyslog-doc <none> pn rsyslog-gssapi <none> pn rsyslog-mongodb <none> pn rsyslog-mysql | rsyslog-pgsql <none> pn rsyslog-openssl | rsyslog-gnutls <none> pn rsyslog-relp <none> -- no debconf information
