Path: csiph.com!pasdenom.info!newsfeed.bofh.team!news.samoylyk.net!gothmog.csi.it!bofh.it!news.nic.it!robomod From: Thomas Ward Newsgroups: linux.debian.maint.python Subject: Re: [backintime] Advise about unresponsive DPM and new 1.5.6 release Date: Thu, 18 Dec 2025 04:40:01 +0100 Message-ID: References: X-Mailbox-Line: From debian-python-request@lists.debian.org Thu Dec 18 03:38:37 2025 Old-Return-Path: X-Amavis-Spam-Status: No, score=-3.858 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, HTML_MESSAGE=2, LDO_WHITELIST=-5, MURPHY_SCAM1=0.1, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SARE_LWSHORTT=1.24] autolearn=no autolearn_force=no X-Policyd-Weight: using cached result; rate: -5.5 X-Greylist: delayed 1258 seconds by postgrey-1.36 at bendel; Thu, 18 Dec 2025 03:38:17 UTC X-Forward-Email-ID: 6943723aa17553c9d9c026b6 X-Forward-Email-Sender: rfc822; teward@ubuntu.com, smtp.forwardemail.net, 121.127.44.73 X-Forward-Email-Version: 2.0.6 X-Forward-Email-Website: https://forwardemail.net X-Report-Abuse: abuse@forwardemail.net X-Report-Abuse-To: abuse@forwardemail.net Content-Type: multipart/alternative; boundary="------------x0O9GLjtr40yaQYEgOrFz4aA" MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Content-Language: en-US X-Mailing-List: archive/latest/23510 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/a8b92b62-52be-496a-b12c-b48fb31b178b@ubuntu.com Approved: robomod@news.nic.it Lines: 147 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Cc: Debian python X-Original-Date: Wed, 17 Dec 2025 22:17:13 -0500 X-Original-Message-ID: X-Original-References: <4737412.LvFx2qVVIh@soren-desktop> X-Original-X-Complaints-To: abuse@forwardemail.net Xref: csiph.com linux.debian.maint.python:17273 This is a multi-part message in MIME format. --------------x0O9GLjtr40yaQYEgOrFz4aA Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit On 2025-12-17 21:41, Soren Stoutner wrote: > 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 I am not willing to long term help with the package maintenance, but I can prepare an NMU that can be uploaded and sponsored that can contain your updated version for Unstable.  It will still need sponsored/reviewed as I am not a DD, but I would be willing to at least give the NMU route a shot to assist in the short term. (I have other obligations that prevent a long-term maintaining of a package). >> 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. Let me know if this is a route you would like me to explore, Christian. Thomas --------------x0O9GLjtr40yaQYEgOrFz4aA Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit
On 2025-12-17 21:41, Soren Stoutner wrote:
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
I am not willing to long term help with the package maintenance, but I can prepare an NMU that can be uploaded and sponsored that can contain your updated version for Unstable.  It will still need sponsored/reviewed as I am not a DD, but I would be willing to at least give the NMU route a shot to assist in the short term. (I have other obligations that prevent a long-term maintaining of a package). 

      

        
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.


    

    
Let me know if this is a route you would like me to explore,
      Christian.

    


    

    
Thomas

    

      

    

  


--------------x0O9GLjtr40yaQYEgOrFz4aA--