Path: csiph.com!4.us.feeder.erje.net!2.eu.feeder.erje.net!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: Mattia Rizzolo Newsgroups: linux.debian.maint.python,linux.debian.devel.release Subject: Re: Severity bump script Date: Mon, 02 Dec 2019 23:40:02 +0100 Message-ID: References: X-Mailbox-Line: From debian-python-request@lists.debian.org Mon Dec 2 22:39:02 2019 Old-Return-Path: X-Amavis-Spam-Status: No, score=-4.531 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, FREEMAIL_FORGED_FROMDOMAIN=0.218, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, 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-ot1-f44.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=cDylQXVtmd1Rk1gIDnjdJ6xJxCF5uH5/wxBe0cte82Y=; b=reliTCZIWb/n4qIY8Qj8kcltM+RQSC3RiOoXCxezm9qODxjTSdHWtlEXnnTgJEE/8u 1dAio0+1h6vYxOSPC3ab+2O3mnXVwCo8HxNrRd6iOT/WANN8iD9PgArQ6htRe9ml6TCY IFUMRT+TCAUXHI5AMcW6DV0iVRIcKFnoLRqtstMEA3MaA36G3kZPBlZmyYIB5iK2oK3Y 2oBHp/CkxJpCcRtcjqanYhlhN7YIMVdyDFMdYjflOuOe819anhx7SDPeoDq/7UZtSVLD gXnLLXloToD3yxXcFf9HOknUcHPE89zFItFV7WaAHYkXLnK5QzDL3LMRaNV/j3gxyp9r /VGg== X-Gm-Message-State: APjAAAVoVFyQVyuR0R/hb3ZPRGST7ijySB8E3oPEEokOB4uq/DRGJtUa gOZsReBOL4l3YZHGT0SsWcO2SdUzrEA= X-Google-SMTP-Source: APXvYqzh3xlamV7GIG5YQ7lZ5QVbCFy2aaCsIQJWe2zo5LAI/QQE4hEuAX9UIV2qpcg5rsxZti7bag== X-Received: by 2002:a9d:7082:: with SMTP id l2mr1013579otj.213.1575326327040; Mon, 02 Dec 2019 14:38:47 -0800 (PST) X-Received: by 2002:a9d:7410:: with SMTP id n16mr1109303otk.23.1575326326091; Mon, 02 Dec 2019 14:38:46 -0800 (PST) MIME-Version: 1.0 X-Gmail-Original-Message-ID: Content-Type: multipart/alternative; boundary="000000000000127a1b0598c03e72" X-Mailing-List: archive/latest/17689 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/CAHKYmev4Wkiu3RJf+gF4rUTnp-V2e96_fyA55PFwN+EPmJx0fA@mail.gmail.com Approved: robomod@news.nic.it Lines: 63 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Cc: Sandro Tosi , Ondrej Novy , debian-python , Debian release team X-Original-Date: Mon, 2 Dec 2019 23:38:32 +0100 X-Original-Message-ID: X-Original-References: <349bb59d7f28ad6c70e567d9939b99f2f924d01a.camel@ondrej.org> <153751f7-2d80-3e4c-feb1-ea8b53767946@debian.org> Xref: csiph.com linux.debian.maint.python:12093 linux.debian.devel.release:92417 --000000000000127a1b0598c03e72 Content-Type: text/plain; charset="UTF-8" On Mon, 2 Dec 2019, 10:25 pm Paul Gevers, wrote: > Hi, > > On 02-12-2019 22:15, Sandro Tosi wrote: > > the blocks are only between py2removal packages, so if a package > > un-related to the py2removal effort > > depend/recomments/b-deps/autotest-triggers a py2removal *application*, > that > > is still considered a leaf package > > You'll fix that, right? Because why would the tree stop at Python? A > leaf package is a package without Depends/Build-Depends in Debian. Because the python2 removal is about python2. If you depend on a python2 package then the dependant application needs to likewise be dropped or updated, but it also is at the same time somewhat out of scope from "us". So it's either file py2removal bugs also against packages that don't depend on python, but just use an application that happens to use python2, or the current status quo. That's my take at least. Also, I am one of those that think we should be much more forceful, and the current situation looks just fine for me, so I might be biased. --000000000000127a1b0598c03e72 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Mon, 2 Dec 2019, 10:25 pm Paul Gevers, <elbrus@debian.org> wrote:
Hi,

On 02-12-2019 22:15, Sandro Tosi wrote:
> the blocks are only between py2removal packages, so if a package
> un-related to the py2removal effort
> depend/recomments/b-deps/autotest-triggers a py2removal *application*,= that
> is still considered a leaf package

You'll fix that, right? Because why would the tree stop at Python? A leaf package is a package without Depends/Build-Depends in Debian.

Because the = python2 removal is about python2.=C2=A0 If you depend on a python2 package = then the dependant application needs to likewise be dropped or updated, but= it also is at the same time somewhat out of scope from "us".

So it's either file py2= removal bugs also against packages that don't depend on python, but jus= t use an application that happens to use python2, or the current status quo= .
That's my take at least.

Also, I am one of those that think we should = be much more forceful, and the current situation looks just fine for me, so= I might be biased.
--000000000000127a1b0598c03e72--