Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #11887
| 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 | 2019-10-14 16:00 +0200 |
| Message-ID | <yR93c-3CA-7@gated-at.bofh.it> (permalink) |
| References | <yQZwR-64v-3@gated-at.bofh.it> <yR43w-yL-15@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
>> But in both cases, it's going to take a very long time. Do we really >> want to get stuck on these packages for like forever, or would it feel >> ok to raise the severity to serious, so that the package gets >> auto-removed and then we can work on removing Python 2 from its >> dependencies? > > for me it's perfectly fine to rise severity to serious of all leaf packages with py2remove bug as soon as possible. And let's do it "automatically" everytime any package gets leaf state. i think it's a bit premature to raise severity to RC (we should also check with the release team): these bugs have been opened since just 2 months and a half, and the development cycle for bullseye started not longer before. there's still a lot of time. (and removing a py2 package from a leaf pkg takes 5 minutes, usually, so if everyone in this thread had done that instead of writing an email, we'd be down 5 bugs already :D ) I think it's also extremely premature (and just a bad idea in general) to consider breakage of reverse dependencies but just dropping py2 packages. the Release Team is extremely unhappy with this approach for dealing with the py2removal bugs, so let's not even consider that option. Regards, -- 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 | Next in thread | Find similar | Unroll thread
Re: Raising severity to serious for some Python 2 leaf packages with no Python 3 support upstream Ondrej Novy <novy@ondrej.org> - 2019-10-14 10:40 +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-14 16:00 +0200
Re: Raising severity to serious for some Python 2 leaf packages with no Python 3 support upstream Andrey Rahmatullin <wrar@debian.org> - 2019-10-14 16:30 +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 17:10 +0200
csiph-web