Package: wtmpdb Version: 0.72.0-1 Severity: normal Upgrading wtmpdb from versions between 0.13.0-6 and 0.72.0-1 can leave useless runlevels configured that do not cause the edge-level trigger in the init script since version 0.71.0+git20250228.4e4b54e-2 to record boots.
Fresh installations since 0.71.0+git20250228.4e4b4e-2 are not affected but upgrades to later versions cannot detect that the wrong runlevels have already been set from an earlier version. This affects any current _or future_ users of sysvinit who tested affected versions of wtmpdb prior to the trixie release. The proportion of affected users who deliberately modified their configured runlevels is likely to be a minority of affected users and probably nil, therefore it would be appropriate forcibly to reset the runlevels for these users in a one of maintscripts operation. -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.12.19-amd64 (SMP w/24 CPU threads; PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: sysvinit (via /sbin/init) LSM: AppArmor: enabled Versions of packages wtmpdb depends on: ii init-system-helpers 1.68 ii libaudit1 1:4.0.2-2+b2 ii libc6 2.41-6 ii libsystemd0 257.4-9 ii libwtmpdb0 0.72.0-1 Versions of packages wtmpdb recommends: ii libpam-wtmpdb 0.72.0-1 wtmpdb suggests no packages. -- no debconf information
