sysdig-dkms fails to build on kinetic with linux 5.19

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Libera.chat.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1982490/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

debdiff in attach allows to correctly build sysdig-dkms in jammy with linux 5.19.

here the 'buildN' can be dropped since you're adding actual changes

uploaded

Hello Andrea, or anyone else affected,

Accepted sysdig into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/sysdig/0.27.1-0.3ubuntu0.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Performed only build tests due to lack of hardware for better testing.

Build test with generic 5.15 and hwe-5.19 kernels:

=========================================================
Setting up sysdig-dkms (0.27.1-0.3ubuntu0.1) ...
Loading new sysdig-0.27.1 DKMS files...
Building for 5.15.0-60-generic 5.19.0-32-generic
Building initial module for 5.15.0-60-generic
EFI variables are not supported on this system
/sys/firmware/efi/efivars not found, aborting.
Done.

sysdig-probe.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/5.15.0-60-generic/updates/dkms/

depmod...
Building initial module for 5.19.0-32-generic
EFI variables are not supported on this system
/sys/firmware/efi/efivars not found, aborting.
Done.

sysdig-probe.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/5.19.0-32-generic/updates/dkms/
=========================================================

This bug was fixed in the package sysdig - 0.27.1-0.3ubuntu0.1

---------------
sysdig (0.27.1-0.3ubuntu0.1) jammy; urgency=medium

  * Support linux 5.19 (LP: #1982490):
    - d/p/fix-kmod-build-on-5.18.patch

 -- Andrea Righi <email address hidden> Tue, 17 Jan 2023 15:14:05 +0000

The verification of the Stable Release Update for sysdig has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.