Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #12087
| From | Paul Gevers <elbrus@debian.org> |
|---|---|
| Newsgroups | linux.debian.maint.python, linux.debian.devel.release |
| Subject | Re: Severity bump script |
| Date | 2019-12-02 20:30 +0100 |
| Message-ID | <z8Zyq-4iK-9@gated-at.bofh.it> (permalink) |
| References | <z1aAF-482-3@gated-at.bofh.it> <z1bGp-4LZ-5@gated-at.bofh.it> <z8Fgl-8ku-1@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Cross-posted to 2 groups.
[Multipart message — attachments visible in raw view] - view raw
Hi all, On 01-12-2019 22:45, Sandro Tosi wrote: > Paul, this is the thread i was talking about. > > you were copied in the original email: > https://lists.debian.org/debian-python/2019/10/msg00098.html > > if there is something the RT wants to discuss about this effort, > please do so here, not directly to me (i may be the mail address > sending those control commands, but the decision was taken here). I understand the drive to push for Python 2 removal and sympathize with it. The issue I had yesterday with the process is that "leaf" was wrongly defined, it was looking at Depends, instead of also including Build-Depends. I don't want to stand in the way of Python 2 removal, but as I said before, pulling packages out from underneath maintainers isn't pretty so needs to be done with proper notifications and care. An RC bug to ones own package is acceptable in my opinion as it is a clear discussion forum, and can be (temporarily) down-graded while the discussion is ongoing. Being notified about some other package that I not even need directly but is going to pull "my" package out of testing isn't a nice experience and should be avoided. Yes, that slows down the process, but there are people, emotions and all those irrational things involved. Paul
Back to linux.debian.maint.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Severity bump script Ondrej Novy <novy@ondrej.org> - 2019-11-11 07:50 +0100
Re: Severity bump script Sandro Tosi <morph@debian.org> - 2019-11-11 16:50 +0100
Re: Severity bump script Sandro Tosi <morph@debian.org> - 2019-11-15 01:20 +0100
Re: Severity bump script Dmitry Shachnev <mitya57@debian.org> - 2019-11-15 19:50 +0100
Re: Severity bump script Sandro Tosi <morph@debian.org> - 2019-11-16 04:10 +0100
Re: Severity bump script Ondrej Novy <novy@ondrej.org> - 2019-11-22 09:40 +0100
Re: Severity bump script Sandro Tosi <morph@debian.org> - 2019-11-22 22:30 +0100
Re: Severity bump script Ondrej Novy <novy@ondrej.org> - 2019-11-27 20:40 +0100
Re: Severity bump script Sandro Tosi <morph@debian.org> - 2019-11-28 04:20 +0100
Re: Severity bump script Ondrej Novy <novy@ondrej.org> - 2019-11-28 13:40 +0100
Re: Severity bump script Sandro Tosi <morph@debian.org> - 2019-11-28 19:10 +0100
Re: Severity bump script Ondrej Novy <novy@ondrej.org> - 2019-11-28 21:00 +0100
Re: Severity bump script Sandro Tosi <morph@debian.org> - 2019-12-01 22:50 +0100
Re: Severity bump script Paul Gevers <elbrus@debian.org> - 2019-12-02 20:30 +0100
Re: Severity bump script Paul Gevers <elbrus@debian.org> - 2019-12-02 20:40 +0100
Re: Severity bump script Sandro Tosi <morph@debian.org> - 2019-12-02 22:20 +0100
Re: Severity bump script Paul Gevers <elbrus@debian.org> - 2019-12-02 22:30 +0100
Re: Severity bump script Sandro Tosi <morph@debian.org> - 2019-12-02 22:50 +0100
Re: Severity bump script Mattia Rizzolo <mattia@debian.org> - 2019-12-02 23:40 +0100
Re: Severity bump script Ondrej Novy <novy@ondrej.org> - 2019-12-03 10:40 +0100
Re: Severity bump script Ondrej Novy <novy@ondrej.org> - 2019-12-02 21:00 +0100
Re: Severity bump script Matthias Klose <doko@debian.org> - 2019-12-03 13:30 +0100
Re: Severity bump script Paul Gevers <elbrus@debian.org> - 2019-12-05 12:10 +0100
Re: Severity bump script Sandro Tosi <morph@debian.org> - 2019-12-08 21:00 +0100
Proposal on how to proceed with Python 2 removal from bullseye Paul Gevers <elbrus@debian.org> - 2019-12-14 21:00 +0100
Re: Proposal on how to proceed with Python 2 removal from bullseye Sandro Tosi <morph@debian.org> - 2019-12-18 07:10 +0100
Re: Proposal on how to proceed with Python 2 removal from bullseye Simon McVittie <smcv@debian.org> - 2019-12-22 12:00 +0100
Re: Proposal on how to proceed with Python 2 removal from bullseye Sandro Tosi <morph@debian.org> - 2020-01-07 00:20 +0100
csiph-web