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

[backintime] Advise about unresponsive DPM and new 1.5.6 release

Path	csiph.com!fu-berlin.de!bofh.it!news.nic.it!robomod
From	c.buhtz@posteo.jp
Newsgroups	linux.debian.maint.python
Subject	[backintime] Advise about unresponsive DPM and new 1.5.6 release
Date	Thu, 11 Dec 2025 13:10:02 +0100
Message-ID	<M0NEC-23X3-45@gated-at.bofh.it> (permalink)
X-Mailbox-Line	From debian-python-request@lists.debian.org Thu Dec 11 12:06:09 2025
Old-Return-Path	<c.buhtz@posteo.jp>
X-Amavis-Spam-Status	No, score=-9.308 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, LDO_WHITELIST=-5, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H2=-0.01, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
X-Policyd-Weight	NOT_IN_SBL_XBL_SPAMHAUS=-1.5 CL_IP_EQ_HELO_IP=-2 (check from: .posteo. - helo: .mout01.posteo. - helo-domain: .posteo.) FROM/MX_MATCHES_HELO(DOMAIN)=-2; rate: -5.5
MIME-Version	1.0
Reply-To	Debian python <debian-python@lists.debian.org>
Mail-Reply-To	Debian python <debian-python@lists.debian.org>
Content-Type	text/plain; charset=US-ASCII; format=flowed
Content-Transfer-Encoding	7bit
X-Mailing-List	<debian-python@lists.debian.org> archive/latest/23506
List-ID	<debian-python.lists.debian.org>
List-URL	<https://lists.debian.org/debian-python/>
List-Archive	https://lists.debian.org/msgid-search/e45e39fbb19ccfad6c7b66ac5c13a0d7@posteo.de
Approved	robomod@news.nic.it
Lines	28
Organization	linux.* mail to news gateway
Sender	robomod@news.nic.it
X-Original-Date	Thu, 11 Dec 2025 12:05:50 +0000
X-Original-Message-ID	<e45e39fbb19ccfad6c7b66ac5c13a0d7@posteo.de>
Xref	csiph.com linux.debian.maint.python:17270

Show key headers only | View raw

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.

Any advice?

Best regards,
Christian Buhtz


[1] -- <https://tracker.debian.org/pkg/backintime>
[2] -- <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1117254>

Back to linux.debian.maint.python | Previous | Next — 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