Hi all,

As I mentioned on my previous email, I've been working on the Python
3.15 migration. This is a status update of how things are going as well
as an opportunity for others to help.

## Status

Out of the 7349 packages that I identified as depending on Python in
some way, almost everything has built successfully. 220 failed to build
and 52 are still pending to be built (waiting for build-dependencies).
You can find more details through the dashboard [1].

To get here, I've been applying patches to numerous packages. What I do
is patch the package so that it builds, then send the patch to the BTS.

Some of the build failures are indeed related to Python 3.15, but not
all. Some are due to GCC 16, or Numpy 2.0, or other changes that
affected these packages. Indeed, of the currently failing packages 106
are marked as FTBFS in reproducible builds.

In any case, since I want to verify that everything builds with Python
3.15, I've been taking care of as many packages as I can.

## Release team transition board

The release team has created a transition for Python 3.15 [2]. This
includes 870 packages. Out of those, 759 have been built and tested
successfully, 10 fail to build, and 56 don't pass their tests. [3]

I've been focusing on those remaining packages these past few days,
trying to ensure that the transition goes smoothly when the time comes.

## Request for help

As mentioned, I've been focusing on getting the packages to build in the
sandbox [4], rather than on making the uploads to Debian. Right now,
there are 92 open bugs with available patches (and 53 resolved bugs)
related to this migration [5].

It would be really helpful if more people could jump in and apply those
patches, so that when Python 3.15 is released and added to
python3-defaults, it doesn't cause as much breakage.

## What's next

My next step is to rebuild a subset of the packages again, the ones that
link against cpython, but this time setting Python 3.15 as the default
version. I expect this will uncover more bugs, as there are many
packages that only build for a single Python version, so just having
3.15 available doesn't cause them to build against it.

Happy hacking,

[1]: https://t.gnuservers.com.ar/
[2]: https://release.debian.org/transitions/html/python3.15-add.html
[3]: https://t.gnuservers.com.ar/transition/?
[4]: https://debusine.debian.net/debian/r-python-python3.15/
[5]: 
https://bugs.debian.org/cgi-bin/[email protected]&tag=python3.15

--
"Good judgement comes from experience, and experience comes from bad judgement."
-- Fred Brooks
Saludos /\/\ /\ >< `/

Attachment: signature.asc
Description: PGP signature

Reply via email to