Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #11903
| Path | csiph.com!aioe.org!bofh.it!news.nic.it!robomod |
|---|---|
| From | Sandro Tosi <morph@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 19:10:02 +0200 |
| Message-ID | <yRyuC-33b-15@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> <yRlxn-3i7-3@gated-at.bofh.it> <yRyuC-33b-17@gated-at.bofh.it> |
| X-Original-To | debian-python <debian-python@lists.debian.org> |
| X-Mailbox-Line | From debian-python-request@lists.debian.org Tue Oct 15 17:09:11 2019 |
| Old-Return-Path | <sandro.tosi@gmail.com> |
| X-Amavis-Spam-Status | No, score=-6.727 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, LDO_WHITELIST=-5, MURPHY_DRUGS_REL8=0.02, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001] autolearn=ham autolearn_force=no |
| X-Policyd-Weight | NOT_IN_SBL_XBL_SPAMHAUS=-1.5 CL_IP_EQ_HELO_IP=-2 (check from: .gmail. - helo: .mail-qt1-f169.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; bh=ywI89eRmZQ0xHQA6zGdEpwJhkS6i1QVfPHPQWpnz99g=; b=LcqX4Phgfh4mdRvJkIXjf349hINKKJ23rPyHJjA+8ntJp5s6pjloNR1TxtAV9X62jv Alah+7GxPMGZ8sEduCBHjcliI4byD90KS/r5Xc9f0+KB3u7UU7XPt8xB2WAuNyTrRDlA SMqQItcKdFfRv+Asb7iRL/PrYCbgpo691PGH6KX2fzp9EtUz8aHuZhjMXMDedMGwn5sr xtepVGWWhB7oNEdWb78p/uMXV+20uYSGvxVdhTp0JffojcFvaIWtDmrjap9tB32R+bZA 0qCaiiOoDVQBEahOu5Kt7Z4nnl68FxLE0oTiRWwMrgPpm94FelCDE94rQkir77iBRZIG vk2A== |
| X-Gm-Message-State | APjAAAVd6tNTqpWFfXKiB+4+1XN9z4vVT60Caa8vGH1YEcyjQ5N+bK3y j4hb/Y2IhNdU5DPQTHJIHxQs0WmcX7H0hJx5WKICu4JnVRM= |
| X-Google-SMTP-Source | APXvYqygpHxATKW4WATMIDTQc0sRrN5znInGM0svGqk9KofTPA4gGJxZuJTF8tfaNhU4zcfdL7fjdZPa5ijZ8iBNPxE= |
| X-Received | by 2002:ac8:2e31:: with SMTP id r46mr38779098qta.293.1571159335979; Tue, 15 Oct 2019 10:08:55 -0700 (PDT) |
| MIME-Version | 1.0 |
| Content-Type | text/plain; charset="UTF-8" |
| X-Mailing-List | <debian-python@lists.debian.org> archive/latest/17455 |
| List-ID | <debian-python.lists.debian.org> |
| List-URL | <https://lists.debian.org/debian-python/> |
| List-Archive | https://lists.debian.org/msgid-search/CAB4XWXzVog9G9UrJWu92TWV6AW+FaEB-HDOyR6_6HBdLW5yrYg@mail.gmail.com |
| Approved | robomod@news.nic.it |
| Lines | 31 |
| Organization | linux.* mail to news gateway |
| Sender | robomod@news.nic.it |
| X-Original-Date | Tue, 15 Oct 2019 13:08:29 -0400 |
| X-Original-Message-ID | <CAB4XWXzVog9G9UrJWu92TWV6AW+FaEB-HDOyR6_6HBdLW5yrYg@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> <CALy8Cw4iJvy4yw+3Q2+UZ+ROBu10-fv8eL8AemWquLFMQMXZYQ@mail.gmail.com> <24a50ef2-0cba-fe5c-bc6e-4a340968e8b6@debian.org> |
| Xref | csiph.com linux.debian.maint.python:11903 |
Show key headers only | View raw
On Tue, Oct 15, 2019 at 12:55 PM Thomas Goirand <zigo@debian.org> wrote: > > On 10/15/19 5:00 AM, Craig Small wrote: > > > > > > On Tue, 15 Oct. 2019, 1:04 pm Thomas Goirand, <zigo@debian.org > > <mailto: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. > > Hi Craing, > > I'm not sure if that helps, but here's a patch... :) did you test your patch? +- print "v1 snmpset result: ", res, "\n" ++ print9"v1 snmpset result: ", res, "\n") -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi G+: https://plus.google.com/u/0/+SandroTosi
Back to linux.debian.maint.python | Previous | Next — Previous in thread | Find similar | Unroll 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