On Wed, Nov 13, 2024 at 10:29:06AM +0100, Matthias Klose wrote: > python3-defaults in unstable now adds Python 3.13 as a supported Python 3.13 > version. You might see some additional build failures, until the binNMUs > for this addition are done [1]. This might take some days for some > architectures. We will most likely also see some more issues once the lower > levels of this addition are done. [...] > [1] https://release.debian.org/transitions/html/python3.13-add.html
While there are a few bits of that transition tracker still red, the current target is to work on the list of autopkgtest failures shown on https://tracker.debian.org/pkg/python3-defaults in order to get the addition of 3.13 as a supported version into testing. As usual, this page can be a little hard to interpret because it shows test failures of the versions of those packages in testing, and you have to click through to each corresponding package (sometimes through multiple levels of failures) to see whether it's been fixed in unstable. But with ~35 packages left there, it's getting easier to wade through and we're getting pretty close. Here's the current state, with my comments: * audioread: #1082047; apparently needs packaging of a couple of pieces removed from the standard library. Reverse-dependencies are eartag, puddletag, and python3-acoustid. * dask/dask.distributed: #1088234 and #1088286, but also #1085947 in sphinx-book-theme. I sank a bunch of time into trying to fix this last month and didn't really get anywhere very satisfying. Can anyone with more experience with these packages figure this out? * datalad-next: #1088038. Probably not too hard if you can figure out how that test is supposed to work. * deepdiff: #1088239, blocked by orderly-set in NEW. I poked #debian-ftp. * hyperkitty: #1088312. Should be fairly easy. * ipykernel: Fixed in unstable. * ironic-python-agent: #1089531. Should be fairly easy; zigo said on IRC that this is a leaf package and doesn't need to block migration. * jinja2: Fixed in unstable. * jupyter-server: Fixed in unstable. * mdp: Fixed in unstable. * ovn-octavia-provider: #1088762. zigo said on IRC that this is a leaf package and doesn't need to block migration. * pocketsphinx-python: #1088764. Apparently difficult. * pytest-jupyter: Fixed by new ipykernel in unstable. * python-attrs: Fixed in unstable; blocked on python-cattrs. * python-beartype: #1089017. Apparently fixed upstream, though I don't know exactly where. * python-cattrs: #1073406/#1086614. * python-omegaconf: #1089049. * python-oslo.messaging: I believe this is fixed in unstable (#1089050) and waiting for python-eventlet to migrate to testing. * python-pure-python-adb: #1082251/#1084618; apparently just needs a dependency on python3-zombie-telnetlib? * python-voip-utils: #1088827 fixed in unstable, but has an autopkgtest regression on s390x (#1089826). * rich: #1082290; seems to be fixed upstream. * smart-open: #1089053; upstream fix in progress. * spyder: #1088068/#1089054. * twisted: Fixed in unstable, just waiting for matrix-synapse to migrate first (which should be soon). There are also a number of architecture-specific failures showing up there. Some might go away with a few more retries I guess, but we'll likely need to work out what to do about the rest. I haven't looked at these in any depth. Can anyone help with any of the remaining problems here? This would be especially useful for packages that aren't maintained by the Python team. -- Colin Watson (he/him) [cjwat...@debian.org]
