Bug#1142796: src:python-eventlet: fails to migrate to testing for too long

Paul Gevers <[email protected]>
Newsgroups gmane.linux.debian.devel.bugs.rc
Message-ID <be77c344-c952-484f-9782-b44872453db5__10543.1491554313$1785048319$gmane$org@debian.org>
Source: python-eventlet
Version: 0.40.4-1
Severity: serious
Control: close -1 0.40.4-4
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-eventlet has been trying to migrate 
for 34 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. [end of 
template] It seems that the added Breaks on python3-trio causes the 
Build-Depends of src:octavia-dashboard to not be installable. [continue 
with template]

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-eventlet

Current text from [2]:
Migration status for python-eventlet (0.40.4-1 to 0.40.4-4): Will 
attempt migration (Any information below is purely informational)
Additional info (not blocking):
∙ ∙ Piuparts tested OK - 
https://piuparts.debian.org/sid/source/p/python-eventlet.html
∙ ∙ Autopkgtest for python-eventlet/0.40.4-4: amd64: Pass, arm64: Pass, 
armhf: Pass, i386: Pass, loong64: Pass, ppc64el: Pass, riscv64: Pass, 
s390x: Pass
∙ ∙ Autopkgtest for swift/2.37.1-5: amd64: Pass, arm64: Pass, armhf: No 
tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, 
superficial or marked flaky ♻, loong64: No tests, superficial or marked 
flaky ♻ (reference ♻), ppc64el: Pass, riscv64: Ignored failure ♻ 
(reference ♻), s390x: Test triggered (failure will be ignored)
∙ ∙ Reproduced on amd64 - info
∙ ∙ Reproduced on arm64 - info
∙ ∙ Reproduced on armhf - info
∙ ∙ Reproduced on i386 - info
∙ ∙ Required age reduced by 3 days because of autopkgtest
∙ ∙ 31 days old (needed 2 days)
OpenPGP_signature.asc (application/pgp-signature, 585 B)
-----BEGIN PGP SIGNATURE-----

wsC7BAABCABvBYJqZaxICRCcXJnrBb11CkcUAAAAAAAeACBzYWx0QG5vdGF0aW9u
cy5zZXF1b2lhLXBncC5vcmeVGWXF0m8AU4zJnX/Rld4RMkhu70OAWm8Wto+F8c6z
NxYhBFi2bUhza+k7BS3mcpxcmesFvXUKAABrGwf/UrHYa3DYpom7lzI0+Csdiq+e
55tu2CxUnWFAu1yivnfMSMuNsOwTNxixJlFJG02TXu+2TpM1TgqWU/BkKrDZpbV6
DDNccianCUoV+Q9edImtqGB6Yhs4pQsOtFGP3h3dlusGNftxZ1BY0CdV4D7X9VBu
AKCEE8ZVTs0+XvEG+gKP2HoZ/4zHp1tvHPNeiH0bk3lo73hfvHM/sO8aAMLAXplB
ydxWYPTSwkGLKGlSp6sGbPfCGTi4ZbAP6id8xn1hb8JNopkuF5O4hb1+JR4b/GMk
XzKHDTsMoj8lpvYJPx+1eML2L5ricpt8eB8sd3w1iWNnDDtN+DnNisWfX/thRQ==
=7Vu2
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.