[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1012208: unblock: python-pytest-asyncio/0.18.2-1



Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: unblock

Please unblock package python-pytest-asyncio

(Please provide enough (but not too much) information to help
the release team to judge the request efficiently. E.g. by
filling in the sections below.)

[ Reason ]
python-pytest-asyncio and pytest-mock need to be upgraded together;
pytest-mock 3.7.0-2 build-depends on the newer version of
python-pytest-asyncio (0.18.2-1), while the older version of
pytest-mock (3.6.1-1) breaks with it.  So python-pytest-asyncio can't
transition because it will break the version of pytest-mock already in
testing, and pytest-mock can't transition because of the
build-dependency on the newer python-pytest-asyncio.

[ Impact ]
(What is the impact for the user if the unblock isn't granted?)
python3-jupyter-kernels won't transition, and so I can't get the newer
verion of spyder into testing either (I haven't uploaded it to
unstable yet, though).

[ Tests ]
(What automated or manual tests cover the affected code?)
It's the autopkgtests that are blocking things; they succeed (at least
for me) if the newer versions of both packages are used.

[ Risks ]
(Discussion of the risks involved. E.g. code is trivial or
complex, key package vs leaf package, alternatives available.)
A lot of packages use these in their testing suites.

[ Checklist ]
  [ ] all changes are documented in the d/changelog
  [ ] I reviewed all changes and I approve them
  [ ] attach debdiff against the package in testing
  not so relevant here?

[ Other info ]
(Anything else the release team should know.)

unblock python-pytest-asyncio/0.18.2-1


Reply to: