This bug was fixed in the package dkms - 3.0.11-1ubuntu7

---------------
dkms (3.0.11-1ubuntu7) mantic; urgency=medium

  * Reset test messages correctly.

dkms (3.0.11-1ubuntu6) mantic; urgency=medium

  * Fix hardcoded arch in test result expectations.

dkms (3.0.11-1ubuntu5) mantic; urgency=medium

  * Attempt #5 to fix autopkgtest on all arches.

dkms (3.0.11-1ubuntu4) mantic; urgency=medium

  * Testsuite forces a fake mok key, on arches that do not have
    update-secureboot-policy. Thus it should be possible to run the tests
    on all arches without specifying no-signing-tool flag. Try this now,
    again.

dkms (3.0.11-1ubuntu3) mantic; urgency=medium

  * Support running tests on systems with module signing, but without
    update-secureboot-policy.
  * Limit dkms-test-dkms to prevent badpkg on i386 for dkms-autopkgtest

dkms (3.0.11-1ubuntu2) mantic; urgency=medium

  * Fix autopkgtest for ubuntu delta.

dkms (3.0.11-1ubuntu1) mantic; urgency=medium

  * Deliberate Ubuntu delta:
    - Even if there is no delta with Debian, do not force-sync this
    package. This package will be updated by the kernel team as part of
    landing new kernels. Neither upstream, nor Debian, use dkms to the
    same extend as Ubuntu Kernel Team build processes do, plus Ubuntu has
    more dkms packages than Debian. Testing in Debian is insufficient for
    successful upload to Ubuntu. Over the previous two cycles, there were
    multiple regressions introduced in upstream and Debian revisions that
    have significantly impacted Ubuntu development. Introducing more
    strict upload process for the DKMS package should hopefully mitigate
    this. Previous request from the Kernel to do this, was ignored close
    to Lunar release, which caused Lunar to be shipped with a regressed
    dkms.

  *  Fixup autopkgtest:
    - Support systems with secure boot off
    - Support systems without update-secureboot-policy

dkms (3.0.11-1) experimental; urgency=medium

  * New upstream release.
    - Adds BUILD_EXCLUSIVE_{CONFIG,_KERNEL_{MIN,MAX}}.  (Closes: #911665)
    - Fixes BUILD_EXCLUSIVE matches propagating as error.  (Closes: #1031561)
  * Drop patches that were applied upstream.
  * Avoid unnecessary rpm comands on Debian based systems.  (Closes: #741399)

dkms (3.0.10-9) experimental; urgency=medium

  * Add dkms-test-dkms package with trivial kernel module for dkms tests.
  * New autopkgtest: Install some-dkms after linux-headers.
  * New autopkgtest: Install linux-headers after some-dkms.
  * New autopkgtest: Install some-dkms after linux-image w/o linux-headers.
  * New autopkgtest: Install linux-image after some-dkms w/o linux-headers.
  * Upload to experimental.

dkms (3.0.10-8ubuntu1) mantic; urgency=medium

  * Fix a regression that prevents a kernel installation if a BUILD_EXCLUSIVE
    skips a DKMS build. LP: #2018226

dkms (3.0.10-8) unstable; urgency=medium

  * Disable tests broken by fix-builtin-archive-dkms-coinstallation.patch.
    (Closes: #1033396)
  * Run autopkgtest for all architectures using the headers from the
    linux-headers-generic (virtual) meta-package.
  * Generate dh_dkms.1 at build time.
  * Clean up /boot/*.old-dkms on upgrades from bullseye.  (Closes: #717584)
  * Clean up obsolete /etc/dkms/sign_helper.sh on upgrades. (Closes: #1019563)
  * dkms-autopkgtest: Try to 'dkms install' its BUILD_DEPENDS before testing a
    module. (Single level only, without recursion.)  (Closes: #1034303)
  * Fix fallback value for BUILD_MODULE_NAME[0].  (Closes: #651973)
  * dkms.8: Clarify 'dkms add' arguments.  (Closes: #704917)
  * Print a warning if /proc is not mounted.  (Closes: #810665, #968074)
  * dkms_autoinstaller: Skip autoinstall if headers are missing (like
    dkms_common.postinst).  (Closes: #1030595)
  * Use return code 77 if skipping due to BUILD_EXCLUSIVE_*.
  * Sort kernels by version.

 -- Dimitri John Ledkov <dimitri.led...@canonical.com>  Wed, 24 May 2023
10:11:33 +0100

** Changed in: dkms (Ubuntu Mantic)
       Status: Confirmed => 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/2018226

Title:
  autoinstall fails despite BUILD_EXCLUSIVE

Status in dkms package in Ubuntu:
  Fix Released
Status in dkms source package in Lunar:
  Fix Committed
Status in dkms source package in Mantic:
  Fix Released

Bug description:
  [Impact]

  Kernel upgrades fail if DKMS packages are currently installed that
  include BUILD_EXCLUSIVE directives which skip the DKMS build. In this
  case, the dkms tool incorrectly returns a non-zero exit status.

  $ sudo /etc/kernel/postinst.d/dkms 6.2.0-20-generic
   * dkms: running auto installation service for kernel 6.2.0-20-generic        
                                                                 Deprecated 
feature: REMAKE_INITRD 
(/var/lib/dkms/oem-ethernet-r8169-aspm-support-bionic/4/source/dkms.conf)
  Deprecated feature: REMAKE_INITRD (/etc/dkms/framework.conf)
  Sign command: /usr/bin/kmodsign
  Signing key: /var/lib/shim-signed/mok/MOK.priv
  Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der
  Deprecated feature: REMAKE_INITRD 
(/var/lib/dkms/oem-ethernet-r8169-aspm-support-bionic/4/source/dkms.conf)
  Error! The 
/var/lib/dkms/oem-ethernet-r8169-aspm-support-bionic/4/6.2.0-20-generic/x86_64/dkms.conf
 for module oem-ethernet-r8169-aspm-support-bionic includes a BUILD_EXCLUSIVE 
directive which does not match this kernel/arch/config.
  This indicates that it should not be built.
  Error! One or more modules failed to install during autoinstall.
  Refer to previous errors for more information.     [fail]

  [Test Plan]

  Install such a DKMS (like [1]), and run:
  $ sudo /etc/kernel/postinst.d/dkms $(uname -r)

  This command should return with exit status '0'.

  [1]  http://oem.archive.canonical.com/updates/pool/public/o/oem-
  ethernet-r8169-aspm-support-bionic-dkms/

  [Where problems could occur]

  This fix changes how DKMS status/results are handled during
  autoinstall. So problems would only show up if DKMS modules are
  installed and are being processed (for example during a kernel upgrade
  or installation). Or if the dkms tool is invoked manually.

  [Other info]

  The bug was introduced in upstream dkms version 3.0.9 and fixed in
  3.0.11.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/2018226/+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

Reply via email to