On Tue, Jun 07, 2022 at 08:27:38AM +0100, Julian Gilbey wrote: > > > Anyone willing to go for it? > > > > I thought you were volunteering for it? :) jokes aside, i think > > preparing the new pytest upstream release for experimental may be the > > "easiest" part of this ordeal. > > I guess it will depend on how much breakage it causes; the > deprecations and breaking changes listed at > https://docs.pytest.org/en/stable/changelog.html see somewhat > "obscure", but who knows how much they're used in Debian packages?! > > I wish I could help, but I only have a couple of hours per week for > Debian stuff, so this is beyond my capacity, unfortunately :-(
Actually, on reflection, with the potential size of this, it is probably worth collaborating on; I could certainly participate. Sandro: you managed the numpy transition, it seems. What is involved in something like this? I would imagine something like: (1) Upload pytest 7.x to experimental (2) Arrange with Lucas to test build all rdeps against the experimental version of pytest (by which I mean: all packages which require python3-pytest as a (recursive) build-dependency) (3) File bugs (with patches where possible) against all packages which either FTBFS with the experimental pytest or which fail their autopkgtest suite with the experimental pytest. Presumably these bugs would have a usertag associated with them so they can be easily monitored. (4) After an appropriate time period, prepare NMUs for remaining bugs. (5) Once all bugs are closed, upload to unstable. I could certainly do (1) and help with (3)-(5) if someone else can do (2) and help with (3)-(5). Best wishes, Julian
