Path: csiph.com!fu-berlin.de!bofh.it!news.nic.it!robomod From: Soren Stoutner Newsgroups: linux.debian.maint.python Subject: Re: [src:backintime] Upload despite Hard Freeze (no response from maintainer/uploader) Date: Tue, 17 Jun 2025 23:20:01 +0200 Message-ID: References: X-Original-To: debian-python@lists.debian.org X-Mailbox-Line: From debian-python-request@lists.debian.org Tue Jun 17 21:18:58 2025 Old-Return-Path: X-Amavis-Spam-Status: No, score=-117.416 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DKIMWL_WL_HIGH=-2.907, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, LDO_WHITELIST=-5, PGPSIGNATURE=-5, RCVD_IN_DNSWL_MED=-2.3, UNPARSEABLE_RELAY=0.001, USER_IN_DKIM_WELCOMELIST=-0.01, USER_IN_DKIM_WHITELIST=-100] autolearn=ham autolearn_force=no Organization: Debian Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAFVBMVEWIg4F7bGiws7ReTkyy kYoXFRrd6/4yMA0PAAACaklEQVQ4y22TwXabMBBFJaPuNZGSNZZp1uhM6BpkJeu4VFk3bsL/f0Lf CHC6qHyOgbl68zTDoIwaVfh3tUopTUGpbFToDiFnY9IY2oMAZYMiS4R9SfbSXepSS5EcFAa/muIU aRj8mkoUqrEraFzhYegBmqig0LyCIyM8DAwPlpBqmJVYaD2UeWZ3abVjsqKIojg+hY4omsyIcNSi qIBM6jJWOveS6kvBeVvHJ+VYzJUW88RmA12UiBx3HEcUMRuzIZI6tBQovTrPclNB3AuUXoXvs0XY C3B2baJpW4Dn2ZpVMInCirkxoyhM1qpK5nFrO65QvCrCqql2DyPgvm94iMQz5/PmISuEotxQGMD5 M5G1N9CjXJ5HQH96BZG2xx6AzejYZccxT4Re3Zr4bPKkCcGcz5Or3dVEABkAUY/znnVcQVVkrXVU vomoEJFe7x4nQuaZmZELL6qnXZGIB5YV/Q2IogtSmyNybEcBX2+QCLOAQYm+gmoORUrYzV7dc6R2 T1WPm45oVEQqsjtoIovHyTmcyxMhVVxTqapomZyLlAmTKC9AmjgamXXGZo+epNrXO3wGGiPRHbKL FnMy2RRgRb1gzFXXGjhICp8wqaTtdtyQH6nWTfkatJvJJoUCbOjSC7wR9/naEVognxrOFdLh7Ugx QpA/0QT4pRV0+u2dqsXD5y9EBDjVAJS3ZZLxmZblgmsU8x7mBeCKg48Py7WU2IiH1epbEbC8K9Ms y0cpcySVUcdQVrBY+rEsv+XpYgFKXT8B3v2yATxv8fKK2EfC358tsIMLYqfD401xA0j1EY4P/wWf IbhlOWyBv4OQsywBM8MAAAAAAElFTkSuQmCC MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart159110930.7YDyUoj3Kj"; micalg="pgp-sha512"; protocol="application/pgp-signature" X-Debian-User: soren X-Mailing-List: archive/latest/23069 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/2838903.Nya5fj1elA@soren-desktop Approved: robomod@news.nic.it Lines: 133 Sender: robomod@news.nic.it X-Original-Cc: c.buhtz@posteo.jp X-Original-Date: Tue, 17 Jun 2025 14:18:30 -0700 X-Original-Message-ID: <2838903.Nya5fj1elA@soren-desktop> X-Original-References: <4bKKVr01S2z6tyB@submission01.posteo.de> Xref: csiph.com linux.debian.maint.python:16937 --nextPart159110930.7YDyUoj3Kj Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8"; protected-headers="v1" From: Soren Stoutner To: debian-python@lists.debian.org Cc: c.buhtz@posteo.jp Date: Tue, 17 Jun 2025 14:18:30 -0700 Message-ID: <2838903.Nya5fj1elA@soren-desktop> Organization: Debian In-Reply-To: MIME-Version: 1.0 On Monday, June 16, 2025 11:56:19=E2=80=AFPM Mountain Standard Time c.buhtz= @posteo.jp=20 wrote: > Hello Andrey, >=20 > Am 16.06.2025 23:29 schrieb Andrey Rakhmatullin: > > That's expected, so what did you want to know when you asked "how to > > proceed further"? >=20 > I just want to be sure that there is no other Debian-like process or > channel > where to put such requests in, e.g. a ticket against a pseudo-package or > something like this. It is not easy for outsiders like me. >=20 > So it seems this list was the correct place and there is no other > channel. > And I can do nothing else than waiting. >=20 > Thank you for the answers. > Regards, > Christian The thing you need to understand about Debian is that it has a strong packa= ge- ownership model. That means that very few things happen without the packag= e=20 maintainers being involved and other Debian Developers are reticent to step= on=20 the package maintainers=E2=80=99 toes. Typically, for the software I package, I try to develop strong relationship= s=20 with the upstream developers. If I were ever contacted by an upstream=20 developer stating that an important fix should be shipped in the Debian on = an=20 expedited schedule, I would do everything possible to make it happen. I do no know why you have not had this experience with the maintainers of y= our=20 package this time. Perhaps they are very busy and haven=E2=80=99t seen you= r=20 communications. Or perhaps they have lost interest in contributing to Debi= an. =20 Or perhaps they are ill. As far as I know, none of them have responded=20 negatively to your suggestion of an update. Debian has a couple of procedures for dealing with packages whose maintaine= rs=20 are absent or unresponsive. The least invasive is an NMU (Non-Maintainer=20 Upload). The most invasive is package Salvaging (becoming the new=20 maintainer). Both of these require extra steps and delayed time compared t= o=20 the maintainer updating the package. As stated earlier, Debian Developers tend to be fairly reticent to step on= =20 other developer=E2=80=99s toes. And, in addition, most are fairly busy and= don=E2=80=99t have=20 a lot of bandwidth to take on any new tasks. The result of this is that of= ten=20 a package has to languish for several years before someone else picks it up. As an upstream developer, you only have a few basic options when dealing wi= th=20 this unfavorable situation. 1. Do the Debian packaging yourself (that is what I personally do). As you= =20 already mentioned, Debian packaging is a surprisingly complicated task. It= =20 took me three months of reading documentation before I was ready to start=20 working on my first package, and another three months after that before I=20 could produce usable results (and years later I am still learning all types= of=20 new things about doing it well). 2. Wait for a response--which might or might not ever come--from those who= =20 have maintained the package in the past. 3. Wait for some other package maintainer to take over maintenance of the=20 package. None of these are ideal. The ideal would be that every package is maintain= ed=20 by an active and involved maintainer who responds in a timely manner to eve= ry=20 bug report and every upstream release. The ideal is also that Debian has a= =20 surplus of developers that have enough time to make sure that nothing falls= =20 through the cracks. I try to always be in the middle of mentoring one or t= wo=20 new developers to move us in that direction. =2D-=20 Soren Stoutner soren@debian.org --nextPart159110930.7YDyUoj3Kj Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part. Content-Transfer-Encoding: 7Bit -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEJKVN2yNUZnlcqOI+wufLJ66wtgMFAmhR26cACgkQwufLJ66w tgMd9Q/+PGNR2GyPDX6i+pPLhLojNfWeRXimIEKJsT3Rypo89u2mk0/vWcTLVMbr o97xM25qpjIhAGl1zkWwEvW15o7nYT4gxP8gIMd3KYMVpwHdlzqnqU8rTdaSgs4F UdvJIP/JG5LZVdhJWCmNYPSiVkImf2YQd8W3TfnhMsFZMpbHbctm8CF3rsb14T0a tiSYYXl0syW0Z9kTN3kJjwUmE8EEjB8u2xu+1cIDzymwyh6ZQ1QA3EwSnwhpQ0Jj +7ddJxUMgxi+Z5O1VNwedHVeGcNziq5rOVqVfMEy7PMHokUK2zThZukb1potmXRu 0XuJOEY+nLYZzGkC2HHN+d1nErGaZWmdPgkI0jKnD1dnLKt8DHJG6ky8JFxp4ABN vdETnk3fr79wyVQfxszTkKx8hy8efnlDxpfzTMThT2Wni6DiHf6BwYDGi7vqNV6+ VW1hcorylzxr8Y6AjO9xwKnfHGceceJTUa4NS5YL3zVZ6s/Eb0Zp4r+9XQfc8oUc IuJO2beNq5sUgGcyt5ua7oO/jo0TVyLtWRqv8Eg64Iwznvpl6BP6vBStCo+7kgk9 s7B9Wz2bo3bGdAX5+rwlpSgCyCkgRH5M/aL7jiUTD6aUpLy8HFtmfIRRCBP4DoM+ kndkxaDpEsSrhxiu4CWZ+3lQu3tKuGHi1UdCYZFPdmCGAvpD4Ks= =d+8P -----END PGP SIGNATURE----- --nextPart159110930.7YDyUoj3Kj--