Your message dated Fri, 24 May 2024 11:49:04 +0200
with message-id <[email protected]>
and subject line Re: v4l2loopback-utils: Unable to use dynamic device 
management due to old version
has caused the Debian Bug report #985507,
regarding v4l2loopback-utils: Unable to use dynamic device management due to 
old version
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
985507: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985507
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: v4l2loopback-utils
Version: 0.12.5-1
Severity: normal
X-Debbugs-Cc: [email protected]

Dear Maintainer,

The current version of v4l2loopback-ctl in Unstable (currently 0.6) is a bit
behind compared to upstream, and, as a result, I am unable to use dynamic
device management to create new loopback devices on-the-fly since the option
does not exist, see:

https://github.com/umlaeute/v4l2loopback#dynamic-device-management

As a workaround, I built v4l2loopback-ctl directly from upstream, but it would
be great if the new version was included in Debian.

Thanks,
Goran


-- System Information:

Versions of packages v4l2loopback-utils depends on:
ii  gstreamer1.0-tools  1.18.3-1
ii  sudo                1.9.5p2-2
ii  v4l-utils           1.20.0-2

Versions of packages v4l2loopback-utils recommends:
ii  v4l2loopback-dkms  0.12.5-1

v4l2loopback-utils suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message --- v4l2loopback_0.13 (with dynamic device management) was released earlier this year.
as a consequence it was uploaded to Debian on 20 Mar 2024 10:08:55 +0100.

thanks.

--- End Message ---

Reply via email to