Your message dated Mon, 17 Feb 2025 10:39:29 +0100
with message-id <[email protected]>
and subject line Re: dkms: crazy UI difference between success and error case
leading to admin not noticing the latter
has caused the Debian Bug report #1008505,
regarding dkms: crazy UI difference between success and error case leading to
admin not noticing the latter
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1008505: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008505
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: dkms
Version: 2.6.1-4
Severity: important
When DKMS is successful, we see output like this:
-----BEGIN cutting here may damage your screen surface-----
Preparing to unpack .../iproute2-dbgsym_5.10.0-4~jens+6_amd64.deb ...
Unpacking iproute2-dbgsym (5.10.0-4~jens+6) over (5.10.0-4~jens+5) ...
Preparing to unpack .../sch-jens-dkms_5.10.0-4~jens+6_all.deb ...
-------- Uninstall Beginning --------
Module: sch-jens
Version: 5.10.0
Kernel: 4.19.0-17-amd64 (x86_64)
-------------------------------------
Status: Before uninstall, this module version was ACTIVE on this kernel.
sch_jens.ko:
- Uninstallation
- Deleting from: /lib/modules/4.19.0-17-amd64/updates/dkms/
- Original module
- No original module was found for this module on this kernel.
- Use the dkms install command to reinstall any previous module version.
depmod.........
DKMS: uninstall completed.
-------- Uninstall Beginning --------
Module: sch-jens
Version: 5.10.0
Kernel: 4.19.0-18-amd64 (x86_64)
-------------------------------------
Status: Before uninstall, this module version was ACTIVE on this kernel.
sch_jens.ko:
- Uninstallation
- Deleting from: /lib/modules/4.19.0-18-amd64/updates/dkms/
- Original module
- No original module was found for this module on this kernel.
- Use the dkms install command to reinstall any previous module version.
depmod........
DKMS: uninstall completed.
-------- Uninstall Beginning --------
Module: sch-jens
Version: 5.10.0
Kernel: 5.10.0-0.bpo.8-amd64 (x86_64)
-------------------------------------
Status: Before uninstall, this module version was ACTIVE on this kernel.
sch_jens.ko:
- Uninstallation
- Deleting from: /lib/modules/5.10.0-0.bpo.8-amd64/updates/dkms/
- Original module
- No original module was found for this module on this kernel.
- Use the dkms install command to reinstall any previous module version.
depmod...
DKMS: uninstall completed.
------------------------------
Deleting module version: 5.10.0
completely from the DKMS tree.
------------------------------
Done.
Unpacking sch-jens-dkms (5.10.0-4~jens+6) over (5.10.0-4~jens+5) ...
Preparing to unpack .../iproute2_5.10.0-4~jens+6_amd64.deb ...
Unpacking iproute2 (5.10.0-4~jens+6) over (5.10.0-4~jens+5) ...
Preparing to unpack .../iproute2-doc_5.10.0-4~jens+6_all.deb ...
Unpacking iproute2-doc (5.10.0-4~jens+6) over (5.10.0-4~jens+5) ...
Setting up iproute2-doc (5.10.0-4~jens+6) ...
Setting up iproute2 (5.10.0-4~jens+6) ...
Setting up iproute2-dbgsym (5.10.0-4~jens+6) ...
Setting up sch-jens-dkms (5.10.0-4~jens+6) ...
Loading new sch-jens-5.10.0 DKMS files...
Building for 4.19.0-18-amd64
Building initial module for 4.19.0-18-amd64
Done.
sch_jens.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/4.19.0-18-amd64/updates/dkms/
sch_jhtb.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/4.19.0-18-amd64/updates/dkms/
depmod...
DKMS: install completed.
Processing triggers for man-db (2.8.5-2) ...
-----END cutting here may damage your screen surface-----
When not, this is shown:
-----BEGIN cutting here may damage your screen surface-----
[…]
Setting up vim-common (2:8.1.0875-5+deb10u2) ...
Setting up linux-source-5.10 (5.10.103-1~bpo10+1) ...
Setting up libpcap0.8:amd64 (1.8.1-6+deb10u1) ...
Setting up libjbig2dec0:amd64 (0.16-1+deb10u1) ...
Setting up libfaad2:amd64 (2.10.0-1~deb10u1) ...
Setting up libssl-dev:amd64 (1.1.1n-0+deb10u1) ...
Setting up icu-devtools (63.1-6+deb10u3) ...
Setting up linux-config-4.19:amd64 (4.19.235-1) ...
Setting up libisc-export1100:amd64 (1:9.11.5.P4+dfsg-5.1+deb10u7) ...
Setting up libcups2:amd64 (2.2.10-6+deb10u5) ...
Setting up libwavpack1:amd64 (5.1.0-6+deb10u1) ...
Setting up linux-kbuild-5.10 (5.10.103-1~bpo10+1) ...
Setting up libtiff5:amd64 (4.1.0+git191117-2~deb10u4) ...
Setting up xterm (344-1+deb10u2) ...
Setting up vim-runtime (2:8.1.0875-5+deb10u2) ...
Setting up libc-dev-bin (2.28-10+deb10u1) ...
Setting up openssl (1.1.1n-0+deb10u1) ...
Setting up libdns-export1104 (1:9.11.5.P4+dfsg-5.1+deb10u7) ...
Setting up libxml2:amd64 (2.9.4+dfsg1-7+deb10u3) ...
Setting up linux-headers-4.19.0-20-common (4.19.235-1) ...
Setting up linux-kbuild-4.19 (4.19.235-1) ...
Setting up libflac-dev:amd64 (1.3.2-3+deb10u1) ...
Setting up vim (2:8.1.0875-5+deb10u2) ...
Setting up libisc1100:amd64 (1:9.11.5.P4+dfsg-5.1+deb10u7) ...
Setting up linux-image-amd64 (4.19+105+deb10u15) ...
Setting up liblwres161:amd64 (1:9.11.5.P4+dfsg-5.1+deb10u7) ...
Setting up libisccc161:amd64 (1:9.11.5.P4+dfsg-5.1+deb10u7) ...
Setting up libc6-dev:amd64 (2.28-10+deb10u1) ...
Setting up libicu-dev:amd64 (63.1-6+deb10u3) ...
Setting up linux-headers-4.19.0-20-amd64 (4.19.235-1) ...
/etc/kernel/header_postinst.d/dkms:
Error! Bad return status for module build on kernel: 4.19.0-20-amd64 (x86_64)
Consult /var/lib/dkms/sch-jens/5.10.0/build/make.log for more information.
Setting up libdns1104:amd64 (1:9.11.5.P4+dfsg-5.1+deb10u7) ...
Setting up linux-headers-amd64 (4.19+105+deb10u15) ...
Setting up libexpat1-dev:amd64 (2.2.6-2+deb10u4) ...
Setting up libisccfg163:amd64 (1:9.11.5.P4+dfsg-5.1+deb10u7) ...
Setting up libbind9-161:amd64 (1:9.11.5.P4+dfsg-5.1+deb10u7) ...
Setting up libirs161:amd64 (1:9.11.5.P4+dfsg-5.1+deb10u7) ...
Setting up bind9-host (1:9.11.5.P4+dfsg-5.1+deb10u7) ...
Setting up dnsutils (1:9.11.5.P4+dfsg-5.1+deb10u7) ...
Processing triggers for install-info (6.5.0.dfsg.1-4+b1) ...
Processing triggers for mime-support (3.62) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
Processing triggers for libc-bin (2.28-10+deb10u1) ...
Processing triggers for man-db (2.8.5-2) ...
-----END cutting here may damage your screen surface-----
In the success case, there’s this HUGE *SHOUTING* thing with TONS
of EMPTY LINES, dashes to separate, and all.
In the error case… a message easily overlooked. No prompt either,
but Policy says not to, in most cases, so that’s okay, it’s not a
module whose absence will prevent rebooting.
I find this UI… rather contrary to good design.
-- System Information:
Debian Release: 10.12
APT prefers oldstable-updates
APT policy: (500, 'oldstable-updates'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-20-amd64 (SMP w/3 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/lksh
Init: sysvinit (via /sbin/init)
Versions of packages dkms depends on:
ii build-essential 12.6
ii coreutils 8.30-3
ii dpkg-dev 1.19.7
ii gcc 4:8.3.0-1
ii kmod 26-1
ii make 4.2.1-1.2
ii patch 2.7.6-3+deb10u1
Versions of packages dkms recommends:
ii fakeroot 1.23-1
ii linux-headers-amd64 4.19+105+deb10u15
ii lsb-release 10.2019051400
ii sudo 1.8.27-1+deb10u3
Versions of packages dkms suggests:
ii menu 2.1.47+b1
pn python3-apport <none>
-- Configuration Files:
/etc/dkms/framework.conf changed:
autoinstall_all_kernels=1
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 3.0.9-1
On Mon, 28 Mar 2022 02:34:54 +0200 Thorsten Glaser <[email protected]> wrote:
Package: dkms
Version: 2.6.1-4
...
Setting up linux-headers-4.19.0-20-amd64 (4.19.235-1) ...
/etc/kernel/header_postinst.d/dkms:
Error! Bad return status for module build on kernel: 4.19.0-20-amd64 (x86_64)
Consult /var/lib/dkms/sch-jens/5.10.0/build/make.log for more information.
Setting up libdns1104:amd64 (1:9.11.5.P4+dfsg-5.1+deb10u7) ...
...
In the success case, there’s this HUGE *SHOUTING* thing with TONS
of EMPTY LINES, dashes to separate, and all.
Since 3.1.x dkms is much less noisy in the successful case.
In the error case… a message easily overlooked. No prompt either,
but Policy says not to, in most cases, so that’s okay, it’s not a
module whose absence will prevent rebooting.
I find this UI… rather contrary to good design.
Since 3.0.9 dkms autoinstall returns a non-zero exit code if one of the
modules failed to build or install, this propagates to a postinst
failure of the corresponding linux-image-*/linux-headers-* package and
should no longer go unnoticed.
Andreas
--- End Message ---
