Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.maint.python > #14147

Re: Updating pytest

From Julian Gilbey <julian@d-and-j.net>
Newsgroups linux.debian.maint.python
Subject Re: Updating pytest
Date 2022-06-07 14:50 +0200
Message-ID <EvGOJ-3ciy-3@gated-at.bofh.it> (permalink)
References (4 earlier) <EujUd-2kpz-11@gated-at.bofh.it> <EurRL-2p9E-3@gated-at.bofh.it> <Evty9-33vd-3@gated-at.bofh.it> <EvvTj-359t-3@gated-at.bofh.it> <EvBP4-395I-5@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


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

Back to linux.debian.maint.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

Updating pytest Julian Gilbey <julian@d-and-j.net> - 2022-06-02 14:10 +0200
  Re: Updating pytest Andrius Merkys <merkys@debian.org> - 2022-06-02 14:20 +0200
    Re: Updating pytest Sandro Tosi <morph@debian.org> - 2022-06-02 16:30 +0200
      Re: Updating pytest julien.puydt@gmail.com - 2022-06-02 17:30 +0200
        Re: Updating pytest Julian Gilbey <julian@d-and-j.net> - 2022-06-03 20:10 +0200
          Re: Updating pytest Paul Wise <pabs@debian.org> - 2022-06-04 04:40 +0200
            Re: Updating pytest Julian Gilbey <julian@d-and-j.net> - 2022-06-07 00:40 +0200
              Re: Updating pytest Sandro Tosi <morph@debian.org> - 2022-06-07 03:10 +0200
                Re: Updating pytest Julian Gilbey <julian@d-and-j.net> - 2022-06-07 09:30 +0200
                Re: Updating pytest Julian Gilbey <julian@d-and-j.net> - 2022-06-07 14:50 +0200
                Re: Updating pytest Sandro Tosi <morph@debian.org> - 2022-06-07 22:00 +0200
                Re: Updating pytest Julian Gilbey <julian@d-and-j.net> - 2022-06-08 10:10 +0200
                Re: Updating pytest Julian Gilbey <julian@d-and-j.net> - 2022-06-08 13:50 +0200
                Re: Updating pytest Andrius Merkys <merkys@debian.org> - 2022-06-08 13:50 +0200
                Re: Updating pytest Andrius Merkys <merkys@debian.org> - 2022-06-07 09:40 +0200

csiph-web