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

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 2019-10-15 05:00 +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>
Organization linux.* mail to news gateway

Show all headers | 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