On Sat, Jun 7, 2025 at 3:07 AM Sebastian Ramacher <[email protected]> wrote: > On 2025-06-05 17:51:10 -0400, Jeremy Bícha wrote: > > Release Team, > > > > I noticed today while reading https://bugs.debian.org/1107304 that > > python3.13 was not included in the toolchain packages list [1]. My > > reading of the list is that it was intended to be there. > > It is there. The list contains > > python3 (default) > > That covers python3.13.
I agree on the intent. I had assumed that there would also be a britney block to enforce it but I guess that was a wrong assumption? python3.13 3.13.2-2 and 3.13.2-3 migrated after Toolchain Freeze. And 3.13.3-2 migrated after Soft Freeze. Now it's finally blocked because it is a key package. I don't see any unblock or pre-approval requests for python3.13, despite there being 6 or 7 uploads to Unstable after Toolchain Freeze. The table at https://release.debian.org/testing/freeze_policy.html says that toolchain packages need pre-approval. So I'm a bit annoyed that there was yet another python3.13 upload this week that happened to trigger an RC bug in Unstable for at least one package (pdfarranger). [1] https://release.debian.org/testing/essential-and-build-essential.txt Thank you, Jeremy Bícha
