public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: "cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>,
	Libor Ukropec <ace@seznam.cz>
Subject: Re: How does a package become orphaned? (was Re: Attn maintainer: python-paramiko)
Date: Thu, 1 Dec 2022 19:41:37 +0000	[thread overview]
Message-ID: <4c729833-8293-48d4-1b6d-d9f58e4d5137@dronecode.org.uk> (raw)
In-Reply-To: <be310c0a-f31a-a194-c98d-b89b38230111@seznam.cz>

On 17/11/2022 10:24, Libor Ukropec wrote:
> Dne 16.11.2022 v 12:52 Thomas Wolff napsal(a):
>>
>>> 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
>> As a general comment, I'd like to point out that "almost 2 weeks" is 
>> even less than someone's holiday time may be...
> 
> See above in the thread - author did not react here on cygwin for 
> months. What I did, I've found the author on GitHub and contacted him 
> there as well.
> 
>  >>Jon Turney: 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!

Yeah, 10 months is not 2 weeks.

Libor, I've given you maintainer-ship of python-paramiko.

If that's not what the desired outcome here, please let me know.

Sorry for taking so long over this.

I guess somebody should ping Michael Wild to ask about the rest of his 
packages.

>>> 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')
> 
> Any advice to this?

I think BUILD_REQUIRES should include any src_test requirements.

I'll try to document that more clearly.

>>> 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.
> and this?

You can always use the 'playground' repository for any tests or experiments.


  parent reply	other threads:[~2022-12-01 19:41 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-23 22:17 Attn maintainer: python-paramiko Marco Atzeri
2022-01-27  4:18 ` Marco Atzeri
2022-11-02 20:04   ` Libor Ukropec
2022-11-04 12:34     ` How does a package become orphaned? (was Re: Attn maintainer: python-paramiko) Jon Turney
2022-11-04 13:05       ` Chad Dougherty
2022-11-15 18:47         ` Libor Ukropec
2022-11-16 11:52           ` Thomas Wolff
2022-11-17 10:24             ` Libor Ukropec
2022-11-17 18:32               ` Brian Inglis
2022-12-01 19:41               ` Jon Turney [this message]
2022-12-01 20:18                 ` Libor Ukropec
2022-12-02  8:20                   ` Marco Atzeri
2022-12-05 23:07                     ` Libor Ukropec
2022-12-05 20:54                   ` Jon Turney
2022-12-06  0:07                     ` Libor Ukropec
2022-12-01 19:41         ` Jon Turney
2022-12-01 20:02           ` Achim Gratz
2023-05-09 20:16           ` Trusted maintainers (was: Re: How does a package become orphaned? (was Re: Attn maintainer: python-paramiko)) Jon Turney
2023-05-11 13:57             ` Andrew Schulman
2023-05-13 10:18               ` Marco Atzeri
2023-05-30 13:39                 ` Andrew Schulman
2023-06-06  8:12                 ` Corinna Vinschen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4c729833-8293-48d4-1b6d-d9f58e4d5137@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=ace@seznam.cz \
    --cc=cygwin-apps@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).