Your message dated Fri, 04 Dec 2020 06:18:20 +0000
with message-id <e1kl4q8-0002bu...@fasolo.debian.org>
and subject line Bug#975900: fixed in aria2 1.35.0-3
has caused the Debian Bug report #975900,
regarding aria2: autopkgtest needs update for new version of python3-defaults:
output to stderr
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.)
--
975900: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975900
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: aria2
Version: 1.35.0-2
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org,
python3-defau...@packages.debian.org
Tags: sid bullseye
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:python3-defaults
Dear maintainer(s),
With a recent upload of python3-defaults the autopkgtest of aria2 fails
in testing when that autopkgtest is run with the binary packages of
python3-defaults from unstable. It passes when run with only packages
from testing. In tabular form:
pass fail
python3-defaults from testing 3.9.0-3
aria2 from testing 1.35.0-2
all others from testing from testing
I copied some of the output at the bottom of this report. To me the
failure seems to be due to harmless output to stderr. The test itself
seems to consider the situation OK. (If the output to stderr can't be
prevented easily, there is the allow-stderr restriction).
Currently this regression is blocking the migration of python3-defaults
to testing [1]. Of course, python3-defaults shouldn't just break your
autopkgtest (or even worse, your package), but it seems to me that the
change in python3-defaults was intended and your package needs to update
to the new situation.
If this is a real problem in your package (and not only in your
autopkgtest), the right binary package(s) from python3-defaults should
really add a versioned Breaks on the unfixed version of (one of your)
package(s). Note: the Breaks is nice even if the issue is only in the
autopkgtest as it helps the migration software to figure out the right
versions to combine in the tests.
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://qa.debian.org/excuses.php?package=python3-defaults
https://ci.debian.net/data/autopkgtest/testing/amd64/a/aria2/8417542/log.gz
autopkgtest [12:09:47]: test httpfile: [-----------------------
11/25 12:09:48 [[1;32mNOTICE[0m] Downloading 1 item(s)
11/25 12:09:48 [[1;31mERROR[0m] Failed to load trusted CA certificates
from /etc/ssl/certs/ca-certificates.crt. Cause: Error while reading file.
127.0.0.1 - - [25/Nov/2020 12:09:48] "GET /debian/control HTTP/1.1" 200 -
11/25 12:09:48 [[1;32mNOTICE[0m] Download complete:
/tmp/autopkgtest-lxc.dha_1a5m/downtmp/autopkgtest_tmp/control
Download Results:
gid |stat|avg speed |path/URI
======+====+===========+=======================================================
dced68|OK |
546KiB/s|/tmp/autopkgtest-lxc.dha_1a5m/downtmp/autopkgtest_tmp/control
Status Legend:
(OK):download completed.
autopkgtest [12:09:48]: test httpfile: -----------------------]
autopkgtest [12:09:49]: test httpfile: - - - - - - - - - - results - -
- - - - - - - -
httpfile FAIL stderr: 127.0.0.1 - - [25/Nov/2020 12:09:48]
"GET /debian/control HTTP/1.1" 200 -
autopkgtest [12:09:49]: test httpfile: - - - - - - - - - - stderr - - -
- - - - - - -
127.0.0.1 - - [25/Nov/2020 12:09:48] "GET /debian/control HTTP/1.1" 200 -
autopkgtest [12:09:49]: @@@@@@@@@@@@@@@@@@@@ summary
signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: aria2
Source-Version: 1.35.0-3
Done: Kartik Mistry <kar...@debian.org>
We believe that the bug you reported is fixed in the latest version of
aria2, 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 975...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Kartik Mistry <kar...@debian.org> (supplier of updated aria2 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: Fri, 04 Dec 2020 11:34:30 +0530
Source: aria2
Architecture: source
Version: 1.35.0-3
Distribution: unstable
Urgency: low
Maintainer: Patrick Ruckstuhl <patr...@ch.tario.org>
Changed-By: Kartik Mistry <kar...@debian.org>
Closes: 975900
Changes:
aria2 (1.35.0-3) unstable; urgency=low
.
[ Patrick Ruckstuhl ]
* debian/control:
+ Updated Standards-Version to 4.5.1
* debian/tests/control
+ Add restriction to allow-stderr (Closes: #975900)
.
[ Kartik Mistry ]
* Updated debian/watch.
Checksums-Sha1:
11f6b28c1d1d0e1f6fa81889f0289d20cd6afca5 2172 aria2_1.35.0-3.dsc
d37f26832249dfd6a83fe37c1b7358f6306b1ae1 6440 aria2_1.35.0-3.debian.tar.xz
Checksums-Sha256:
ff4948d34f4f7e850b66e7257b659feb3d462ffa6e987c8715894d0cdc26bafd 2172
aria2_1.35.0-3.dsc
f4e9e9b3793be5d37f7cb231e85e851f40c8abcfa1ccaa55f81ef33f6e17cd58 6440
aria2_1.35.0-3.debian.tar.xz
Files:
6e1f0fb814d51bde17524adb65c2feb7 2172 net optional aria2_1.35.0-3.dsc
8fd813b8e505f30e1c842204c6ed3d12 6440 net optional aria2_1.35.0-3.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEEa2MbXvVUr2sRlmKSAsHT8ng6pN4FAl/J0f8ACgkQAsHT8ng6
pN4LXhAAu+bDqrDjsXcvL5CYpELSTpF//Q37GVBV512exMG00BFb9zrCCYTdsCRp
EIfB9NT2eNfbHCJPYmRT7KCOVAmLeUf5b3EwKP6k1n1OXvP0WRIMYZw1MRA0KWLM
wUYFQwMjamJ+OtMEBvtNLj7CuE+LonfvEDAaK85WbnlEZSvczfUzMCehm8JPCSNb
r67xXdWCplXODApcbpaxqBQ275dR9wajMhT3VjsZR23+ACdu2iAKxHhx7PW1sMI7
E0hbNhBIAiD2ggetAdjXbuwmt67ko8eoLMk1+gYMSSWKWbR+YurXcR8Tt6prgnte
b2sOcplI12SHU299T4yINl5wZu7nGK7gdGoGmcZ+5qYa9mXZqOiEuBE0ndl15gS0
toGwYHAn2lGNvUskK4E1mhHHBy82FW+IKClAt1fsv7JPm25x45ie9CICedSlFH16
d/dI7lr5wO+QPcwJPWgFPJWiCQQ1t+h654PBB8nqUECVzgUguD2NFF0ll1WbqEY/
IqCALgIsZ588FPieh7xbL9Ju8oHIhv58a67MOgluecKlWxmWIlU0Ebm+SDVRpbUg
uuhPPnDui3AOdWlEW80o4gMda44e+t8ECVD8TXEzKpIApEInpzFDp4FDRefBN0Ne
jKUuoks211Uu2bqjyjAVwvxu+sKfliEpPi7jyxLr4h5AQwrd6s0=
=fTRg
-----END PGP SIGNATURE-----
--- End Message ---
