Path: csiph.com!aioe.org!bofh.it!news.nic.it!robomod From: Sandro Tosi 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: References: X-Original-To: Simon McVittie X-Mailbox-Line: From debian-python-request@lists.debian.org Mon Jan 6 23:15:35 2020 Old-Return-Path: 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: archive/latest/17802 List-ID: List-URL: 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 , debian-python , Debian release team X-Original-Date: Mon, 6 Jan 2020 18:14:53 -0500 X-Original-Message-ID: X-Original-References: <349bb59d7f28ad6c70e567d9939b99f2f924d01a.camel@ondrej.org> <153751f7-2d80-3e4c-feb1-ea8b53767946@debian.org> <5a41fe54-4f24-e3ae-0bd7-d73ce87d7f44@debian.org> <20191222105814.GA399004@espresso.pseudorandom.co.uk> Xref: csiph.com linux.debian.maint.python:12193 linux.debian.devel.release:92920 On Sun, Dec 22, 2019 at 5:58 AM Simon McVittie 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