Package: dkms Version: 3.1.0-1 Severity: important -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
I was wondering why the autopkgtests were failing, till I realized the problem may actually be in dkms itself. It turns out the error messages come from debian/scripts/dkms-autopkgtest. https://github.com/dell/dkms/actions show massive amounts of failed CI tests which were fixed about a month ago. So it could very well be that the recently released 3.1.2 version fixes various reported (autopkg)test failures. Set the severity higher then normal because of those failures. - -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (101, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.12+unreleased-amd64 (SMP w/16 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages dkms depends on: ii build-essential 12.12 ii dpkg-dev 1.22.11 ii kmod 33+20240816-2 ii lsb-release 12.1-1 ii make 4.3-4.1 ii patch 2.7.6-7 Versions of packages dkms recommends: ii clang-16 [c-compiler] 1:16.0.6-27+b1 ii clang-19 [c-compiler] 1:19.1.4-1 ii fakeroot 1.36-1 ii gcc [c-compiler] 4:14.2.0-1 ii gcc-10 [c-compiler] 10.5.0-4 ii gcc-13 [c-compiler] 13.3.0-8 ii gcc-14 [c-compiler] 14.2.0-8 ii sudo 1.9.16p1-1 Versions of packages dkms suggests: ii e2fsprogs 1.47.1-1+b1 ii menu 2.1.50 - -- no debconf information -----BEGIN PGP SIGNATURE----- iHUEARYIAB0WIQT1sUPBYsyGmi4usy/XblvOeH7bbgUCZ0jnXgAKCRDXblvOeH7b buehAQDbF0/5e8Dw37x1JlpOvROaNV65z5jCGk4zAfqZbnQq7wD+PMoNd4VL4qJ3 wgAnRqyp9n5zyvir+t74ZrbE8NUFJws= =kkue -----END PGP SIGNATURE-----
