Your message dated Fri, 31 Mar 2023 15:59:56 +0200
with message-id <[email protected]>
and subject line Re: Impossible to install a kernel module for a specific
kernel version in a clean manner
has caused the Debian Bug report #859888,
regarding Impossible to install a kernel module for a specific kernel version
in a clean manner
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.)
--
859888: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859888
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: dkms
Version: 2.2.0.3-2
Architecture: all
Hello,
the script /usr/lib/dkms/dkms_autoinstaller includes the following command in
line 42:
dkms autoinstall --kernelver $kernel .
This does not allow to install modules for a specific/exclusive kernel version
and ignores the list of kernel versions set in /usr/lib/dkms/common.postinst .
Having a look at the man page or the online help of dkms, you see that dkms
command autoinstall does not accept any further option(s). Is this behaviour
intended or a mistake?
Best greetings
Sebastian Kraus
--- End Message ---
--- Begin Message ---
On Sat, 8 Apr 2017 17:00:44 +0000 "Kraus, Sebastian"
<[email protected]> wrote:
the script /usr/lib/dkms/dkms_autoinstaller includes the following command in
line 42:
dkms autoinstall --kernelver $kernel .
This does not allow to install modules for a specific/exclusive kernel version
and ignores the list of kernel versions set in /usr/lib/dkms/common.postinst .
Having a look at the man page or the online help of dkms, you see that dkms
command autoinstall does not accept any further option(s). Is this behaviour
intended or a mistake?
dkms_autoinstaller and common.postinst are orthogonal to each other:
dkms_autoinstaller runs from the postinst of linux-{image,headers}-* and
attempts to build *all* dkms modules for a *single* kernel (that is
currently being configured).
common.postinst runs from the postinst of a module-dkms package and
attempts to build a *single* dkms module (that is currently being
configured) for *all* kernels that have headers available on the system.
Of course you can also manually do
dkms build module/version -k $kver
Andreas
--- End Message ---
