[Bug 2073010] Re: Module doesn't build for kernel at build time

[John Cabaj]

** Description changed:

  [Impact]
  
- * Kernel source directory was fixed to /lib/modules/($uname -r), which works for building when DKMS package is installed, but not when built within context of a kernel build
- * dh-dkms was added to initial upload during sponsorship, but is not available in Jammy or Focal. This prevents the package from building.
+ * For Focal and Jammy releases, the package never left the -proposed pocket due to dh-dkms being added to initial upload during sponsorship, which is not available in those respective releases.
+ * For Noble release, the package is only installable via DKMS, but cannot be built and signed alongside the kernel build during kernel SRU cycle (https://wiki.ubuntu.com/Kernel/StableReleaseCadence). This is because the kernel source directory was fixed to /lib/modules/($uname -r), which works for building when DKMS package is installed, but not when built within context of a Launchpad kernel build, where the build headers are self-contained during the build process.
  * Correcting src/md5.c also mistakenly set to public domain in copyright
  * Using debhelper-compat (= 12) for Focal
  
  [Fix]
  
  * Simple re-package, with updated .dkms file, dependencies, and
  copyright
  
  [Test Plan]
  
- * Compile and install dkms module
- * Microsoft tested
+ * Install requisite kernel (Focal, Jammy, or Noble) in some virtual environment (LXD or otherwise)
+ * Install DKMS module, which will rebuild against the kernel installed
+ * Ensure DKMS module builds and installs properly, and the module can be inserted via insmod
+ 
+ * Microsoft has additionally tested the module in-depth
  
  [Where problems could occur]
  
- * Low regression risk
+ * Regression risk is low as this module has been tested already, and these changes are limited to packaging.
+ * These updates allow the module to build for both Focal and Jammy, as those packages never left the -proposed pocket due to build dependency issues.
+ * In the case of Noble, the risk is that this could fail to build in some unforeseen circumstance where the kernel_source_dir variable is missing, though that would point to broader issues in DKMS.

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/2073010

Title:
  Module doesn't build for kernel at build time

Status in involflt package in Ubuntu:
  New
Status in involflt source package in Focal:
  Incomplete
Status in involflt source package in Jammy:
  Incomplete
Status in involflt source package in Noble:
  Incomplete

Bug description:
  [Impact]

  * For Focal and Jammy releases, the package never left the -proposed pocket due to dh-dkms being added to initial upload during sponsorship, which is not available in those respective releases.
  * For Noble release, the package is only installable via DKMS, but cannot be built and signed alongside the kernel build during kernel SRU cycle (https://wiki.ubuntu.com/Kernel/StableReleaseCadence). This is because the kernel source directory was fixed to /lib/modules/($uname -r), which works for building when DKMS package is installed, but not when built within context of a Launchpad kernel build, where the build headers are self-contained during the build process.
  * Correcting src/md5.c also mistakenly set to public domain in copyright
  * Using debhelper-compat (= 12) for Focal

  [Fix]

  * Simple re-package, with updated .dkms file, dependencies, and
  copyright

  [Test Plan]

  * Install requisite kernel (Focal, Jammy, or Noble) in some virtual environment (LXD or otherwise)
  * Install DKMS module, which will rebuild against the kernel installed
  * Ensure DKMS module builds and installs properly, and the module can be inserted via insmod

  * Microsoft has additionally tested the module in-depth

  [Where problems could occur]

  * Regression risk is low as this module has been tested already, and these changes are limited to packaging.
  * These updates allow the module to build for both Focal and Jammy, as those packages never left the -proposed pocket due to build dependency issues.
  * In the case of Noble, the risk is that this could fail to build in some unforeseen circumstance where the kernel_source_dir variable is missing, though that would point to broader issues in DKMS.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/involflt/+bug/2073010/+subscriptions