Your message dated Wed, 21 Aug 2019 10:35:46 +0000
with message-id <e1i0nxy-000evv...@fasolo.debian.org>
and subject line Bug#934709: fixed in v4l2loopback 0.12.2-1
has caused the Debian Bug report #934709,
regarding v4l2loopback: autopkgtest fails when there is a new version of
linux-latest
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 ow...@bugs.debian.org
immediately.)
--
934709: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934709
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: v4l2loopback
Version: 0.12.1-1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: issue
Control: affects -1 src:linux-latest
Dear maintainers,
With a recent upload of linux-latest the autopkgtest of v4l2loopback
fails in testing when that autopkgtest is run with the binary packages
of linux-latest from unstable. It passes when run with only packages
from testing. In tabular form:
pass fail
linux-latest from testing 106
v4l2loopback from testing 0.12.1-1
versioned deps [0] from testing from unstable
all others from testing from testing
Currently this regression is blocking the migration of linux-latest to
testing [1], but I'll tell the migration software to ignore this
failure, as it seems to me that your package is broken when the latest
linux kernel isn't equal to the kernel running your test. I copied some
of the output at the bottom of this report. For your first test, if this
really can't be fixed and this installation is supposed to fail, I
suggest you mark the first test with the skip-not-installable
restriction. Maybe the second test should be marked as skippable as well
(I don't know, but you'll need to make it exit with code 77 in the
skippable situation).
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[0] You can see what packages were added from the second line of the log
file quoted below. The migration software adds source package from
unstable to the list if they are needed to install packages from
linux-latest/106. I.e. due to versioned dependencies or breaks/conflicts.
[1] https://qa.debian.org/excuses.php?package=linux-latest
https://ci.debian.net/data/autopkgtest/testing/amd64/v/v4l2loopback/2720576/log.gz
Setting up v4l2loopback-dkms (0.12.1-1) ...
Loading new v4l2loopback-0.12.1 DKMS files...
It is likely that 4.9.0-8-amd64 belongs to a chroot's host
Building for 5.2.0-2-amd64
Building initial module for 5.2.0-2-amd64
Error! Bad return status for module build on kernel: 5.2.0-2-amd64 (x86_64)
Consult /var/lib/dkms/v4l2loopback/0.12.1/build/make.log for more
information.
dpkg: error processing package v4l2loopback-dkms (--configure):
installed v4l2loopback-dkms package post-installation script subprocess
returned error exit status 10
Setting up linux-headers-5.2.0-2-amd64 (5.2.7-1) ...
/etc/kernel/header_postinst.d/dkms:
Error! Bad return status for module build on kernel: 5.2.0-2-amd64 (x86_64)
Consult /var/lib/dkms/v4l2loopback/0.12.1/build/make.log for more
information.
dpkg: dependency problems prevent configuration of autopkgtest-satdep:
autopkgtest-satdep depends on v4l2loopback-dkms; however:
Package v4l2loopback-dkms is not configured yet.
dpkg: error processing package autopkgtest-satdep (--configure):
dependency problems - leaving unconfigured
Setting up linux-headers-amd64 (5.2+106) ...
Processing triggers for systemd (241-7) ...
Processing triggers for libc-bin (2.28-10) ...
Errors were encountered while processing:
v4l2loopback-dkms
autopkgtest-satdep
E: Sub-process /usr/bin/dpkg returned an error code (1)
========================================
and:
========================================
# Build modules
/usr/bin/make -C /usr/src/modules/v4l2loopback v4l2loopback \
KERNEL_DIR=/usr/src/linux-headers-5.2.0-2-amd64
KERNEL_VERSION=5.2.0-2-amd64
KERNELCONF=/usr/src/linux-headers-5.2.0-2-amd64/.config
make[2]: Entering directory '/usr/src/modules/v4l2loopback'
Building v4l2-loopback driver...
/usr/bin/make -C /usr/src/linux-headers-5.2.0-2-amd64
M=/usr/src/modules/v4l2loopback modules
make[3]: Entering directory '/usr/src/linux-headers-5.2.0-2-amd64'
CC [M] /usr/src/modules/v4l2loopback/v4l2loopback.o
/usr/src/modules/v4l2loopback/v4l2loopback.c: In function ‘vidioc_qbuf’:
/usr/src/modules/v4l2loopback/v4l2loopback.c:1509:4: error: implicit
declaration of function ‘v4l2_get_timestamp’; did you mean
‘v4l2_get_subdevdata’? [-Werror=implicit-function-declaration]
v4l2_get_timestamp(&b->buffer.timestamp);
^~~~~~~~~~~~~~~~~~
v4l2_get_subdevdata
cc1: some warnings being treated as errors
make[6]: ***
[/usr/src/linux-headers-5.2.0-2-common/scripts/Makefile.build:290:
/usr/src/modules/v4l2loopback/v4l2loopback.o] Error 1
make[5]: *** [/usr/src/linux-headers-5.2.0-2-common/Makefile:1610:
_module_/usr/src/modules/v4l2loopback] Error 2
make[4]: *** [Makefile:179: sub-make] Error 2
make[3]: *** [Makefile:8: all] Error 2
make[3]: Leaving directory '/usr/src/linux-headers-5.2.0-2-amd64'
make[2]: *** [Makefile:43: v4l2loopback.ko] Error 2
make[2]: Leaving directory '/usr/src/modules/v4l2loopback'
make[1]: *** [debian/rules:17: binary-modules] Error 2
make[1]: Leaving directory '/usr/src/modules/v4l2loopback'
make: *** [/usr/share/modass/include/common-rules.make:56: kdist_build]
Error 2
tput: No value for $TERM and no -T specified
BUILD FAILED!
tput: No value for $TERM and no -T specified
See
/var/cache/modass/v4l2loopback-source.buildlog.5.2.0-2-amd64.1565687553
for details.
Build failed. Press Return to continue...
signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: v4l2loopback
Source-Version: 0.12.2-1
We believe that the bug you reported is fixed in the latest version of
v4l2loopback, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 934...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
IOhannes m zmölnig (Debian/GNU) <umlae...@debian.org> (supplier of updated
v4l2loopback package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Wed, 21 Aug 2019 11:59:27 +0200
Source: v4l2loopback
Architecture: source
Version: 0.12.2-1
Distribution: unstable
Urgency: medium
Maintainer: IOhannes m zmölnig (Debian/GNU) <umlae...@debian.org>
Changed-By: IOhannes m zmölnig (Debian/GNU) <umlae...@debian.org>
Closes: 934709
Changes:
v4l2loopback (0.12.2-1) unstable; urgency=medium
.
* New upstream version 0.12.2
.
* Drop versioned B-Ds where version is satisfied in oldoldstable
* Switched build-system from CDBS to DH
* Install TODO
* Use symlinks to get additional documentation for all binary packages
* Update autopkgtests
* Explicit Depends on autopkgtests
* Drop obsolete "needs-recommmends" restriction
* Add "isolation-machine" restriction
(Closes: #934709)
* Use a script for module-assistant autopkgtest
* Bump dh-compat to 12
* Use debhelper-compat instead of d/compat
* Use dh_prep rather than "dh_clean -k"
* Bump standards version to 4.4.0
Checksums-Sha1:
605d3607a84589775942af2d760ce6d053290423 2419 v4l2loopback_0.12.2-1.dsc
0b0f898192cb6c889bb4439a324de6782662ba82 49147 v4l2loopback_0.12.2.orig.tar.gz
1833725d3b4a5bb9cf80573eaaf24a87880f9c73 8480
v4l2loopback_0.12.2-1.debian.tar.xz
Checksums-Sha256:
33b07671070c9a2f6cf652f239e24a2451183a69be0a118163eba6645cb075d6 2419
v4l2loopback_0.12.2-1.dsc
6d2c27a69d982bf39d7330b92f084fd0388beef486879320ccf263e4716cd549 49147
v4l2loopback_0.12.2.orig.tar.gz
b16a446748670ab0ac03d97a5a52222b2a2a8634d076306caf67152df72668a7 8480
v4l2loopback_0.12.2-1.debian.tar.xz
Files:
f4f78407598f3c6a2c428cdc39252625 2419 kernel optional v4l2loopback_0.12.2-1.dsc
bc634d94d2413c76ace9d9eaee5eb731 49147 kernel optional
v4l2loopback_0.12.2.orig.tar.gz
e27342c7a60402e5632955fdcbeaab3f 8480 kernel optional
v4l2loopback_0.12.2-1.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQJKBAEBCAA0FiEEdAXnRVdICXNIABVttlAZxH96NvgFAl1dGGIWHGZvcnVtQHVt
bGFldXRlLm11ci5hdAAKCRC2UBnEf3o2+Fz6D/92yHMFet4IaZixnR7kYjfLJqXw
Vcng0DW2rjoS/La+EKyGyOs5zYGYSXxR1j4tLvnPFDMaeuLfukXWv3Bm8XJoAOBU
ntXYgjy5sHX6sHednswEgH6aQ1x1ybbioarZMoSfrj7N0sa0UkwXRoXMlW/f9mP8
66gM5BUVEHg+QiDeQ2yHdkCGnbs4TBakJP0ML2LPeTvMA606f6k9+pXA7su8kMcw
BS/CYyz1lUutVeg2nMQIwqhJQ/IIYE9/tqvdscrD0Grc3GPfbSawdsCK8KZkMNwd
f6Rke+yLYg8lKZZb5YbjWOtj4FUjXLFz8qiBxxRhtRysVouPc8MxK9A5wU0GBdu9
pLJ4dbnlrR47C3z/Ityyp4YsZWQl1Su6K4ozkeWJvVeaHUoZjoNWIEecx3V4eWpe
ALAPAF7s6SaIkrEk+a5BD6evdGbLHpuiEt2nhaAK9ruAYg+NMe7aWn2RpTLFceK/
VM/4vHpCwbu3qB3c5R6K72BMe3/YAqYN027dMEPMsAQ0SZACakBxT4UieRtjEEX2
CK8DED0z3u5XQcy5QqgfIweO3F9TUGTyxX4TG0Os+bleSezUUiWkjHVjfBiys4eM
j1iPamRI3ZWjJfKIewgfHoLJ4pjDrNKOFN23PZBqDLAYiHsctijeZ/EzMdC1OGe7
xgnGg1/8sTU9tpTJog==
=JM8W
-----END PGP SIGNATURE-----
--- End Message ---
