Source: urlwatch
Version: 2.15-1
User: debian-ci@lists.debian.org
Usertags: needs-update
Control: affects -1 src:python3-defaults
[X-Debbugs-CC: debian-ci@lists.debian.org,
python3-defaults@packages.debian.org]
Dear maintainers,
With a recent upload of python3-defaults (which changed the default
python3 from 3.6 to 3.7) the autopkgtest of urlwatch 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.7.1-2
urlwatch from testing 2.15-1
all others from testing from testing
I copied some of the output at the bottom of this report.
Currently this regression is contributing to the delay of 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 needed, please change
the bug's severity.
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/u/urlwatch/1389136/log.gz
autopkgtest [05:14:00]: test nominalCase.sh: - - - - - - - - - -
results - - - - - - - - - -
nominalCase.sh FAIL stderr:
/usr/lib/python3/dist-packages/urlwatch/reporters.py:335: FutureWarning:
Possible nested set at position 1
autopkgtest [05:14:03]: test migration.sh: - - - - - - - - - - results
- - - - - - - - - -
migration.sh FAIL stderr:
/usr/lib/python3/dist-packages/urlwatch/reporters.py:335: FutureWarning:
Possible nested set at position 1
Attachment:
signature.asc
Description: OpenPGP digital signature