On Tue, Jun 07, 2022 at 03:49:37PM -0400, Sandro Tosi wrote: > > 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 > > i took care of this just now, uploading pytest/7.1.2 to experimental > (and i've messed up the branches on salsa, so i've committed my > changes to `experimental2`)
Amazing, thanks! I might have used a version number such as -1~exp1, but that is fairly immaterial. And at least I'm not the only one to mess up things on salsa! ;-) > > (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) > > I'll take care of this soon, likely after pytest has been built on a > buildd host (so will be either later today EST or tomorrow) Great! > > (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. > > that's something usually Lucas can automate, but he'll provided a set > of failed/successful logs for us to look at. OK, that's really helpful. > > (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 Best wishes, Julian
