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: Sandro Tosi Newsgroups: linux.debian.maint.python Subject: Re: Raising severity to serious for some Python 2 leaf packages with no Python 3 support upstream Date: Mon, 14 Oct 2019 16:00:02 +0200 Message-ID: References: X-Original-To: debian-python X-Mailbox-Line: From debian-python-request@lists.debian.org Mon Oct 14 13:55:00 2019 Old-Return-Path: X-Amavis-Spam-Status: No, score=-6.75 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, LDO_WHITELIST=-5, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001] autolearn=ham autolearn_force=no X-Policyd-Weight: using cached result; 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; bh=8XXgplpBEv2/pBhjQbn4P4TCuHi7ohkxN/iLNMnfD08=; b=lxuP7v6SRRqoVMCCyiz1Wwz40ZfFZ3EXz3WCpB1zVK+EC54cewFPN9ebT2WG2tGMe6 JP7HgcCJN0+VT6Yr4ptd9Y3I104+nWPPAQETB1KOfjca0eVPnATiAGoFcutuqVvb5QOe +Ovb5O3BhshdLN+M9JmZP+Y2Bq1arWl1ChUdGfEfCTnQEe2Xe25HkwvxgcWM1Z1k2Gmu LlWzqjY+xuEVD3dLpxB3sE/SpWjMRIfGikULD6pEveQMChqWwI5qV6Pd7mqNB+RcL1i9 l/x/OjXcNsNiZxcXrL15uyMmw/WqmEPBMqwq9Kw20r9B+k0pCwMGH6Zs07urCVLpwwsv 20BQ== X-Gm-Message-State: APjAAAWXFSfsj5bXyjz571x8pbTQJXNwVGdNUYRZsGh+Bi5i+MHnKl0q 0W3nHaTuOqwBDRugKaf/0CsWQyOyvYWqNAlXUVranpa8 X-Google-SMTP-Source: APXvYqxdEIFMPD1dZWsHB/rtJZV6WgN3+yImOEk1jlT0xE1asEZ2AIAE/N/XUqaoblGdlpBUvJq/q0fe6ZjZcSCkdZc= X-Received: by 2002:a37:f61d:: with SMTP id y29mr14208605qkj.338.1571061286059; Mon, 14 Oct 2019 06:54:46 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" X-Mailing-List: archive/latest/17436 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/CAB4XWXxed4BOwz--JpzqJH82HVwHbS5R=hZczqmXsfj4VU4w3g@mail.gmail.com Approved: robomod@news.nic.it Lines: 28 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Date: Mon, 14 Oct 2019 09:54:18 -0400 X-Original-Message-ID: X-Original-References: <90426bab-9b7e-468c-da1b-6815bd6e947f@debian.org> Xref: csiph.com linux.debian.maint.python:11887 >> But in both cases, it's going to take a very long time. Do we really >> want to get stuck on these packages for like forever, or would it feel >> ok to raise the severity to serious, so that the package gets >> auto-removed and then we can work on removing Python 2 from its >> dependencies? > > for me it's perfectly fine to rise severity to serious of all leaf packages with py2remove bug as soon as possible. And let's do it "automatically" everytime any package gets leaf state. i think it's a bit premature to raise severity to RC (we should also check with the release team): these bugs have been opened since just 2 months and a half, and the development cycle for bullseye started not longer before. there's still a lot of time. (and removing a py2 package from a leaf pkg takes 5 minutes, usually, so if everyone in this thread had done that instead of writing an email, we'd be down 5 bugs already :D ) I think it's also extremely premature (and just a bad idea in general) to consider breakage of reverse dependencies but just dropping py2 packages. the Release Team is extremely unhappy with this approach for dealing with the py2removal bugs, so let's not even consider that option. Regards, -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi G+: https://plus.google.com/u/0/+SandroTosi