Re: Maintaining potentially orphaned packages in Debian Commons team

Richard Lewis <richard.lewis.debian-gM/[email protected]>
Newsgroups gmane.linux.debian.devel.general
Message-ID <[email protected]>
Andrey Rakhmatullin <[email protected]> writes:

> On Sat, Jun 06, 2026 at 05:12:30PM +0100, Steve McIntyre wrote:
>>>For clucene-core we have a maintainer who has not uploaded in nearly ten
>>>years, contact attempts that went unanswered, repeated NMUs, and pending
>>>fixes from contributors. Yet, as far as I understand, there is currently
>>>no established procedure that would allow the package to become formally
>>>orphaned without active involvement from the maintainer.
>>>
>>>This is exactly the gap I am trying to discuss. If we believes that such
>>>packages should become formally orphaned rather than move to Debian
>>>Commons, what is the practical path to achieve that?
>>
>>What am I missing here? This sounds like a classic example of
>>something that normally gets done with MIA processing.
>
> There were two maintainers, and only one is formally MIA. The other
> one, as Andreas wrote, "was asked about interest to become Maintainer
> four years ago with no response".


I must be missing something: surely this other maintainer should then be
removed from the package by the MIA team?
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.