On Mon, Dec 16, 2024 at 01:58:14AM +0000, Colin Watson wrote: > 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.
We've dealt with on the order of half of those one way or another, so here's an update: > * audioread: #1082047; apparently needs packaging of a couple of pieces > removed from the standard library. Reverse-dependencies are eartag, > puddletag, and python3-acoustid. I poked #debian-ftp about maybe getting python-deadlib through NEW. > * 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? Currently exchanging email with Nilson about the state of sphinx-book-theme. It might also be worth somebody seeing if it's practical to temporarily detach dask/dask.distributed from its documentation theme. > * datalad-next: #1088038. Probably not too hard if you can figure out > how that test is supposed to work. Fixed. > * deepdiff: #1088239, blocked by orderly-set in NEW. I poked > #debian-ftp. ftpmaster processed orderly-set through NEW, so Emmanuel fixed this in unstable. There's currently an i386 autopkgtest failure, but Fabian fixed rust-associative-cache to build on i386, and that should sort it out once it reaches testing. > * hyperkitty: #1088312. Should be fairly easy. No progress - anyone? > * 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. > > * ovn-octavia-provider: #1088762. zigo said on IRC that this is a leaf > package and doesn't need to block migration. Thomas fixed these two in unstable. > * pocketsphinx-python: #1088764. Apparently difficult. No progress as far as I know. (I guess we could wait for autoremoval from testing, which is currently scheduled for 29 December.) > * 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. No progress on this lot as far as I know. > * python-oslo.messaging: I believe this is fixed in unstable > (#1089050) and waiting for python-eventlet to migrate to testing. Fixed. > * python-pure-python-adb: #1082251/#1084618; apparently just needs a > dependency on python3-zombie-telnetlib? Emmanuel fixed this in unstable. > * python-voip-utils: #1088827 fixed in unstable, but has an autopkgtest > regression on s390x (#1089826). No progress. I poked Edward on IRC. > * rich: #1082290; seems to be fixed upstream. I investigated this (with help from debusine's new reverse-dependency autopkgtest workflow) and concluded that upgrading rich and textual should fix it; details in the bug. Waiting for feedback from Sandro. > * smart-open: #1089053; upstream fix in progress. Fixed in unstable. > * spyder: #1088068/#1089054. See replies to this email thread. There's clearly some more work to do here, but it looks somewhat tractable. > * twisted: Fixed in unstable, just waiting for matrix-synapse to > migrate first (which should be soon). Fixed. > 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. I chased down a few of these. dipy is fixed in unstable; fenics-basix is #1090766; I fixed pytest-forked and pytest-mpi in unstable. python-libtmux/s390x (e.g. https://ci.debian.net/packages/p/python-libtmux/testing/s390x/55551127/) looks as though it needs investigation. statsmodels/armel (e.g. https://ci.debian.net/packages/s/statsmodels/testing/armel/55559166/) probably just requires skipping some slow tests, since the test takes twice as long while we have two supported Python versions and it's not very fast on armel to begin with. Somebody who knows the package better than I do can probably make a guess at which tests are most reasonable to exclude. -- Colin Watson (he/him) [cjwat...@debian.org]
