Your message dated Wed, 30 Sep 2020 12:48:51 +0000
with message-id <e1knbxp-0008ep...@fasolo.debian.org>
and subject line Bug#971161: fixed in evemu 2.7.0-3
has caused the Debian Bug report #971161,
regarding evemu: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned
exit code 2
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.)
--
971161: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971161
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: evemu
Version: 2.7.0-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200926 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[4]: Entering directory '/<<PKGBUILDDIR>>/test'
> PASS: test-cxx-compile
> PASS: test-c-compile
> ../config-aux/test-driver: line 107: 31163 Aborted "$@" >
> $log_file 2>&1
> FAIL: test-evemu-create
> ========================================================
> Kernel device emulation 2.7.0: test/test-suite.log
> ========================================================
>
> # TOTAL: 3
> # PASS: 2
> # SKIP: 0
> # XFAIL: 0
> # FAIL: 1
> # XPASS: 0
> # ERROR: 0
>
> .. contents:: :depth: 2
>
> FAIL: test-evemu-create
> =======================
>
> test-evemu-create: test-evemu-create.c:184: check_evemu_read: Assertion
> `evemu_has_event(dev, i, j)' failed.
> FAIL test-evemu-create (exit status: 134)
>
> ============================================================================
> Testsuite summary for Kernel device emulation 2.7.0
> ============================================================================
> # TOTAL: 3
> # PASS: 2
> # SKIP: 0
> # XFAIL: 0
> # FAIL: 1
> # XPASS: 0
> # ERROR: 0
> ============================================================================
> See test/test-suite.log
> ============================================================================
> make[4]: *** [Makefile:760: test-suite.log] Error 1
> make[4]: Leaving directory '/<<PKGBUILDDIR>>/test'
> make[3]: *** [Makefile:868: check-TESTS] Error 2
> make[3]: Leaving directory '/<<PKGBUILDDIR>>/test'
> make[2]: *** [Makefile:955: check-am] Error 2
> make[2]: Leaving directory '/<<PKGBUILDDIR>>/test'
> make[1]: *** [Makefile:478: check-recursive] Error 1
> make[1]: Leaving directory '/<<PKGBUILDDIR>>'
> dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2
The full build log is available from:
http://qa-logs.debian.net/2020/09/26/evemu_2.7.0-2_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: evemu
Source-Version: 2.7.0-3
Done: Stephen Kitt <sk...@debian.org>
We believe that the bug you reported is fixed in the latest version of
evemu, 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 971...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Stephen Kitt <sk...@debian.org> (supplier of updated evemu 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: SHA512
Format: 1.8
Date: Wed, 30 Sep 2020 14:29:19 +0200
Source: evemu
Architecture: source
Version: 2.7.0-3
Distribution: unstable
Urgency: medium
Maintainer: Stephen Kitt <sk...@debian.org>
Changed-By: Stephen Kitt <sk...@debian.org>
Closes: 971161
Changes:
evemu (2.7.0-3) unstable; urgency=medium
.
* Apply upstream fix for the tests. Closes: #971161.
* Switch to debhelper compatibility level 13.
Checksums-Sha1:
6e12e31fc6e0c5c2cf572945c9e6948507f150dd 2325 evemu_2.7.0-3.dsc
aac41b07bf279a5df84eee1814d5f71e5a2afadb 12104 evemu_2.7.0-3.debian.tar.xz
0094a5c3b5f836f470678ddfd19de5f27584e5bc 7319 evemu_2.7.0-3_source.buildinfo
Checksums-Sha256:
cd30983372d09abd9d19b5368bb0fc4ed7307732340837c0a1951edf37a525bb 2325
evemu_2.7.0-3.dsc
964b36893a662e98d5c7b72bdeaeb890a97937c4540c2e0f859e30287bb6d18b 12104
evemu_2.7.0-3.debian.tar.xz
fcbb018bdf5834b921c9401135c17e95c9ede9ae20f2a86a1b22710a54ec7546 7319
evemu_2.7.0-3_source.buildinfo
Files:
0d20eccd110ced0445d38c7af945d59d 2325 libs optional evemu_2.7.0-3.dsc
4b783e4b42e0e4a8d3b8cb730a41e112 12104 libs optional
evemu_2.7.0-3.debian.tar.xz
31791f07a8bbedcf7aea9f2264464c52 7319 libs optional
evemu_2.7.0-3_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEnPVX/hPLkMoq7x0ggNMC9Yhtg5wFAl90ejUACgkQgNMC9Yht
g5yQoA//a7VsZlqEhipKZAlBORct+0FdzQJ1Ev+kmGi6V8ncce0d5kgoNpyEr7Kc
yuoNhBqgc2OSs6ezue9mW18yYbS72I64bL8mdVDT8ivbn2t7u9kEPa5bzUbkkr35
Xh9vuqXADAQECVkkLPaG24vdAKKGBAxJ2TY3D70gkD4YSxARNqJ/hi9OtsPhV1NC
v3D413ohFbAM9nhL5ifg60EAJZyxkBT+aYs0qbVAWLdATHtUDT5NFIiugnwmFlaA
vD3wT8fkc/wakNSOCqbdstn9eaAi1HBsLKxJGPpCXvUEBjmSkUfKgaPL5O+Bz9go
mtjnL8IzNVbT0kbvHhMkG1Wko9/5Z/RpCYp4Y/9X/Ra8oI9/v/JErzzrhY1x3TB8
VNwaxC1NafD8hR753Q/Ww+yxmqtHZ4e/4y0CVeyxd6HPF/ApfmZQcsp4C49GYafW
E0QXvqZ8n31Idr5X/OJw84hYZtKneqEQGdAxcfY5hj2/07Inu4klBNVwHTTny1l1
Hp+v53DWjdNZaTNSBmO6s6O9iuOZHLTBDn16Wl5QXhjz07Q28qUdxD7IfDWYMKED
RVFDC3CsQ90Ctm8wq5ZQ1QFQyK9O4sgQ4KSklUYg1vOyfDt+q6ZTyxneJzcO+xxs
BiZE2Oyv1C+hywLRQ3vwQy31Lx0abTCYfIKEN3nt3kBB2GYw5vQ=
=SJOT
-----END PGP SIGNATURE-----
--- End Message ---
