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

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

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

Path csiph.com!aioe.org!bofh.it!news.nic.it!robomod
From Craig Small <csmall@dropbear.xyz>
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 23:30:02 +0200
Message-ID <yRg4G-8ba-13@gated-at.bofh.it> (permalink)
References <yQZwR-64v-3@gated-at.bofh.it> <yQZwR-64v-1@gated-at.bofh.it>
X-Original-To Nicholas D Steeves <nsteeves@gmail.com>
X-Mailbox-Line From debian-python-request@lists.debian.org Mon Oct 14 21:24:09 2019
Old-Return-Path <csmall@dropbear.xyz>
X-Amavis-Spam-Status No, score=-4.501 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FROM_SUSPICIOUS_NTLD=0.499, 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: .dropbear. - helo: .mail-qk1-x730.google. - helo-domain: .google.) FROM/MX_MATCHES_HELO(DOMAIN)=-2; rate: -5.5
Dkim-Signature v=1; a=rsa-sha256; c=relaxed/relaxed; d=dropbear-xyz.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=i24goXYKMICcjNAQjapKDbVTrsaR8Nn/aNdoMrrVeYM=; b=z306XMmZkYbVOgj7MFNhpSQr4FxEH/Zbp+CDmYcGMFr1iuvpGPULuVLqRTJkfGsCh2 HxUNYbC0Zix43y+K72cFwwG4elLoHtBKdzhGFhz+jeT68HaDUv7D7U9ySJfeZRoZUFRS heKg1BTX6DLsE6uWJt2jOJbh3NiKmGPqqoT6dds3AFVzlS3skvmBsxLXJNWbiaCUW/TM 9puf49s+2Dgbf/+nCVP5FF6IXwXRXjIx+gXWcAutUYzv5r/h1BYW2Hgt1p3Mvcpf3Hw0 VXIaVOaEqRQvlHV8zzCa02VLiO9n04axZQyPBxbUZ7VTHOyaDqjWjCYNcCLMWnGTUMQ3 iclQ==
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=i24goXYKMICcjNAQjapKDbVTrsaR8Nn/aNdoMrrVeYM=; b=eBuxBO+6maBuw1StpHipR11ZK+fbD0db/BHkO5kNj1Ns0QPt2aP79xHwAYaWOWMJ03 6NM3G1wzbKFCm8b8KJyEPUgLs2rCAVz8w9qpuaMMQyqYIn3PyNn+lUeBmPSOyE6tr10f L4CS0hygKX2dPQZVNmrt8O73jF7lULgNeREgb4FVsUFVe9nb6RHnPfs2TCwiM0tO4TI0 MWePt6p7BJcQfJYoHChk3XaBTziCcIGdx1BogBbUxMRCMNwDo6ubB/oHWd+d95JRV+jN o70dXwVEzijusbGrVIvWSlCYmGYwDxfl6cUqvZZRlXDXjsBLG7T3T0t77sx7S2i6jM7v NZ1w==
X-Gm-Message-State APjAAAXyNzQEAVBe0njX/kuRIu0cq/YZUSIoII41m8t4fu30e5XL+eM1 +SGb0qUWrKFeUhggybR4TQwuZeQOv7DFNqlqtB+xUvCudH0=
X-Google-SMTP-Source APXvYqwHhP82ke7kBo7jX74TwvsTKbLCWWM1fFs5bopHFeEfOn52c0jnozzdrLtteXFojXr7QZ3wJGwvOtATb5T/LWo=
X-Received by 2002:a37:9c0a:: with SMTP id f10mr18289259qke.321.1571087157050; Mon, 14 Oct 2019 14:05:57 -0700 (PDT)
MIME-Version 1.0
Content-Type multipart/alternative; boundary="000000000000e85a050594e53b6e"
X-Mailing-List <debian-python@lists.debian.org> archive/latest/17446
List-ID <debian-python.lists.debian.org>
List-URL <https://lists.debian.org/debian-python/>
List-Archive https://lists.debian.org/msgid-search/CALy8Cw7TEvK=cuRVriAxz2nnYa7LYQJgvNa=XqnvVh1rkLJbBg@mail.gmail.com
Approved robomod@news.nic.it
Lines 37
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 08:05:44 +1100
X-Original-Message-ID <CALy8Cw7TEvK=cuRVriAxz2nnYa7LYQJgvNa=XqnvVh1rkLJbBg@mail.gmail.com>
X-Original-References <90426bab-9b7e-468c-da1b-6815bd6e947f@debian.org> <87zhi4gfil.fsf@DigitalMercury.dynalias.net>
Xref csiph.com linux.debian.maint.python:11897

Show key headers only | View raw

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

Hi All,
  Just be careful with the bugs severity on complicated packages. I totally
get the python only packages that produce a single binary, go for it for
those.

However consider the net-snmp python module. It's python 2 only and
upstream isn't changing it. In fact I am pretty sure they don't support it.

So get rid of it right? Yes, except that I cannot get a new version of
net-snmp into the archive due to a perl module bug.

So while I agree on the general approach, just look out for those multiple
binary type packages.

 - 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