Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


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

Re: Raising severity to serious for some Python 2 leaf packages with no Python 3 support upstream

Path csiph.com!3.us.feeder.erje.net!4.us.feeder.erje.net!feeder.erje.net!2.eu.feeder.erje.net!news2.arglkargh.de!news.mixmin.net!aioe.org!bofh.it!news.nic.it!robomod
From Ondrej Novy <novy@ondrej.org>
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 10:40:02 +0200
Message-ID <yR43w-yL-15@gated-at.bofh.it> (permalink)
References <yQZwR-64v-3@gated-at.bofh.it>
X-Original-To Thomas Goirand <zigo@debian.org>
X-Mailbox-Line From debian-python-request@lists.debian.org Mon Oct 14 08:39:08 2019
Old-Return-Path <ondrej.novy@gmail.com>
X-Amavis-Spam-Status No, score=-4.749 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=2, LDO_WHITELIST=-5, RCVD_IN_DNSWL_NONE=-0.0001] 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-vk1-xa32.google. - helo-domain: .google.) FROM/MX_MATCHES_HELO(DOMAIN)=-2; rate: -5.5
Dkim-Signature v=1; a=rsa-sha256; c=relaxed/relaxed; d=ondrej-org.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=tkdEfy/aZ7peuK0Tq047+qbmqS6A4qj49XNFQlymDJk=; b=RnCoM3iD27jmp2llINkAaJZSN6UQuyEr8LeDsM8J0R1O2X3+KCGyUjO8ro+hUGlIpu RwwlfxiPKKYr22W5vge3g5CH+RCqxMkIjqIg4waBKah1aZUKA8N5D0ZRxWVpTmg1FsUa AO3FhIyJENqpeFn761aOgq1a5I0SlQTyLONx52fsstq/xe6l48mxvxW+vA+3z9RU004l T7nX+/P44J8b73e25LY2QVQvLtsKbiNiVI5dmehhKIdeptLbUz60ep0atyz7RDsla3pE 7s1WBTF53u5nvufoHRd0IdJh0KJ8mmRDAnwmcZRAfz2vGxZA0XNAJrSlVeokPR/PTEaI 9JYA==
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=tkdEfy/aZ7peuK0Tq047+qbmqS6A4qj49XNFQlymDJk=; b=FlY5t4iGznb2d5A1zwcrOJyiQVkYfoJyfCUV1M3GU0WDdloUfD43+geSbRHp8npXDG r+btoPlXf5ML+zCLfi/b1qU/ppsGHkvYu8wYJ/Z0v9eXInMqr4zE1ZxBUZTkxGRYn3nk AMtMBKKBDJdnY1IVz67LnzTvPyTSXLJH8un9LT6lTDuYeagV5RtH4XqV82MbXchxhaCX zOPE5sfvAhy2LMkKL6AEbb72muFi6QT3bkNJ64TUAeKf3JUwgaKtq/fR6MVm8kP1ZqI0 sTlMwIxZo0/GM96m9P4O85qwY6xa0ReffCtGl8oEVFQ6pdcuSnP4OJh1fymH87Yx1zL4 bheQ==
X-Gm-Message-State APjAAAW9Q4T5dwvu1lPlnatF16Fr36M3VcTs4q3BVHBxETrAZSiBd52G AUYWuzhcklTKq8BTCR5uZFgzYkO7EWAemF9wrjG6mGWL
X-Google-SMTP-Source APXvYqxffv0w0Jlve9XUPalVF7A3SkrbrG7yUrPbs0MVQSRgpOpegkGBmjVtqIAWOUcwKogA38wTqh9ceW7YXCQ1MVg=
X-Received by 2002:a1f:a613:: with SMTP id p19mr15064598vke.102.1571041282884; Mon, 14 Oct 2019 01:21:22 -0700 (PDT)
MIME-Version 1.0
Content-Type multipart/alternative; boundary="0000000000009808a40594da8dc6"
X-Mailing-List <debian-python@lists.debian.org> archive/latest/17434
List-ID <debian-python.lists.debian.org>
List-URL <https://lists.debian.org/debian-python/>
List-Archive https://lists.debian.org/msgid-search/CAOO6c=yWE2xnLbciExgsutrGAit8VP0DdZ-e1k-Ho+nUjL8hrw@mail.gmail.com
Approved robomod@news.nic.it
Lines 52
Organization linux.* mail to news gateway
Sender robomod@news.nic.it
X-Original-Cc debian-python <debian-python@lists.debian.org>
X-Original-Date Mon, 14 Oct 2019 10:21:12 +0200
X-Original-Message-ID <CAOO6c=yWE2xnLbciExgsutrGAit8VP0DdZ-e1k-Ho+nUjL8hrw@mail.gmail.com>
X-Original-References <90426bab-9b7e-468c-da1b-6815bd6e947f@debian.org>
Xref csiph.com linux.debian.maint.python:11886

Show key headers only | View raw


[Multipart message — attachments visible in raw view] - view raw

Hi,

po 14. 10. 2019 v 4:52 odesílatel Thomas Goirand <zigo@debian.org> napsal:

> 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.

But to do this correctly, we need release goal. Do we have one?

-- 
Best regards
 Ondřej Nový

Back to linux.debian.maint.python | Previous | Next — Next in thread | Find similar | Unroll thread


Thread

Re: Raising severity to serious for some Python 2 leaf packages with  no Python 3 support upstream Ondrej Novy <novy@ondrej.org> - 2019-10-14 10:40 +0200
  Re: Raising severity to serious for some Python 2 leaf packages with  no Python 3 support upstream Sandro Tosi <morph@debian.org> - 2019-10-14 16:00 +0200
    Re: Raising severity to serious for some Python 2 leaf packages with  no Python 3 support upstream Andrey Rahmatullin <wrar@debian.org> - 2019-10-14 16:30 +0200
    Re: Raising severity to serious for some Python 2 leaf packages with  no Python 3 support upstream Sandro Tosi <morph@debian.org> - 2019-10-15 17:10 +0200

csiph-web