[Bug 2078947] Re: Import new upstream 0.13.2 release

[Launchpad Bug Tracker]

This bug was fixed in the package v4l2loopback - 0.13.2-1ubuntu1

---------------
v4l2loopback (0.13.2-1ubuntu1) oracular; urgency=medium

  * Merge from Debian (LP: #2078947), remaining changes:
    - v4l2loopback: backward compatibility for v4l2-relayd

 -- You-Sheng Yang <vicamo.yano at canonical.com>  Mon, 02 Sep 2024
18:26:32 +0800

** Changed in: v4l2loopback (Ubuntu Oracular)
       Status: In Progress => Fix Released

-- 
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/2078947

Title:
  Import new upstream 0.13.2 release

Status in v4l2-relayd package in Ubuntu:
  Triaged
Status in v4l2loopback package in Ubuntu:
  Fix Released
Status in v4l2-relayd source package in Noble:
  Triaged
Status in v4l2loopback source package in Noble:
  Won't Fix
Status in v4l2-relayd source package in Oracular:
  Triaged
Status in v4l2loopback source package in Oracular:
  Fix Released

Bug description:
  The v4l2loopback has released v0.13.0 on March 20, 2024, and the
  latest v0.13.2 in May. Debian has v0.13.2 as well.

  Starting from v4l2loopback v0.13.0, the client usage event has been
  upstreamed as part of the official v4l2loopback owning events, and a
  different event ID from the one has been used by v4l2-relayd is chosen
  to avoid interference of users for other purposes. This, however,
  introduced backward compatibility issue for v4l2-relayd, which should
  receive similar fix (also with compatibility to different v4l2loopback
  versions) as possible.

  While Ubuntu ships prebuilt v4l2loopback kernel module in linux-
  modules{,-extra} and generic kernel may become hwe kernel of a
  previous LTS release, it makes such version bumps tied to series as
  well.

  The plan is:
  1. to support both event IDs in v4l2loopback/oracular,
  2. while v4l2loopback/oracular is compiled into kernels linux/oracular and linux-oem-6.11/noble, v4l2-relayd/noble should be better adopt the same fix to make sure it will continue to be compatible with latter v4l2loopback from linux-modules{,-extra}.
  3. all the kernels in jammy remains unaffected, and so is v4l2-relayd.

  Upstream: https://github.com/umlaeute/v4l2loopback/releases/tag/v0.13.2
  Debian Trixie: https://packages.debian.org/trixie/v4l2loopback-dkms

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/v4l2-relayd/+bug/2078947/+subscriptions