Your message dated Thu, 9 Jan 2025 16:38:41 +0000
with message-id <z3_7kwnddkfn7...@riva.ucam.org>
and subject line Re: Bug#1091004: python-ring-doorbell: autopkgtest needs
update for new version of python-pytest-asyncio
has caused the Debian Bug report #1091004,
regarding python-ring-doorbell: autopkgtest needs update for new version of
python-pytest-asyncio
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.)
--
1091004: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1091004
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-ring-doorbell
Version: 0.8.12-1
Severity: serious
X-Debbugs-CC: python-pytest-asyn...@packages.debian.org
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:python-pytest-asyncio
Dear maintainer(s),
With a recent upload of python-pytest-asyncio the autopkgtest of
python-ring-doorbell fails in testing when that autopkgtest is run with
the binary packages of python-pytest-asyncio from unstable. It passes
when run with only packages from testing. In tabular form:
pass fail
python-pytest-asyncio from testing 0.24.0a1-1
python-ring-doorbell from testing 0.8.12-1
all others from testing from testing
I copied some of the output at the bottom of this report. The test fails
because a deprecation warning is printed to stderr (which by default
fails an autopkgtest unless the allow-stderr restriction is used).
Currently this regression is blocking the migration of
python-pytest-asyncio to testing [1]. Of course, python-pytest-asyncio
shouldn't just break your autopkgtest (or even worse, your package), but
it seems to me that the change in python-pytest-asyncio 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 python-pytest-asyncio
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=python-pytest-asyncio
https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-ring-doorbell/55591542/log.gz
54s /usr/lib/python3/dist-packages/pytest_asyncio/plugin.py:208:
PytestDeprecationWarning: The configuration option
"asyncio_default_fixture_loop_scope" is unset.
OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: python-ring-doorbell
Source-Version: 0.9.12-1
On Sun, Dec 22, 2024 at 08:11:28AM +0100, Paul Gevers wrote:
> 54s /usr/lib/python3/dist-packages/pytest_asyncio/plugin.py:208:
> PytestDeprecationWarning: The configuration option
> "asyncio_default_fixture_loop_scope" is unset.
This was fixed in 0.9.12-1:
python-ring-doorbell (0.9.12-1) unstable; urgency=medium
* New upstream release fixing warnings using pytest-asyncio.
* Add myself to uploaders.
-- Roland Mas <lola...@debian.org> Wed, 20 Nov 2024 19:13:15 +0100
... but that hadn't made it to testing due to other problems. I just
uploaded 0.9.12-3 (mostly the work of Carles and Roland) which should be
able to migrate.
--
Colin Watson (he/him) [cjwat...@debian.org]
--- End Message ---
