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

Re: Proposal on how to proceed with Python 2 removal from bullseye

From	Sandro Tosi <morph@debian.org>
Newsgroups	linux.debian.maint.python, linux.debian.devel.release
Subject	Re: Proposal on how to proceed with Python 2 removal from bullseye
Date	2020-01-07 00:20 +0100
Message-ID	<zlJPb-2Tx-1@gated-at.bofh.it> (permalink)
References	(5 earlier) <z9Xbb-8ac-5@gated-at.bofh.it> <zbaSK-4HY-3@gated-at.bofh.it> <zdlK1-5x2-1@gated-at.bofh.it> <zeAH1-48F-29@gated-at.bofh.it> <zg77P-4N3-1@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Cross-posted to 2 groups.

Show all headers | View raw

On Sun, Dec 22, 2019 at 5:58 AM Simon McVittie <smcv@debian.org> wrote:
>
> On Wed, 18 Dec 2019 at 01:08:11 -0500, Sandro Tosi wrote:
> > let me know if this makes sense or additional changes are required.
>
> #942941 in src:dbus-python was bumped to serious because:
> > python-dbus-tests is a module and has 0 external rdeps or not in testing
>
> Please could you give python-dbus-tests or *-tests an exception to the
> RC severity bumps, or only bump the severity if *every* Python 2 binary
> package in a source package is eligible for removal, or something?
> python-dbus still has a significant number of rdeps, and I don't want to
> support python-dbus without keeping its automated tests available.

i just implement what asked here, with also a "rollback" functionality
that will downgrade any RC bug for a source with not-leaf packages.
there's a chance some bugs which severity was raised by hand (f.e.
because a dependency package was removed) will get reverted to normal,
we'll see how it goes. the change will go live in a few minutes.

-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi

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

Thread

Severity bump script Ondrej Novy <novy@ondrej.org> - 2019-11-11 07:50 +0100
  Re: Severity bump script Sandro Tosi <morph@debian.org> - 2019-11-11 16:50 +0100
  Re: Severity bump script Sandro Tosi <morph@debian.org> - 2019-11-15 01:20 +0100
    Re: Severity bump script Dmitry Shachnev <mitya57@debian.org> - 2019-11-15 19:50 +0100
      Re: Severity bump script Sandro Tosi <morph@debian.org> - 2019-11-16 04:10 +0100
    Re: Severity bump script Ondrej Novy <novy@ondrej.org> - 2019-11-22 09:40 +0100
      Re: Severity bump script Sandro Tosi <morph@debian.org> - 2019-11-22 22:30 +0100
        Re: Severity bump script Ondrej Novy <novy@ondrej.org> - 2019-11-27 20:40 +0100
          Re: Severity bump script Sandro Tosi <morph@debian.org> - 2019-11-28 04:20 +0100
            Re: Severity bump script Ondrej Novy <novy@ondrej.org> - 2019-11-28 13:40 +0100
              Re: Severity bump script Sandro Tosi <morph@debian.org> - 2019-11-28 19:10 +0100
                Re: Severity bump script Ondrej Novy <novy@ondrej.org> - 2019-11-28 21:00 +0100
  Re: Severity bump script Sandro Tosi <morph@debian.org> - 2019-12-01 22:50 +0100
    Re: Severity bump script Paul Gevers <elbrus@debian.org> - 2019-12-02 20:30 +0100
      Re: Severity bump script Paul Gevers <elbrus@debian.org> - 2019-12-02 20:40 +0100
        Re: Severity bump script Sandro Tosi <morph@debian.org> - 2019-12-02 22:20 +0100
          Re: Severity bump script Paul Gevers <elbrus@debian.org> - 2019-12-02 22:30 +0100
            Re: Severity bump script Sandro Tosi <morph@debian.org> - 2019-12-02 22:50 +0100
            Re: Severity bump script Mattia Rizzolo <mattia@debian.org> - 2019-12-02 23:40 +0100
        Re: Severity bump script Ondrej Novy <novy@ondrej.org> - 2019-12-03 10:40 +0100
      Re: Severity bump script Ondrej Novy <novy@ondrej.org> - 2019-12-02 21:00 +0100
      Re: Severity bump script Matthias Klose <doko@debian.org> - 2019-12-03 13:30 +0100
        Re: Severity bump script Paul Gevers <elbrus@debian.org> - 2019-12-05 12:10 +0100
          Re: Severity bump script Sandro Tosi <morph@debian.org> - 2019-12-08 21:00 +0100
            Proposal on how to proceed with Python 2 removal from bullseye Paul Gevers <elbrus@debian.org> - 2019-12-14 21:00 +0100
              Re: Proposal on how to proceed with Python 2 removal from bullseye Sandro Tosi <morph@debian.org> - 2019-12-18 07:10 +0100
                Re: Proposal on how to proceed with Python 2 removal from bullseye Simon McVittie <smcv@debian.org> - 2019-12-22 12:00 +0100
                Re: Proposal on how to proceed with Python 2 removal from bullseye Sandro Tosi <morph@debian.org> - 2020-01-07 00:20 +0100

csiph-web