Package: virtualbox-dkms Version: 7.1.12-dfsg-2+b1 Severity: normal It looks like the fix for #1105784 is not applied correctly on upgrades from broken versions, leaving the users with an empty /etc/modprobe.d/virtualbox- dkms.conf directory that still generates the warning, in the best case, or with /etc/modprobe.d/virtualbox-dkms.conf/virtualbox-dkms.modprobe.conf retained but marked as an obsolete conffile.
The best case probably works like this: 1. preinst renames the config to .dpkg-remove 2. dpkg tries to remove the directory and fails with "Directory not empty" 3. postinst removes .dpkg-remove, the directory stays -- System Information: Debian Release: forky/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.16-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages virtualbox-dkms depends on: ii dkms 3.2.0-1 Versions of packages virtualbox-dkms recommends: ii virtualbox 7.1.12-dfsg-2+b1 virtualbox-dkms suggests no packages. -- debconf-show failed
