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


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

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

Path csiph.com!news.dns-netz.com!news.freedyn.net!aioe.org!bofh.it!news.nic.it!robomod
From Craig Small <csmall@debian.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 Tue, 15 Oct 2019 05:00:02 +0200
Message-ID <yRle2-2VJ-7@gated-at.bofh.it> (permalink)
References <yQZwR-64v-3@gated-at.bofh.it> <yQZwR-64v-1@gated-at.bofh.it> <yRg4G-8ba-13@gated-at.bofh.it> <yRle2-2VJ-9@gated-at.bofh.it>
X-Mailbox-Line From debian-python-request@lists.debian.org Tue Oct 15 02:52:36 2019
Old-Return-Path <csmall@dropbear.xyz>
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 <CALy8Cw754-MWKdL-7wifQ8Mh9JwXmEMs+d+3jKbGFrasVrAHpg@mail.gmail.com>
Content-Type multipart/alternative; boundary="000000000000a6f3f20594ea12a5"
X-Mailing-List <debian-python@lists.debian.org> archive/latest/17449
List-ID <debian-python.lists.debian.org>
List-URL <https://lists.debian.org/debian-python/>
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 <debian-python@lists.debian.org>
X-Original-Date Tue, 15 Oct 2019 13:52:08 +1100
X-Original-Message-ID <CALy8Cw754-MWKdL-7wifQ8Mh9JwXmEMs+d+3jKbGFrasVrAHpg@mail.gmail.com>
X-Original-References <90426bab-9b7e-468c-da1b-6815bd6e947f@debian.org> <87zhi4gfil.fsf@DigitalMercury.dynalias.net> <CALy8Cw7TEvK=cuRVriAxz2nnYa7LYQJgvNa=XqnvVh1rkLJbBg@mail.gmail.com> <02f08d76-c0b7-79c6-ae68-6f82f6ed9dff@debian.org>
Xref csiph.com linux.debian.maint.python:11898

Show key headers only | View raw


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

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


>

Back to linux.debian.maint.python | Previous | Next — Previous in thread | 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 Nicholas D Steeves <nsteeves@gmail.com> - 2019-10-14 05:50 +0200
  Re: Raising severity to serious for some Python 2 leaf packages with  no Python 3 support upstream Neil Williams <codehelp@debian.org> - 2019-10-14 09:20 +0200
    Re: Raising severity to serious for some Python 2 leaf packages with  no Python 3 support upstream Gregor Riepl <onitake@gmail.com> - 2019-10-14 20:20 +0200
      Re: Raising severity to serious for some Python 2 leaf packages  with no Python 3 support upstream Neil Williams <codehelp@debian.org> - 2019-10-14 21:30 +0200
    Re: Raising severity to serious for some Python 2 leaf packages with  no Python 3 support upstream Gregor Riepl <onitake@gmail.com> - 2019-10-14 20:30 +0200
      Re: Raising severity to serious for some Python 2 leaf packages  with no Python 3 support upstream Neil Williams <codehelp@debian.org> - 2019-10-14 21:30 +0200
  Re: Raising severity to serious for some Python 2 leaf packages with  no Python 3 support upstream Craig Small <csmall@dropbear.xyz> - 2019-10-14 23:30 +0200
    Re: Raising severity to serious for some Python 2 leaf packages with  no Python 3 support upstream Craig Small <csmall@debian.org> - 2019-10-15 05:00 +0200
    Re: Raising severity to serious for some Python 2 leaf packages with  no Python 3 support upstream Craig Small <csmall@dropbear.xyz> - 2019-10-15 05:20 +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 19:10 +0200

csiph-web