Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

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

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

Show all headers | View raw

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

On Thursday, December 18, 2025 1:35:55 AM Mountain Standard Time 
c.buhtz@posteo.jp wrote:
> Hello Soren and Thomas,
> thank you very much for your feedback and kind words. Even this is
> somehow helpful for me and my mood.
> 
> In my understanding the DPT would take over the package but only if the
> current maintainer says OK to it.
> Anyway.

That isn’t actually correct.  The policy is that the Debian Packaging Team (or 
any team in Debian except for the QA team, which only handles packages that 
have been abandoned) does not maintain a package unless at least one human 
maintainer is listed by name in the Uploaders field.  That Uploader is the 
primary maintainer of the package.  The rest of the team is only a backup.

For example, see python-electrum-ecc, which has two uploaders:

https://tracker.debian.org/pkg/python-electrum-ecc

Or python-construct-classes with one uploader:

https://tracker.debian.org/pkg/python-construct-classes

backintime lists one Maintainer and two Uploaders.

https://tracker.debian.org/pkg/backintime

Based on what you have said I assume all three are inactive.  If someone wants 
to salvage the package, they can choose to move it under the Debian Python 
Team, but they must put themselves in the Uploaders field, which is a 
commitment for them to maintain it going forward.
 
> I also think that upstream maintainers shouldn't do Debian maintenance
> also. An upstream maintainer is IMHO not objective enough.
> But I also know this is not reality today. I can speak only for myself I
> shouldn't do both jobs. To risky to introduce or break things by
> accident.

I can respect that.  But I can tell you that in my personal case I am both the 
upstream developer and the Debian maintainer for Privacy Browser, and it has 
worked out well for the package.

-- 
Soren Stoutner
soren@debian.org

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