Path: csiph.com!news.dns-netz.com!news.freedyn.net!aioe.org!bofh.it!news.nic.it!robomod From: Craig Small Newsgroups: linux.debian.maint.python Subject: Re: Raising severity to serious for some Python 2 leaf packages with no Python 3 support upstream Date: Tue, 15 Oct 2019 05:00:02 +0200 Message-ID: References: X-Mailbox-Line: From debian-python-request@lists.debian.org Tue Oct 15 02:52:36 2019 Old-Return-Path: X-Amavis-Spam-Status: No, score=-4.253 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, FROM_SUSPICIOUS_NTLD=0.499, HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=2, LDO_WHITELIST=-5, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001] autolearn=no autolearn_force=no X-Policyd-Weight: NOT_IN_SBL_XBL_SPAMHAUS=-1.5 CL_IP_EQ_HELO_IP=-2 (check from: .dropbear. - helo: .mail-qk1-f181.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=lIaFgeg1YD2hHoG9wJrOkpuum0Nq4pKSq7Iq6Sq7wFw=; b=OwzpnL6p8i780M1W6XOFf48pAhqBGpGkDcHbGl7DZG7dvke8DzANckZTonXSYn688N EENJYB5irDIMXBEmub5QqIJ41uvbALWxBJtTkXspjnq1O7fJjeqczql2x3jzo06BrcDH 16WQnlZTUr4cLrxTByn+K6VxJDAgP/LEDJ3aQskX+gH9ux9fV8xZ3TB45PRLfBG3MmEF C8FvZBlyVO3+n5sm2oOPJSmORVB7DZUITnnSu/LKU8XHVFwdovfgYsDrAmD6ckL/eTI7 Huf8qFhf8bFVPgj4La/6ljXMC9Em4QjFOWjqJJE1qJ5KZEeoKbrZ7LpeY+1tFwxI1TvE vpUw== X-Gm-Message-State: APjAAAWqWBGAGAEIqPCESAsK0xr1X4sSC0t0vLYCyLKyLgLqiFp4w3AC fMo7KZyyQeHNfO8pQb0/z2OYKyNszOP8O/sA X-Google-SMTP-Source: APXvYqybIV1Q9Lzhg8uAi7wWTpEon1sr4ivW7E3ETNQPAdTLR93fxZm1YFOhoFGbuKN5mUtqS/7knQ== X-Received: by 2002:a37:9a0d:: with SMTP id c13mr33762770qke.93.1571107940314; Mon, 14 Oct 2019 19:52:20 -0700 (PDT) X-Received: by 2002:ac8:290f:: with SMTP id y15mr37070682qty.181.1571107939735; Mon, 14 Oct 2019 19:52:19 -0700 (PDT) MIME-Version: 1.0 X-Gmail-Original-Message-ID: Content-Type: multipart/alternative; boundary="000000000000a6f3f20594ea12a5" X-Mailing-List: archive/latest/17449 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/CALy8Cw754-MWKdL-7wifQ8Mh9JwXmEMs+d+3jKbGFrasVrAHpg@mail.gmail.com Approved: robomod@news.nic.it Lines: 59 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Cc: debian-python X-Original-Date: Tue, 15 Oct 2019 13:52:08 +1100 X-Original-Message-ID: X-Original-References: <90426bab-9b7e-468c-da1b-6815bd6e947f@debian.org> <87zhi4gfil.fsf@DigitalMercury.dynalias.net> <02f08d76-c0b7-79c6-ae68-6f82f6ed9dff@debian.org> Xref: csiph.com linux.debian.maint.python:11898 --000000000000a6f3f20594ea12a5 Content-Type: text/plain; charset="UTF-8" On Tue, 15 Oct. 2019, 1:04 pm Thomas Goirand, wrote: > > Either we don't have enough details about net-snmp, or you're trying to > push for not-valid-yet-another-exception. > It's more if a source package makes multiple binary packages, one of those being a python 2 package, and there are other temporary reasons why that python package cannot be updated yet. The perl problem has nothing to do with python, except that problem holds up the update of net-snmp. The goal is to fix the other problem and remove the python module, but it will take time possibly. I'm pretty sure net-snmp is not the only situation where the python binary package is one of the many from a single source. In fact these will probably be the problem ones because they're often a case of "make python bindings once then ignore" situation. - Craig > --000000000000a6f3f20594ea12a5 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Tue, 15 Oct. 2019, 1:04 pm Thomas Goirand, <zigo@debian.org> wrote:

Either we don't have enough details about net-snmp, or you're tryin= g to
push for not-valid-yet-another-exception.

It's more if a source package = makes multiple binary packages, one of those being a python 2 package, and = there are other temporary reasons why that python package cannot be updated= yet.

The perl problem h= as nothing to do with python, except that problem holds up the update of ne= t-snmp.=C2=A0 The goal is to fix the other problem and remove the python mo= dule, but it will take time possibly.

I'm pretty sure net-snmp is not the only situation where = the python binary package is one of the many from a single source.=C2=A0 In= fact these will probably be the problem ones because=C2=A0 they're oft= en a case of "make python bindings once then ignore" situation.

=C2=A0- Craig


--000000000000a6f3f20594ea12a5--