Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #14728
| From | Thomas Goirand <zigo@debian.org> |
|---|---|
| Newsgroups | linux.debian.maint.python |
| Subject | Re: Python 3.11 for bookworm? |
| Date | 2022-12-15 16:10 +0100 |
| Message-ID | <FCY1X-aR0U-5@gated-at.bofh.it> (permalink) |
| References | <FC0Sf-agdq-21@gated-at.bofh.it> <FC9C9-alMw-1@gated-at.bofh.it> <FCaeR-alZR-11@gated-at.bofh.it> |
| Organization | Debian |
On 12/13/22 10:57, c.buhtz@posteo.jp wrote: > Am 13.12.2022 10:15 schrieb Timo Röhling: >> One remaining problem is the unmaintained nose package >> [...] >> done some work patching up nose > > This question is just for my learning: Why is nose patched? Upstream > nose is unmaintained for years. > > I understand that you cannot drop nose from Debian in the current > situation of a freeze in one months and so many dependencies. > > But isn't there a Debian process/workflow to "warn" package maintainers > about an upcoming package drop of one of there dependend packages to put > some pressure into it? Looking into the list of over 200 packages I see > this also as a chance to clean out some other unmaintained (and maybe > not so important) packages from the Debian repo. It's unfortunately sometimes a bit harder than what one may think. Removing Nose from (build-)depends in some cases is hard, and IMO we started this process a way too late. Hopefully, Trixie will be nose-free! In the mean time, it is unfortunately my opinion that it's too late for Bookworm and that we must keep Nose for one more release. Cheers, Thomas Goirand (zigo)
Back to linux.debian.maint.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Python 3.11 for bookworm? Graham Inggs <ginggs@debian.org> - 2022-12-13 01:00 +0100
Re: Python 3.11 for bookworm? Andrius Merkys <merkys@debian.org> - 2022-12-13 08:20 +0100
Re: Python 3.11 for bookworm? Graham Inggs <ginggs@debian.org> - 2022-12-13 19:50 +0100
Re: Python 3.11 for bookworm? Timo Röhling <roehling@debian.org> - 2022-12-13 10:20 +0100
Re: Python 3.11 for bookworm? c.buhtz@posteo.jp - 2022-12-13 11:00 +0100
Re: Python 3.11 for bookworm? Dmitry Shachnev <mitya57@debian.org> - 2022-12-13 11:10 +0100
Re: Python 3.11 for bookworm? Thomas Goirand <zigo@debian.org> - 2022-12-15 16:10 +0100
Re: Python 3.11 for bookworm? Dmitry Shachnev <mitya57@debian.org> - 2022-12-15 17:20 +0100
Re: Python 3.11 for bookworm? Julian Gilbey <julian@d-and-j.net> - 2022-12-13 13:40 +0100
Re: Python 3.11 for bookworm? Thomas Goirand <zigo@debian.org> - 2022-12-15 16:20 +0100
Re: Python 3.11 for bookworm? Julian Gilbey <julian@d-and-j.net> - 2022-12-18 19:10 +0100
Re: Python 3.11 for bookworm? Julian Gilbey <julian@d-and-j.net> - 2022-12-19 10:50 +0100
Re: Python 3.11 for bookworm? Jochen Sprickerhof <jspricke@debian.org> - 2022-12-19 17:00 +0100
Re: Python 3.11 for bookworm? Julian Gilbey <julian@d-and-j.net> - 2022-12-19 21:30 +0100
Re: Python 3.11 for bookworm? Louis-Philippe Véronneau <pollo@debian.org> - 2022-12-13 17:10 +0100
Re: Python 3.11 for bookworm? Thomas Goirand <zigo@debian.org> - 2022-12-15 16:20 +0100
Re: Python 3.11 for bookworm? Thomas Goirand <zigo@debian.org> - 2022-12-16 10:50 +0100
csiph-web