On Thursday, December 18, 2025 1:35:55 AM Mountain Standard Time [email protected] 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 [email protected]
signature.asc
Description: This is a digitally signed message part.
