Bug#953952: kmod: libkmod2-udeb contains binary instead of libraries
Package: kmod
Version: 26+20191223-1
Severity: serious
Tags: d-i
Justification: Policy 8.6.4
The libkmod2 shlibs file contains the following entry:
| libkmod 2 libkmod2 (>= 26+20191223)
| udeb: libkmod 2 libkmod2-udeb (>= 26+20191223)
It means that libkmod.so.2 is supposed to be provided by libkmod2-udeb.
In practice it only contains the kmod binaries:
| $ dpkg -c libkmod2-udeb_27-2_amd64.udeb
| drwxr-xr-x root/root 0 2020-03-13 22:53 ./
| drwxr-xr-x root/root 0 2020-03-13 22:53 ./bin/
| -rwxr-xr-x root/root 121656 2020-03-13 22:53 ./bin/kmod
| drwxr-xr-x root/root 0 2020-03-13 22:53 ./etc/
| drwxr-xr-x root/root 0 2020-03-13 22:53 ./etc/modprobe.d/
| -rw-r--r-- root/root 246 2020-03-13 22:53 ./etc/modprobe.d/aliases.conf
| drwxr-xr-x root/root 0 2020-03-13 22:53 ./sbin/
| lrwxrwxrwx root/root 0 2020-03-13 22:53 ./bin/lsmod -> kmod
| lrwxrwxrwx root/root 0 2020-03-13 22:53 ./sbin/depmod -> /bin/kmod
| lrwxrwxrwx root/root 0 2020-03-13 22:53 ./sbin/insmod -> /bin/kmod
| lrwxrwxrwx root/root 0 2020-03-13 22:53 ./sbin/lsmod -> /bin/kmod
| lrwxrwxrwx root/root 0 2020-03-13 22:53 ./sbin/modinfo -> /bin/kmod
| lrwxrwxrwx root/root 0 2020-03-13 22:53 ./sbin/modprobe -> /bin/kmod
| lrwxrwxrwx root/root 0 2020-03-13 22:53 ./sbin/rmmod -> /bin/kmod
udev-udeb depends on libkmod2-udeb as /lib/systemd/systemd-udevd
requires libkmod.so.2.
The binaries should probably be moved to a different package like
kmod-udeb, as they conflict with busybox-udeb. Right now the kmod ones
are used, but it depends on the unpack order.
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 5.4.0-3-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Reply to: