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

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

Path	csiph.com!aioe.org!bofh.it!news.nic.it!robomod
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	Tue, 07 Jan 2020 00:20:01 +0100
Message-ID	<zlJPb-2Tx-1@gated-at.bofh.it> (permalink)
References	<z1aAF-482-3@gated-at.bofh.it> <z1bGp-4LZ-5@gated-at.bofh.it> <z8Fgl-8ku-1@gated-at.bofh.it> <z8Zyq-4iK-9@gated-at.bofh.it> <z9ftw-5Xo-5@gated-at.bofh.it> <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>
X-Original-To	Simon McVittie <smcv@debian.org>
X-Mailbox-Line	From debian-python-request@lists.debian.org Mon Jan 6 23:15:35 2020
Old-Return-Path	<sandro.tosi@gmail.com>
X-Amavis-Spam-Status	No, score=-4.841 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, LDO_WHITELIST=-5, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SARE_MLH_Stock10=1.66] autolearn=no autolearn_force=no
X-Policyd-Weight	NOT_IN_SBL_XBL_SPAMHAUS=-1.5 CL_IP_EQ_HELO_IP=-2 (check from: .gmail. - helo: .mail-qv1-f67.google. - helo-domain: .google.) FROM/MX_MATCHES_HELO(DOMAIN)=-2; rate: -5.5
X-Google-Dkim-Signature	v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=phAItXTm6zc8edZ+0hwaubG97ziJ+fygYm9SJxMCCd0=; b=W0GMvE8Z2Ji4kocQ14v2hy7rUHZ+pyRgcGYsu30rX0Q7T3+AHuTmncX2f1dD0e5UW2 z1WHlOFutz0dZ+B7ecw+wcyELnAc7kc/vJV0D+gZCbyYg4uxTm7WDcu1o/YSTX8izTyK Oqcu9oKHG5zZ+K/QT6CO+qAT6JoWDGkfXqAB/c88CyGTRgwkP/2g0N7+FuyssHrEV983 +Yh7E4JjeQIbh30ajg4fVInq5CY+aNdYrOJtFipXAZYmaDmGQWKadLueoR6Fs3WB+pOj jj+/HM72IEHQaJKf5e4zjjEHqw2RQBB2cujCUaZYCY7BLdPKttU/P5MAO0XbPcUdUUKS pHCw==
X-Gm-Message-State	APjAAAWSYub60kSWjRHCmyNz1EsvAdNGdFKVHR6dnNyu2g+XZqdyfeZy MkDMlV5yUiICbQqozfPq2QTk8CkCcK0A6i80r9c=
X-Google-SMTP-Source	APXvYqz6ty+UdRglpxEKQqDRdpMIpekP3p9/DPOjFdjXIPyR9O+C8WPM9qyNKTNsKMncVY62gWx+p3KXhdrqb1mBYns=
X-Received	by 2002:a05:6214:10cb:: with SMTP id r11mr78500772qvs.59.1578352519919; Mon, 06 Jan 2020 15:15:19 -0800 (PST)
MIME-Version	1.0
Content-Type	text/plain; charset="UTF-8"
X-Mailing-List	<debian-python@lists.debian.org> archive/latest/17802
List-ID	<debian-python.lists.debian.org>
List-URL	<https://lists.debian.org/debian-python/>
List-Archive	https://lists.debian.org/msgid-search/CAB4XWXyZ2uZ6qzFnYYE6MR6Wva9FMjipV4swZVqW0a4DAxhb9Q@mail.gmail.com
Approved	robomod@news.nic.it
Lines	25
Organization	linux.* mail to news gateway
Sender	robomod@news.nic.it
X-Original-Cc	Paul Gevers <elbrus@debian.org>, debian-python <debian-python@lists.debian.org>, Debian release team <debian-release@lists.debian.org>
X-Original-Date	Mon, 6 Jan 2020 18:14:53 -0500
X-Original-Message-ID	<CAB4XWXyZ2uZ6qzFnYYE6MR6Wva9FMjipV4swZVqW0a4DAxhb9Q@mail.gmail.com>
X-Original-References	<349bb59d7f28ad6c70e567d9939b99f2f924d01a.camel@ondrej.org> <CAOO6c=zo004jCyXYMYbBhPonWk+CgTu368EtFfdPR9wJN3=jgw@mail.gmail.com> <CAB4XWXz6g5iz=60Kta-wZSPicq9uK_gk1CZcPCVdY8G3rzd1-g@mail.gmail.com> <153751f7-2d80-3e4c-feb1-ea8b53767946@debian.org> <c2207cfc-5593-4e36-2910-2b043ef25f9f@debian.org> <a7be89f7-8e49-f32d-9d3c-5c502538fc4f@debian.org> <CAB4XWXxOq7nNj-ucPVYfz1Gen=cT0N-U-zF5+=d8H6UMN2k4_g@mail.gmail.com> <5a41fe54-4f24-e3ae-0bd7-d73ce87d7f44@debian.org> <CAB4XWXyDCU=RCUtaJF=M0TMtrgthL585_Z6sdEnLWunvfeeciw@mail.gmail.com> <20191222105814.GA399004@espresso.pseudorandom.co.uk>
Xref	csiph.com linux.debian.maint.python:12193 linux.debian.devel.release:92920

Cross-posted to 2 groups.

Show key headers only | 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