From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mxd-1-a75.seznam.cz (mxd-1-a75.seznam.cz [IPv6:2a02:598:128:8a00::1000:a75]) by sourceware.org (Postfix) with ESMTPS id 254AB38AA24D for ; Tue, 15 Nov 2022 18:47:57 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 254AB38AA24D Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=seznam.cz Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=seznam.cz Received: from email.seznam.cz by smtpc-mxd-74849b8976-qwg2j (smtpc-mxd-74849b8976-qwg2j [2a02:598:128:8a00::1000:a75]) id 681b4a83cd4d487c681b448d; Tue, 15 Nov 2022 19:47:47 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=seznam.cz; s=szn20221014; t=1668538068; bh=Cq4YWznSgzMkO2nTHFjRwxdDjx5YCBi/HdpG5xNuHnk=; h=Received:Message-ID:Date:MIME-Version:User-Agent:Subject:To: References:From:In-Reply-To:Content-Type: Content-Transfer-Encoding; b=BE+pXcGo27AeEFUOMGfCLdu1o9Rq+B9SfCktX2/9D8oE7plvu2G4XJqYHMSiNdcfl WTnoQAfPji7+SlJ0GD8bGWI+Ko/8mtQMySo1kDvzmZr4FKbxQs4g5OLj69dMH6zMdx bPIU9EBw7HDkO6k3q5N5QCnvGsEPuzKgvLF3M0flxPseIzGIIzfnFyC4ec2hKJ0ydj mbo9GVf4gw9jP8DfrBgr4etyRQHG225LfiTMqH2g7BS87+XpL1ee2dBKdETGOd6aTY +yGhhho4p1azqPMC0l7rQbRabue5UVfpbHfyv+Wd3+70NWVhAG/Q4tnOtXNA6wsBo9 sAPpChJ3XnaYg== Received: from [192.168.2.5] (brno.ccbr.com [77.240.178.2]) by email-relay12.ko.seznam.cz (Seznam SMTPD 1.3.140) with ESMTP; Tue, 15 Nov 2022 19:47:46 +0100 (CET) Message-ID: Date: Tue, 15 Nov 2022 19:47:34 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.4.2 Subject: Re: How does a package become orphaned? (was Re: Attn maintainer: python-paramiko) To: cygwin-apps@cygwin.com References: <3fdca14d-95fa-0398-46a9-6d5291ceae96@gmail.com> <0282d084-b2b2-132f-1e82-4159a4d1de05@gmail.com> <36a5d2b5-41f7-52a4-c95f-d9f2e4f12e96@dronecode.org.uk> From: Libor Ukropec In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-0.4 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM,JMQ_SPF_NEUTRAL,NICE_REPLY_A,RCVD_IN_SBL_CSS,SPF_HELO_NONE,SPF_PASS,TXREP autolearn=no autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: Dne 04.11.2022 v 14:05 Chad Dougherty napsal(a): > On 2022-11-04 08:34, Jon Turney wrote: >> The second is not so clear: A package is orphaned if it's maintainer >> is not responsive to queries as to if they still want to be the maintainer of the package. >> >> It's undefined how many times we should ping, or how long we should wait for a response, >> but I think that the ~10 months that's elapsed here is more than enough! >> > > If the prospective adopter is also proposing an update that addresses security > vulnerabilities in the old package, I suggest that that, and the severity and impact of > those vulnerabilities be factored into the timeout decision. > What I do not want to do is the violent take over, so I gave some time to the original owner of the python-paramiko to respond. I created a bug on github.com almost 2 weeks ago and so far no reaction: https://github.com/wildmichael/cygwin/issues/1 So I'd like to ask for ITA for his several packages, BUT: the cygport is executing in "src_test" some python tests that in the end requires some python packages not available as cygwin packages (typing_extensions, mock, pytest-mock, may be others). So should I a) remove the test? (this is not my preference) or b) specify/execute in the cygport `pip3 install pkg1 pkg2 ...` - I'd expect that executing any stuff in the cygport is not allowed (and I do not want to trigger 'misuse alarm') and additional question - how do I execute scallywag "before" the ITA is approved and git repo created? Can/should I use 'playground' branch for another package that I already maintain? I do not see guide on cygwin.com is explaining this. Thank you, Libor