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

Soren Stoutner <[email protected]> Wed, 17 Dec 2025 19:41:03 -0700

Newsgroups	gmane.linux.debian.devel.python
Organization	Debian
Message-ID	<4737412.LvFx2qVVIh@soren-desktop>

On Thursday, December 11, 2025 5:05:50 AM Mountain Standard Time 
[email protected] 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
[email protected]

signature.asc (application/pgp-signature, 833 B)