Re: Suggestion for orphaning process (Was: Maintaining potentially orphaned packages in Debian Commons team)

Andrey Rakhmatullin <[email protected]>
Newsgroups gmane.linux.debian.devel.general
Message-ID <[email protected]>
On Mon, Jun 08, 2026 at 12:15:40PM -0400, Marvin Renich wrote:
>> OK, you do not consider Debian Commons part of the solution, and I can
>> understand the argument that Debian Commons should only be used when at
>> least one person explicitly wants to take ongoing responsibility for the
>> package.
>>
>> My reading of the current thread is that several people agree that
>> clucene-core appears to lack active maintenance, while there is less
>> agreement about the appropriate process to handle such packages. Since
>> the package does not seem to fit the usual MIA workflow, perhaps we
>> should discuss what criteria and procedure would be appropriate for
>> formal orphaning in such cases.
>
>I do not understand why clucene-core "does not seem to fit the usual MIA
>workflow", and I suspect that this is where others are also not
>following your logic.

I feel like the answer is "I don't want to wait some more years".

>You seem to be saying that there should be a way to orphan a package
>without either involving the MIA team or getting the blessing of the
>maintainer, and my question is "Why?"

I think this framing is useful. And think the answer is:

* In past several years the MIA team was reportedly nonexistent.
* When someone sees a package that has been clearly unmaintained for 
   years, a normal desire is to mark it as orphaned "now-ish" and not "in a 
   year or several".

>I think all of your "criteria" constitute unnecessary bureaucracy for a
>problem that already has enough bureaucracy.

It's replacing one kind of bureaucracy with another, simpler, one.

-- 
WBR, wRAR
signature.asc (application/pgp-signature, 894 B)
-----BEGIN PGP SIGNATURE-----

iQJhBAABCgBLFiEEtf6ieDcfC1EgtGkao+OWn23e7IYFAmom+qEtFIAAAAAAFQAP
cGthLWFkZHJlc3NAZ251cGcub3Jnd3JhckBkZWJpYW4ub3JnAAoJEKPjlp9t3uyG
ulAQAKaaSq/+c864ZQ7gWohst87h9fKJjTmcUWbeHAxqIhIMdsGM6Yrs9a2xCJ6Z
Z1NYztUy8Zl9r+U3P15mYgiAA64zmp+dz/zoXo2Nc2icsayba2P2oqVybe/mBOrs
4vxoJlq8/S5Of6itLgv/KpknGhYP/lYVz+Piz9oQSf7gZ2OPUaQ7UYBIRgfBpnGD
AuDtyxHRENJCbV2WFe0FWWudskqNGGcixiLVf+xHEHMh59pY8XkkqhPza5GByTFC
Hthd0vrqIkHSu4opQLIaRz5V91j39bCi9vCLMX37lE5yyArAabqn7dSZo9YQPchk
bbbMeT9x33n4+TV9gDMy1OulCBot0b7v/aB1gwwoka3ijR0+Xn85KMwuY8m9y9Bg
K31+WXV2AzdaKmvezhgAk3QEzO10vnNnEPBZFLQHDrd1oD+oFqAPbRqPuYPrnBR0
H8/dhKATGCLzf8rasjEDw6MKmM5uDe4BZBolPaH4KesrXVI7ENBdJ+J+EFYc3hUp
D4G+8vahc3FnCzkLKSBKU8ZYXV20pg+fPuZrF9/4iRphAt8H7x5L1g8aCE4TB0wh
4t8rZ6qaZMaxzzmDqhUf+CYVQR+RqQcrQSZdF4MiHRcY+AiHi6flzcyGUYF0BtW2
I6FqzcLXSniiK2J4QRvyGPTQS53w5EFHboYcARnFo6EafSFU
=/PEg
-----END PGP SIGNATURE-----
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.