Path: csiph.com!news.mixmin.net!aioe.org!bofh.it!news.nic.it!robomod
From: c.buhtz@posteo.jp
Newsgroups: linux.debian.maint.python
Subject: Re: Python 3.11 for =?UTF-8?Q?bookworm=3F?=
Date: Tue, 13 Dec 2022 11:00:01 +0100
Message-ID: <FCaeR-alZR-11@gated-at.bofh.it>
References: <FC0Sf-agdq-21@gated-at.bofh.it> <FC9C9-alMw-1@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 Dec 13 09:58:18 2022
Old-Return-Path: <c.buhtz@posteo.jp>
X-Amavis-Spam-Status: No, score=-9.48 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, LDO_WHITELIST=-5, MURPHY_DRUGS_REL8=0.02, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham autolearn_force=no
X-Policyd-Weight: using cached result; rate: -5.5
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: quoted-printable
Mail-Followup-To: Debian Python <debian-python@lists.debian.org>
X-Mailing-List: <debian-python@lists.debian.org> archive/latest/20588
List-ID: <debian-python.lists.debian.org>
List-URL: <https://lists.debian.org/debian-python/>
List-Archive: https://lists.debian.org/msgid-search/4a7a4d174aaf4df2a518518b86e6be76@posteo.de
Approved: robomod@news.nic.it
Lines: 16
Organization: linux.* mail to news gateway
Sender: robomod@news.nic.it
X-Original-Date: Tue, 13 Dec 2022 09:57:57 +0000
X-Original-Message-ID: <4a7a4d174aaf4df2a518518b86e6be76@posteo.de>
X-Original-References: <CAM8zJQutSSUGjSRjK+jEzd6XMtMTFBrM6dPPKpUcbnexTKADSw@mail.gmail.com> <20221213091537.wovnxc44yzietsls@mail.gaussglocke.de>
Xref: csiph.com linux.debian.maint.python:14722

Am 13.12.2022 10:15 schrieb Timo R=C3=B6hling:
> 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=20
nose is unmaintained for years.

I understand that you cannot drop nose from Debian in the current=20
situation of a freeze in one months and so many dependencies.

But isn't there a Debian process/workflow to "warn" package maintainers=20
about an upcoming package drop of one of there dependend packages to put=20
some pressure into it? Looking into the list of over 200 packages I see=20
this also as a chance to clean out some other unmaintained (and maybe=20
not so important) packages from the Debian repo.