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

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

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 Tue, 15 Oct 2019 05:20:01 +0200
Message-ID <yRlxn-3i7-3@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-Original-To Thomas Goirand <zigo@debian.org>
X-Mailbox-Line From debian-python-request@lists.debian.org Tue Oct 15 03:18:08 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-qt1-x82d.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=379PfhZCWV0e4qtkw5bq4F7L/nbNzZYRWnWm7BAtV9M=; b=Sjfa5amhvVJWlvagZjhw1gGUPuZ6UokWCT9QH1w2sJKakqW1Qyt48MvlnM8Rz7s1JL ys6IRBMEa4qtNsnG6iqJTa/GNfBQCaBH/SSt9Wcv3MiRa8YqmqF1fDVhqqDq5BI72Dio UjGkm8lkRwAwV3f4tXNvCZ/ONtS8vAlc2S8UqDBSTL5jW9LErX9r1dUQhq275rToHp3p 2YsjY0inDOjx7Cn2VlSNYAMPKtBm+Adm7RTna3G3XJJf5etPass/e42x1I61oHv8MOy+ 8IEmllex8HCVZEN3jRs8ehguJOkav5Gtrgpej1lF1vHy4ga5EocIFG+5t8qu4W79typt zXyA==
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=379PfhZCWV0e4qtkw5bq4F7L/nbNzZYRWnWm7BAtV9M=; b=rKbOaXresonn7hFkyhnEhpkZvS5TdW+lJ80ozELrhruEx2t7E/Zhzjia30/DENYacF Ms4IUQQiHqtmffkRToTAqsRmYFyCRcs5ot5n3i7B7SvvCAoOS3YZjjDVOlnF0goXkE0e EzPMXWKnn8Dfm+4lPD5paKavA7fU1ek3npwVne2G/jb49TEObMZgig5abR9a+Gni4CsE FJH5xN39BfBursqa29W0Cq3LnCVDA72fuj6sZYiVB/ZF4U8iilxWCSJhqyDTCzF3BRM9 GaRHeJ6kkz/qofC2BQquASPxm5twePnS95uuDWqumaP6O7pTdD9KRbXNmBPNfz4t6NlS NP/Q==
X-Gm-Message-State APjAAAXCZaJQAKAhxaMIVmmOlhpEPZ544F4DF1p1zdTCobOuPQvbHjRY ahQjpZ8QGxUDZjtOUJZQnF/DSxqAsX5xL4kEupTrmw==
X-Google-SMTP-Source APXvYqzyHQhPeLNtJAkbYYS/gAvermt8ia5qGEXNlpY8/+Qp3QUXjRpFZhg1PrbS1AJ6RGRkKxDZAYCV02U632Yiir8=
X-Received by 2002:ac8:2c09:: with SMTP id d9mr37094566qta.381.1571108457520; Mon, 14 Oct 2019 20:00:57 -0700 (PDT)
MIME-Version 1.0
Content-Type multipart/alternative; boundary="00000000000083b73f0594ea31a8"
X-Mailing-List <debian-python@lists.debian.org> archive/latest/17450
List-ID <debian-python.lists.debian.org>
List-URL <https://lists.debian.org/debian-python/>
List-Archive https://lists.debian.org/msgid-search/CALy8Cw4iJvy4yw+3Q2+UZ+ROBu10-fv8eL8AemWquLFMQMXZYQ@mail.gmail.com
Approved robomod@news.nic.it
Lines 30
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 14:00:45 +1100
X-Original-Message-ID <CALy8Cw4iJvy4yw+3Q2+UZ+ROBu10-fv8eL8AemWquLFMQMXZYQ@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:11899

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:

> Please re-read the excellent contribution from Neil Williams
> in this thread, and explain again why we have a special case... :)

I just did re-read it; especially about it's RC bugs not a total removal RM
so these packages will sit in unstable and not move into testing.

That works for me.

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