On 1/5/24 07:30, Jochen Sprickerhof wrote:
* Chris Knadle <chris.kna...@coredump.us> [2024-01-02 16:53]:
The way to orphan a package is to do an upload and setting the
maintainer to be <packa...@qa.debian.org>. Until that's done the
package ends up in maintainership limbo. See the bottom of Policy
3.3, and Developer's Reference section 5.9.4.
Agreed but I think that is something for the Maintainer: to do, who
seems to be active in Debian, otherwise.
Normally, yes. But it also doesn't do to have a maintainer that doesn't
communicate concerning a package; that's the #1 responsibility a package
maintainer has.
The situation with Poco clearly fits the criteria for when "salvaging" a
package is needed:
https://wiki.debian.org/PackageSalvaging
The RC bug for Poco is holding back the following list of source
packages from migrating: clickhouse, clamfs, gm-assistant, gpsshogi, mumble.
Feel free to ask if you have questions regarding maintaining a library.
The main thing I'd like to understand is how to do coordinate the
transition (i.e. the release) with the Release Team. I found some hints
about that here:
https://www.debian.org/doc/manuals/debmake-doc/ch05.en.html#lib-trans
--
Chris Knadle
chris.kna...@coredump.us
