Package: developers-reference Severity: wishlist 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 `[email protected]` 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 -- System Information: Debian Release: forky/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386, armhf Kernel: Linux 7.0.12+deb14.1-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled developers-reference depends on no packages. Versions of packages developers-reference recommends: ii debian-policy 4.7.4.1 ii libjs-jquery 3.7.1+dfsg+~3.5.33-1 ii libjs-sphinxdoc 9.1.0-4 ii sensible-utils 0.0.26 ii sphinx-rtd-theme-common 3.1.0+dfsg-1 Versions of packages developers-reference suggests: ii chromium [www-browser] 149.0.7827.114-1 pn doc-base <none> ii firefox [www-browser] 151.0.4-1 ii firefox-esr [www-browser] 140.11.0esr-1 ii lynx [www-browser] 2.9.3-2 ii opera-stable [www-browser] 132.0.5905.73
