Hello Jochen.
What I want to do is orphan the Poco package as an NMU and then do an
NMU of a new version -- in that order. It seems to be the right thing to
do for this situation. I had a brief discussion with [debian-qa] and was
given feedback that the plan seems reasonable:
https://lists.debian.org/debian-qa/2024/01/msg00006.html
The NMU uploads will go to a -delayed queue to allow stopping it or
increasing delay if there is an objection.
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.
Unfortunately that's not what I see. Feel free to add additional
information.
The last activity I've been able to find from Krzysztof was an upload of
clamfs 2020-01-10. For Poco the last activity from him is 2009. The Git
repository for Poco shows one commit 2009-08-30 and one package upload
2009-09-01. I find no email in [debian-devel] from him as far back as
2014. The Debian bug tracker last activity was January 2011 with one
email in Bug #500134.
Looking at his website, the first thing on the main page mentions
ClamFS. The clamfs package in Debian has him as the only listed
maintainer and the package has dropped out of Testing because of the
Poco library dropped and there as has been no response. Bug #679125 for
clamfs from 2012 has had no response.
I sent email to the Debian MIA team but have not yet heard back from
them. Assuming I can get contact with the MIA team and they start their
process, that will take about six months.
-- Chris
--
Chris Knadle
chris.kna...@coredump.us
Debian Developer
