How does a package become orphaned? (was Re: Attn maintainer: python-paramiko)

[Libor Ukropec]

Dne 05.12.2022 v 21:54 Jon Turney via Cygwin-apps napsal(a):
> On 01/12/2022 20:18, Libor Ukropec wrote:
>> Dne 01.12.2022 v 20:41 Jon Turney napsal(a):
>>> On 17/11/2022 10:24, Libor Ukropec wrote:
>>  >
>>  > If that's not what the desired outcome here, please let me know.
>>
>> I wanted that.
>>
>>>
>>> Sorry for taking so long over this.
>>>
>>> I guess somebody should ping Michael Wild to ask about the rest of his packages.
>> I already did that 29 days ago, no response yet
>> https://github.com/wildmichael/cygwin/issues/1
>>
>> The paramiko depends on python-bcrypt and python-nacl so I'd like to ask for their 
>> ownership too, otherwise the ownership for paramiko does not make sense.
> 
> I've given you maintainer-ship of these as well (Marco is a co-maintainer of python-bcrypt).

thanks, python-nacl already in playground, tests are passing.
I wanted to ask for ITA, but didn't find a time for it, I hope it is not a big problem 
from the process view and also the other developers.

> 
> I've run my ctm2git tool [1] to generate the packaging git repos for python-paramiko and 
> python-nacl with history, which I try to remember to do for package adoptions, when it 
> doesn't already exist. Let me know if you'd like those removed.
no need to remove, always good to have track of history from which it has derived
> 
> (I didn't run if for bcrypt in case Marco doesn't want that)
it seems it is not necessary, as bcrypt is the latest we can support (3.2.0) and Python 
3.9 is supported too.

python-paramiko seems to have more issues to solve, for now I'm disabling the python tests

Thank you,
Libor
> 
> [1] https://github.com/jon-turney/ctm2git (but it's totally janky, so you're better off 
> just asking me to run it :))
> 
>> If Michael Wild by any chance responds and still would like to maintain those packages, 
>> I'll be happy to return them :)
> 
>