* 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.
I may be able to prepare an updated version to upload as an NMU (i.e. it would be Debian version 1.13.0-0.1), but I can't take over maintaining this package long-term because I don't use it and am not familiar with it -- I only maintain a package that has it as a required build dependency. I also haven't maintained a library yet, but I've been in this situation of needing to upload a newer version of a library before so I might be able to figure out what's required to prepare an upload. It would be interesting to upload a new version as an NMU with the maintainer marked as <packa...@qa.debian.org> but strangely that seems to be what's called for here.
Feel free to ask if you have questions regarding maintaining a library. Cheers Jochen
signature.asc
Description: PGP signature
