v4l2loopback 10.0-1ubuntu1 ADT test failure with linux 5.0.0-14-generic

.debdiff attached to this comment.

To fix this, I've backported this patch: https://github.com/umlaeute/v4l2loopback/commit/afe0b233070d7ca5d6df83c5f2723d276dcd287d.patch

No context adjustments were required.

[ Testing ]

I tested this install process for both 4.15.0-49-generic and 5.0.0-14-generic to test for regressions since the changes introduced by this patch are not conditionally compiled.

- Create a Bionic 18.04 VM
- Install the Bionic Linux HWE Edge kernel from -proposed or install the built .debs located here: https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+packages?field.name_filter=linux-hwe-edge&field.status_filter=published&field.series_filter=bionic
- Try installing v4l2loopback-dkms with apt (or you can pull the sources with "pull-lp-source v4l2loopback bionic" and build with "debuild -b -uc -us"
- Confirm that installation fails for the 5.0 kernel (it will succeed for 4.15)
- Pull the sources with "pull-lp-source v4l2loopback bionic"
- Apply the debdiff "debdiff-apply < path-to-diff-in-this-comment.debdiff"
- Build the package "debuild -b -uc -us"
- Install the .deb produced from the previous step "sudo dpkg --install path-to-deb.deb"
- Verify the installation completed successfully. You can also verify the output of "sudo dkms status" is correct.

The attachment "v4l2loopback_0.10.0-1ubuntu1.1.debdiff" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.]

Could you also please file a bug in Debian, so we can pull the change down from there?

Hello Connor, or anyone else affected,

Accepted v4l2loopback into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/v4l2loopback/0.10.0-1ubuntu1.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 and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. 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.

The package in -proposed (0.10.0-1ubuntu1.1) installs correctly without any compilation errors. Updating the verification tag on this bug.

I forgot to verify this for 4.15 in addition to 5.0. The package in -proposed (0.10.0-1ubuntu1.1) installs correctly without any compilation errors for 4.15 and 5.0.

I've attached the log of the installation while running a 4.15 kernel. The 5.0 kernel is also installed on this VM so it similarly compiles for that one as well (as shown in the previous comment).

This bug was fixed in the package v4l2loopback - 0.10.0-1ubuntu1.1

---------------
v4l2loopback (0.10.0-1ubuntu1.1) bionic; urgency=medium

  * Fix build for kernel 5.0 (LP: #1828615)
    - debian/patches/0002-Replace-do_gettimeofday-with-v4l2_get_timestamp.patch

 -- Connor Kuehl <email address hidden> Fri, 10 May 2019 11:32:46 -0700

The verification of the Stable Release Update for v4l2loopback has completed successfully and the package has now been 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.