Your message dated Mon, 15 Dec 2025 16:49:41 +0000
with message-id <[email protected]>
and subject line Bug#1122099: fixed in python-uvicorn 0.38.0-1
has caused the Debian Bug report #1122099,
regarding src:uvloop: fails to migrate to testing for too long
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 [email protected]
immediately.)
--
1122099: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1122099
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: uvloop
Version: 0.21.0+ds1-3
Severity: serious
Control: close -1 0.22.1+ds1-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:uvloop 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. Additionally, blocked packages can have impact on
other packages, which makes preparing for the release more difficult.
Finally, it often exposes issues with the package and/or its
(reverse-)dependencies. We expect maintainers to fix issues that hamper
the migration of their package in a timely manner.
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 and has only been sent
manually. 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=uvloop
Current text from [2]:
Migration status for uvloop (0.21.0+ds1-3 to 0.22.1+ds1-1): BLOCKED:
Rejected/violates migration policy/introduces a regression
Issues preventing migration:
∙ ∙ Updating uvloop would introduce bugs in testing: #1122066
∙ ∙ Autopkgtest for python-uvicorn/0.32.0-3: amd64: Regression ♻
(reference ♻), arm64: Regression ♻ (reference ♻), i386: Regression ♻
(reference ♻), ppc64el: Regression ♻ (reference ♻), riscv64: Failed (not
a regression) ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
∙ ∙ Autopkgtest for uvloop/0.22.1+ds1-1: amd64: Pass, arm64: Pass, i386:
Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
Additional info (not blocking):
∙ ∙ Piuparts tested OK -
https://piuparts.debian.org/sid/source/u/uvloop.html
∙ ∙ Reproducible on amd64 - info ♻ ∙ ∙ Reproducible on arm64 - info ♻ ∙
∙ 31 days old (needed 5 days)
OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: python-uvicorn
Source-Version: 0.38.0-1
Done: Colin Watson <[email protected]>
We believe that the bug you reported is fixed in the latest version of
python-uvicorn, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Colin Watson <[email protected]> (supplier of updated python-uvicorn package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Mon, 15 Dec 2025 16:31:45 +0000
Source: python-uvicorn
Architecture: source
Version: 0.38.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team <[email protected]>
Changed-By: Colin Watson <[email protected]>
Closes: 1122099
Changes:
python-uvicorn (0.38.0-1) unstable; urgency=medium
.
* Team upload.
* New upstream release:
- Fix test failure with current uvloop (closes: #1122099).
* Build-depend on mkdocs-material, now that it's in Debian.
* Use dh-sequence-mkdocs and dh-sequence-python3.
* Drop "Rules-Requires-Root: no", default as of dpkg-dev 1.22.13.
* Standards-Version: 4.7.2.
Checksums-Sha1:
4130b5eaeeacf7a341868de6d923afae786d54f9 2904 python-uvicorn_0.38.0-1.dsc
2dab33bbfedb301d17a37d3735f4ab7a0ebf5c1a 827432
python-uvicorn_0.38.0.orig.tar.gz
eb8791668ac7b3081ec60c7ed45fd9b4efda73eb 7648
python-uvicorn_0.38.0-1.debian.tar.xz
Checksums-Sha256:
e4793d3a3ddc93eb8f4624025ec6e0fcec2aec98703a7988934e4d7939c9365b 2904
python-uvicorn_0.38.0-1.dsc
788c7f1c42ddc698e8735e1c0af8be0a6bc07da5ab51f1d2a05d3c47d5f2cadb 827432
python-uvicorn_0.38.0.orig.tar.gz
927dcd06fd457f57f7c48e50f8be7fa4203f4e108b67eebc429ec7c3b8f7d813 7648
python-uvicorn_0.38.0-1.debian.tar.xz
Files:
1d4fe5df7386b3a0d0a6b89fd145c333 2904 python optional
python-uvicorn_0.38.0-1.dsc
b52d151be25e4c16d8d81730aece57b5 827432 python optional
python-uvicorn_0.38.0.orig.tar.gz
408eab7056c076a11ea38f029e5955a8 7648 python optional
python-uvicorn_0.38.0-1.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEErApP8SYRtvzPAcEROTWH2X2GUAsFAmlAODUACgkQOTWH2X2G
UAu4xA//fWBDfFzvZ2D/AIdO4fSnm/PbyoJAU0L5zSVCM9eEbmfJs28maHueOe9L
TDEAX6X0LFePoLTYeuE4hkwRd2CKmmybX7Bp+RKDui9Vhw7qyl0Kr4QTNSQ1Ggb7
TZdM59A9pVoMIktF3bYCLCftsej76kGtzWv3bVbvTbocZd1FoLY4y6JFEagZkFon
jAR3vW8dumwchxu7WaDqHdi/8fk6XpcXVGRk+KIETot6na/mldslVFu//i6x2X81
Uh2JWDrZ1bbDzN+7Am+p9kWZJjRIBj7EAIR640J1NoS7MXAjHOyRjtk5uKUi1Sug
2Ok5BHVW3BKueG2CIsHEVVXOywcj7y5W5RajkMYM6UKQ9fAkPzWmzUDDoeuK3qCy
R1WdAiq6e1yE0hWYy7uDFYRBPNSgD8HxdZtgt8Voi/O5Ex5AZtwcBF1i8wR5Txf2
0/KS9m2MJFUwaL/+Fo8Sc0dGx99ob3Y40VRG2pD5eel/MDA1mkf6Eoh11GaMJX/z
qZMqT0+oXjDBtHrcvwoMmRlBvQrrBAK8p5CUIWWfyw4mf/QgG83pTi35J1xga2Xl
3fbdSY3kPTqVm5435hRH3CGX+Fr4f5p51x6jQwDNCX5TI/J2XcUZAgxNL2CK0Nhx
WuptSjvuTWfE5qACwYtfhdJmC2sA7nj3cEU3OzkhMPfayO4THT0=
=Oh+5
-----END PGP SIGNATURE-----
pgpoM2GbdnRV_.pgp
Description: PGP signature
--- End Message ---