This bug was fixed in the package west-chamber -
20100405+svn20111107.r124-14.3build1~25.04.1
---------------
west-chamber (20100405+svn20111107.r124-14.3build1~25.04.1) plucky;
urgency=medium
* No-change rebuild for dh_dkms #MODULE_VERSION# fix. (LP: #2102149)
-- Massimiliano Pellizzer <massimiliano.pelliz...@canonical.com> Wed,
14 May 2025 11:26:39 +0200
** Changed in: west-chamber (Ubuntu Plucky)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/2102149
Title:
Multiple DKMS packages fail to install with DKMS unable to find
#MODULE_VERSION#
Status in dkms package in Ubuntu:
Fix Released
Status in lime-forensics package in Ubuntu:
Fix Released
Status in nat-rtsp package in Ubuntu:
Fix Released
Status in osmocom-dahdi-linux package in Ubuntu:
Fix Released
Status in west-chamber package in Ubuntu:
Fix Released
Status in dkms source package in Plucky:
Fix Released
Status in lime-forensics source package in Plucky:
Fix Released
Status in nat-rtsp source package in Plucky:
Fix Released
Status in osmocom-dahdi-linux source package in Plucky:
Fix Released
Status in west-chamber source package in Plucky:
Fix Released
Bug description:
[ Impact ]
Multiple DKMS packages are experiencing the following issue when
compiling:
<dkms-package-name> version <dkms-package-version> fails to install with
output:
Error! The directory
/var/lib/dkms/<dkms-package-name>/#MODULE_VERSION#/source does not appear to
have module source located within it.
This is caused by the different DKMS packages being built incorrectly
due to an outdated dh_dkms helper script where #MODULE_VERSION# in
DKMS config does not get replaced unless the dh_dkms -V option is
specified. Upstream, this is resolved by a change in dh_dkms to always
replace #MODULE_VERSION# in DKMS config:
https://salsa.debian.org/debian/dkms/-/commit/a7e442244cba31800c1fef2f4890179d65531958.
[ Fix ]
Rebuild the affected DKMS packages since the fix landed in the
archive.
[ Test Case ]
In order to the the fix it is possible to simple verify that the dkms
package get installed correctly.
$ sudo apt install <dkms-package-name>
[ Possible Regressions ]
Since the fix just requires a no-changes build, there is no possible
regression.
If the fix does not work the DKMS will not compile, therefore it will not
change the current situation.
---
nat-rtsp-dkms version 0.7+5.3-0.4 fails to install with output:
Error! The directory /var/lib/dkms/nat-rtsp/#MODULE_VERSION#/source does not
appear to have module source located within it.
This is caused by the nat-rtsp-dkms package being built incorrectly
due to an outdated dh_dkms helper script where #MODULE_VERSION# in
DKMS config does not get replaced unless the dh_dkms -V option is
specified. Upstream, this is resolved by a change in dh_dkms to always
replace #MODULE_VERSION# in DKMS config:
https://salsa.debian.org/debian/dkms/-/commit/a7e442244cba31800c1fef2f4890179d65531958.
# sudo apt install nat-rtsp-dkms
Installing:
nat-rtsp-dkms
Summary:
Upgrading: 0, Installing: 1, Removing: 0, Not Upgrading: 27
Download size: 0 B / 15.2 kB
Space needed: 62.5 kB / 5501 MB available
Selecting previously unselected package nat-rtsp-dkms.
(Reading database ... 126191 files and directories currently installed.)
Preparing to unpack .../nat-rtsp-dkms_0.7+5.3-0.4_all.deb ...
Unpacking nat-rtsp-dkms (0.7+5.3-0.4) ...
Setting up nat-rtsp-dkms (0.7+5.3-0.4) ...
Loading new nat-rtsp-#MODULE_VERSION# DKMS files...
Building for 6.14.0-7-generic
Building initial module for 6.14.0-7-generic
Error! The directory /var/lib/dkms/nat-rtsp/#MODULE_VERSION#/source does not
appear to have module source located within it.
Build halted.
dpkg: error processing package nat-rtsp-dkms (--configure):
installed nat-rtsp-dkms package post-installation script subprocess returned
error exit status 8
Errors were encountered while processing:
nat-rtsp-dkms
needrestart is being skipped since dpkg has failed
Error: Sub-process /usr/bin/dpkg returned an error code (1)
This same exact bug affects also lime-forensics-dkms version 1.9.1-7.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/2102149/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
