On Thu, Dec 12, 2024 at 10:21:56PM +0000, Colin Watson wrote: > On Thu, Sep 19, 2024 at 07:08:00PM +0200, Stefano Rivera wrote: > > Forwarded: https://github.com/Textualize/rich/pull/3229 > > > > This package failed build from source when test-built against a version of > > python3-defaults that includes 3.13 as a supported version. > > This seems to be fixed in any upstream version >= 13.8.0. Would it be > possible to upgrade? It looks like there are only ~40 packages left > blocking the 3.13-add transition, so it'd be good to clear out the ones > that are fixed upstream.
We're down to <30 blockers. I experimented with an upgrade to the latest upstream release here: https://debusine.debian.net/debusine/System/work-request/66822/ The python-inline-snapshot failure is I think just #1090276, so the only real regression is in textual, which I see you also maintain. I tried upgrading textual to 1.0.0. This needed new "Build-Depends: python3-platformdirs (>= 3.6.0) <!nocheck>, python3-pytest-xdist <!nocheck>", but otherwise works fine. textual's only reverse-dependency is python-memray; its autopkgtests still pass with the upgraded versions of rich and textual. I briefly considered messing about with cherry-picking individual patches as an alternative, but since we aren't in a freeze it seemed to me that it would probably be better to just upgrade both rich and textual. Do you have an opinion on this? If you don't have time and want me to just deal with it in NMUs then I'm happy to do that. -- Colin Watson (he/him) [[email protected]]
