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

Re: Discussing next steps for the Python2 removal

Path	csiph.com!3.eu.feeder.erje.net!feeder.erje.net!weretis.net!feeder7.news.weretis.net!news.mixmin.net!aioe.org!bofh.it!news.nic.it!robomod
From	Simon McVittie <smcv@debian.org>
Newsgroups	linux.debian.maint.python
Subject	Re: Discussing next steps for the Python2 removal
Date	Mon, 28 Oct 2019 11:00:01 +0100
Message-ID	<yW9YB-81f-7@gated-at.bofh.it> (permalink)
References	<yUWK5-2Yf-1@gated-at.bofh.it> <yV1Tr-6sS-11@gated-at.bofh.it> <yV5u2-9r-3@gated-at.bofh.it>
X-Original-To	debian-python@lists.debian.org
X-Mailbox-Line	From debian-python-request@lists.debian.org Mon Oct 28 09:56:41 2019
Old-Return-Path	<smcv@debian.org>
X-Amavis-Spam-Status	No, score=-9.3 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, LDO_WHITELIST=-5, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham autolearn_force=no
X-Policyd-Weight	using cached result; rate: -3.5
MIME-Version	1.0
Content-Type	text/plain; charset=iso-8859-1
Content-Disposition	inline
Content-Transfer-Encoding	8bit
User-Agent	Mutt/1.10.1 (2018-07-13)
X-Mailing-List	<debian-python@lists.debian.org> archive/latest/17517
List-ID	<debian-python.lists.debian.org>
List-URL	<https://lists.debian.org/debian-python/>
List-Archive	https://lists.debian.org/msgid-search/20191028095559.GA21485@espresso.pseudorandom.co.uk
Approved	robomod@news.nic.it
Lines	13
Organization	linux.* mail to news gateway
Sender	robomod@news.nic.it
X-Original-Date	Mon, 28 Oct 2019 09:56:00 +0000
X-Original-Message-ID	<20191028095559.GA21485@espresso.pseudorandom.co.uk>
X-Original-References	<CAB4XWXx5R3uEkLz7iLjGX-ZTZivWnKTVnJPk3NDQGYtBrO96Jg@mail.gmail.com> <a0d35ad7-4322-bb38-5e1d-6dbb97e33905@zoho.com> <CAOO6c=xPXj4vf31aWOU6riSsLtcD8Td78n6RxBfKyDna87tF6w@mail.gmail.com>
Xref	csiph.com linux.debian.maint.python:11956

Show key headers only | View raw

On Fri, 25 Oct 2019 at 12:38:11 +0200, Ondrej Novy wrote:
> this is not how autorm works. You can't remove from testing only one of two
> binary package from same source package. You are removing  package as a whole.
> 
> But maintainer can anytime fix that bug by removing py2 binary from source
> package, which is few minutes work.

The maintainer of a leaf package can do this in a few minutes at any
time, but library packages with many reverse-dependencies (for example
dbus-python) don't really have that option, so I hope using autorm for
library packages is not on the table at this stage?

    smcv

Thread

Discussing next steps for the Python2 removal Matthias Klose <doko@debian.org> - 2019-10-22 17:10 +0200
  Re: Discussing next steps for the Python2 removal Sandro Tosi <morph@debian.org> - 2019-10-22 17:50 +0200
    Re: Discussing next steps for the Python2 removal Sandro Tosi <morph@debian.org> - 2019-10-23 04:30 +0200
    Re: Discussing next steps for the Python2 removal Sandro Tosi <morph@debian.org> - 2019-11-27 03:20 +0100
  Re: Discussing next steps for the Python2 removal Paul Gevers <elbrus@debian.org> - 2019-10-22 20:50 +0200
  Re: Discussing next steps for the Python2 removal Ondrej Novy <novy@ondrej.org> - 2019-10-24 22:10 +0200
    Re: Discussing next steps for the Python2 removal Sandro Tosi <morph@debian.org> - 2019-10-25 03:40 +0200
    Re: Discussing next steps for the Python2 removal Sandro Tosi <morph@debian.org> - 2019-10-25 03:40 +0200
      Re: Discussing next steps for the Python2 removal "Rebecca N. Palmer" <rebecca_palmer@zoho.com> - 2019-10-25 09:10 +0200
        Re: Discussing next steps for the Python2 removal Ondrej Novy <novy@ondrej.org> - 2019-10-25 13:00 +0200
          Re: Discussing next steps for the Python2 removal Simon McVittie <smcv@debian.org> - 2019-10-28 11:00 +0100
            Re: Discussing next steps for the Python2 removal Ondrej Novy <novy@ondrej.org> - 2019-10-28 11:50 +0100
      Re: Discussing next steps for the Python2 removal Ondrej Novy <novy@ondrej.org> - 2019-10-25 13:00 +0200

csiph-web