* 0013-postinst-Fix-newest-kernel-detection.patch: dkms_common.postinst: We
were passing a list of kernels to get_newest_kernel(), when it expected a
single kernel as its first argument - the currently running kernel. This
in turn meant that the sometimes (if the first thing in the list was
itself the newest kernel), the wrong kernel was passed into
_get_newest_kernel_debian(). As a result this falsely reported that there
was no 'newest' kernel available and then didn't build modules for it.
Drop the parameter to get_newest_kernel(), and instead rely on
CURRENT_KERNEL being set to $(uname -r). (LP: #1681566)
This bug was fixed in the package dkms - 2.3-3ubuntu1
---------------
dkms (2.3-3ubuntu1) zesty; urgency=medium
* 0013-postinst- Fix-newest- kernel- detection. patch: dkms_common. postinst: We kernel( ), when it expected a newest_ kernel_ debian( ). As a result this falsely reported that there kernel( ), and instead rely on
were passing a list of kernels to get_newest_
single kernel as its first argument - the currently running kernel. This
in turn meant that the sometimes (if the first thing in the list was
itself the newest kernel), the wrong kernel was passed into
_get_
was no 'newest' kernel available and then didn't build modules for it.
Drop the parameter to get_newest_
CURRENT_KERNEL being set to $(uname -r). (LP: #1681566)
-- Iain Lane <email address hidden> Thu, 13 Apr 2017 15:50:18 +0100