Bug#1143469: src:python-treq: fails to migrate to testing for too long

Source: python-treq
Version: 25.5.0-2
Severity: serious
Control: close -1 26.7.0-1
Tags: sid forky
User: [email protected]
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:python-treq has been trying to migrate for 
31 days [2], hence this bug report. The current output of the migration 
software for this package is copied to the bottom of this report and 
should list the reason why the package is blocked.

If a package is out of sync between unstable and testing for a longer 
period, this usually means that bugs in the package in testing cannot be 
fixed via unstable. Blocked packages can have impact on other packages, 
which makes preparing for the release more difficult. The situation that 
caused this bug report might even be the result of such an issue. We 
expect maintainers to fix issues that hamper the migration of their 
package in a timely manner. If your package in this situation due to 
another package, consider helping out.

This bug will trigger auto-removal when appropriate. As with all new 
bugs, there will be at least 30 days before the package is auto-removed.

This bug submission immediately closes the bug with the version in 
unstable, so if that version or a later version migrates, this bug will 
no longer affect testing. This bug is also tagged to only affect sid and 
forky, so it doesn't affect (old-)stable.

If you believe your package is unable to migrate to testing due to 
issues beyond your control, don't hesitate to contact the Release Team.

This bug report has been automatically generated. If you have any 
comments with regards to the content or the process, please reach out to me.

Paul

[1] https://lists.debian.org/debian-devel-announce/2023/06/msg00001.html
[2] https://qa.debian.org/excuses.php?package=python-treq

Current text from [2]:
Migration status for python-treq (25.5.0-2 to 26.7.0-1): BLOCKED: 
Rejected/violates migration policy/introduces a regression
Issues preventing migration:
∙ ∙ Autopkgtest for matrix-synapse/1.152.1-1: amd64: Regression ♻ 
(reference ♻), arm64: Regression ♻ (reference ♻), armhf: Regression ♻ 
(reference ♻), i386: Regression ♻ (reference ♻), loong64: Regression ♻ 
(reference ♻), ppc64el: Regression ♻ (reference ♻), riscv64: Regression 
♻ (reference ♻), s390x: Regression ♻ (reference ♻)
∙ ∙ Autopkgtest for python-treq/26.7.0-1: amd64: Pass, arm64: Pass, 
armhf: Pass, i386: Pass, loong64: Pass, ppc64el: Pass, riscv64: Pass, 
s390x: Pass
Additional info (not blocking):
∙ ∙ Piuparts tested OK - 
https://piuparts.debian.org/sid/source/p/python-treq.html
∙ ∙ Reproduced on amd64 - info
∙ ∙ Reproduced on arm64 - info
∙ ∙ Reproduced on armhf - info
∙ ∙ Reproduced on i386 - info
∙ ∙ 31 days old (needed 5 days)

-----BEGIN PGP SIGNATURE-----

wsC7BAABCABvBYJqbxQrCRCcXJnrBb11CkcUAAAAAAAeACBzYWx0QG5vdGF0aW9u
cy5zZXF1b2lhLXBncC5vcmdL3PSvgoBvujUSRlqJvZquH1c4+3KT7fDzKhV6l+lv
rBYhBFi2bUhza+k7BS3mcpxcmesFvXUKAAD1lgf+Mg/+RHJSF3n1zLCwW5/8zvQc
fFw/NueVQBKZbM3PLpLtATWFVwQLetz4FDBZlmuJL3zaw4F1vEmRyPVTIFBdSuWx
64Cy88lAzm7X2KAxeaxEZjZncOMMDgw7vM8edwNuhi9+Du2t6kd3magZhZc8lIBn
5OHKzz0KWALcc4lzcOCs8/qpbaPgt97g/N9AxS81qF3/4BgdLy4gCThCiozXmAHz
u4khVFH3Aq6+4Pkfyw12gRxTvdBVRBpBCLWJj5GzIpkfAZr7hjAIw0TiAvefCZ75
YtFv7vnC3ImGU3e6oF3CNO2aD4C3cetyN7lD30IVotEdk8h/lKefFXMAhC77hw==
=K9RG
-----END PGP SIGNATURE-----