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

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

Path	csiph.com!2.eu.feeder.erje.net!3.eu.feeder.erje.net!feeder.erje.net!news.unit0.net!news.mixmin.net!aioe.org!bofh.it!news.nic.it!robomod
From	Simon McVittie <smcv@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	Sun, 22 Dec 2019 12:00:01 +0100
Message-ID	<zg77P-4N3-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>
X-Mailbox-Line	From debian-python-request@lists.debian.org Sun Dec 22 10:58:39 2019
Old-Return-Path	<smcv@debian.org>
X-Amavis-Spam-Status	No, score=-7.64 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, LDO_WHITELIST=-5, RCVD_IN_DNSWL_MED=-2.3, SARE_MLH_Stock10=1.66] autolearn=ham autolearn_force=no
X-Policyd-Weight	using cached result; rate: -3.5
MIME-Version	1.0
Content-Type	text/plain; charset=us-ascii
Content-Disposition	inline
X-Mailing-List	<debian-python@lists.debian.org> archive/latest/17769
List-ID	<debian-python.lists.debian.org>
List-URL	<https://lists.debian.org/debian-python/>
List-Archive	https://lists.debian.org/msgid-search/20191222105814.GA399004@espresso.pseudorandom.co.uk
Approved	robomod@news.nic.it
Lines	16
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	Sun, 22 Dec 2019 10:58:14 +0000
X-Original-Message-ID	<20191222105814.GA399004@espresso.pseudorandom.co.uk>
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>
Xref	csiph.com linux.debian.maint.python:12166 linux.debian.devel.release:92715

Cross-posted to 2 groups.

Show key headers only | View raw

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.

For now I've downgraded it back to normal.

Thanks,
    smcv

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