Groups > linux.debian.maint.python > #17272

Re: [backintime] Advise about unresponsive DPM and new 1.5.6 release

Path	csiph.com!pasdenom.info!weretis.net!feeder8.news.weretis.net!news.samoylyk.net!gothmog.csi.it!bofh.it!news.nic.it!robomod
From	Soren Stoutner <soren@debian.org>
Newsgroups	linux.debian.maint.python
Subject	Re: [backintime] Advise about unresponsive DPM and new 1.5.6 release
Date	Thu, 18 Dec 2025 03:50:01 +0100
Message-ID	<M3cfv-3IPU-3@gated-at.bofh.it> (permalink)
References	<M0NEC-23X3-45@gated-at.bofh.it>
X-Mailbox-Line	From debian-python-request@lists.debian.org Thu Dec 18 02:41:34 2025
Old-Return-Path	<soren@debian.org>
X-Amavis-Spam-Status	No, score=-114.41 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, LDO_WHITELIST=-5, MURPHY_SCAM1=0.1, 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="nextPart2430286.ElGaqSPkdT"; micalg="pgp-sha512"; protocol="application/pgp-signature"
X-Debian-User	soren
X-Mailing-List	<debian-python@lists.debian.org> archive/latest/23509
List-ID	<debian-python.lists.debian.org>
List-URL	<https://lists.debian.org/debian-python/>
List-Archive	https://lists.debian.org/msgid-search/4737412.LvFx2qVVIh@soren-desktop
Approved	robomod@news.nic.it
Lines	92
Sender	robomod@news.nic.it
X-Original-Cc	Debian python <debian-python@lists.debian.org>
X-Original-Date	Wed, 17 Dec 2025 19:41:03 -0700
X-Original-Message-ID	<4737412.LvFx2qVVIh@soren-desktop>
X-Original-References	<e45e39fbb19ccfad6c7b66ac5c13a0d7@posteo.de>
Xref	csiph.com linux.debian.maint.python:17272

Show key headers only | View raw

[Multipart message — attachments visible in raw view] - view raw

On Thursday, December 11, 2025 5:05:50 AM Mountain Standard Time 
c.buhtz@posteo.jp wrote:
> Hello again,
> and sorry to bother all of you with this issue.
> 
> I am upstream maintainer of backintime [1]. My DPM (Jonathan Wiltshire,
> jmw) is unresponsive and does not react (for 3 months now) to my last
> hotfix release [2] and also not to emails. The other two "uploader"
> expressed to me that they won't be able to do more maintenance tasks on
> that package.
> 
> I don't know what to do. Not having an upload of this release would be
> fine for me, but only if I have a reasons. To give a reason some
> communication need to be done. And that is what jmw is missing.
> 
> I have this problem since I took over the upstream project in 2022. MIA
> is not an option because jmw manages to "react" (with upload but no
> answers) in a time span less then 6 months. The Debian Python Team also
> refuse to take over the package without jmw giving it away. The
> situation is frustrating because I do not know the reasons and there is
> no communication.

I don’t think the problem is that the Debian Python Team is refusing to take 
over the package.  I think the problem is that nobody has the interest in 
taking over the package.  (It is an important distinction when dealing with 
volunteer organizations.)

Debian has an established package salvaging procedure that you or anyone else 
is welcome to follow:

https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#package-salvaging

> Any advice?

I believe the last time you wrote about this problem I mentioned that the only 
way to make sure that a Debian package stays up-to-date is for there to be a 
willing volunteer who has the time and energy to make it happen.  As an 
upstream developer, that either happens if someone comes forward to do so, or 
if you do it yourself.

As the timely-update problem appears to be unresolved, my recommendation to 
you would be to maintain it yourself.  I would be happy to sponsor the upload 
if you salvage the package.

-- 
Soren Stoutner
soren@debian.org

Back to linux.debian.maint.python | Previous | Next — Previous in thread | Next in thread | Find similar

Thread

[backintime] Advise about unresponsive DPM and new 1.5.6 release c.buhtz@posteo.jp - 2025-12-11 13:10 +0100
  Re: [backintime] Advise about unresponsive DPM and new 1.5.6 release Soren Stoutner <soren@debian.org> - 2025-12-18 03:50 +0100
    Re: [backintime] Advise about unresponsive DPM and new 1.5.6 release Thomas Ward <teward@ubuntu.com> - 2025-12-18 04:40 +0100
      Re: [backintime] Advise about unresponsive DPM and new 1.5.6 release c.buhtz@posteo.jp - 2025-12-18 09:40 +0100
        Re: [backintime] Advise about unresponsive DPM and new 1.5.6 release Soren Stoutner <soren@debian.org> - 2025-12-19 01:40 +0100

csiph-web