#1146331 developers-reference: Document the procedure for adopting a pseudo-package

#1146331#5
Date:
2026-08-31 13:04:50 UTC
From:
To:
Sections 5.11.3 and 5.11.4 describe how to orphan/adopt a normal package[0],
but the procedure is different for a pseudo-package because there's no actual
package to edit.  Based on [1], I suggest adding a paragraph like this:

To adopt a pseudo-package, e-mail `debian-debbugs@lists.debian.org` and ask
them
to update their pseudo-packages.maintainers file.  Include the package name,
the name and e-mail address for the old and new maintainer, and a reason for
the
change.  Remember to CC the old maintainer on the e-mail.

I assume the above is correct based on the linked thread, but e.g. they might
prefer a different e-mail address.  I'll tell that thread about this bug,
so hopefully you should get a reply soon with any corrections.

[0] https://www.debian.org/doc/manuals/developers-
reference/pkgs.html#orphaning-a-package
[1] https://lists.debian.org/debian-www/2026/08/msg00088.html

#1146331#10
Date:
2026-08-31 13:26:10 UTC
From:
To:
This is just a terminology thing, but "adopting" somehow feels like
strange language here, because pseudo-packages are really more like
responsibilities that are assigned to teams for specialized situations.
Perhaps "change the maintainer of" rather than "adopt"?

owner@bugs.debian.org instead, please.  Otherwise this seems reasonable
to me.

Thanks,

#1146331#15
Date:
2026-08-31 15:31:12 UTC
From:
To:
yes

yes

seems reasonable to me too and thanks for your bug report with patch, Andrew.
An updated patch would be appreciated...

#1146331#20
Date:
2026-08-31 21:03:54 UTC
From:
To:
Here you go!

https://salsa.debian.org/debian/developers-reference/-/merge_requests/86

I made the changes above and put it all at the bottom of the "adopting"
section.  I'm fine using the term "change the maintainer" in the text, but
chose not to add a new "change the maintainer of a pseudo-package" section
because it seemed too clunky for such a rare edge case.