Source: python-mitogen Version: 0.3.3-7 Severity: serious X-Debbugs-CC: ansible-c...@packages.debian.org Tags: sid bookworm User: debian...@lists.debian.org Usertags: needs-update Control: affects -1 src:ansible-core
Dear maintainer(s),With a recent upload of ansible-core the autopkgtest of python-mitogen fails in testing when that autopkgtest is run with the binary packages of ansible-core from unstable. It passes when run with only packages from testing. In tabular form:
pass fail ansible-core from testing 2.14.0-1 python-mitogen from testing 0.3.3-7 all others from testing from testingI copied some of the output at the bottom of this report. Your package has a hard requirement on older version of either ansible-core or ansible than the current ones.
Currently this regression is blocking the migration of ansible-core to testing [1]. Of course, ansible-core shouldn't just break your autopkgtest (or even worse, your package), but it seems to me that the change in ansible-core 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 ansible-core 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=ansible-core https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-mitogen/29251799/log.gz The following packages have unmet dependencies:ansible-mitogen : Depends: ansible-core (< 2.14) but 2.14.0-1 is to be installed or ansible (< 6) but it is not going to be installed
OpenPGP_signature
Description: OpenPGP digital signature