public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Libor Ukropec <ace@seznam.cz>
To: cygwin-apps@cygwin.com
Subject: Re: Attn maintainer: python-paramiko
Date: Wed, 2 Nov 2022 21:04:54 +0100	[thread overview]
Message-ID: <b308e398-20b4-8e83-c81b-29f9f49bc71e@seznam.cz> (raw)
In-Reply-To: <0282d084-b2b2-132f-1e82-4159a4d1de05@gmail.com>

Hello Michael, Marco,

any update for paramiko and Python 3.9? I'd like to update duplicity that depends on the 
paramiko lib and because the default Python is 3.9 I hit the wall.

Also I do not see the paramiko in the GIT repositories 
(https://www.cygwin.com/git-cygwin-packages/?a=project_list;pf=git/cygwin-packages) nor 
the https://cygwin.com/packages/summary/python-paramiko-src.html does not mention the GIT 
repo at all.

Is the package orphaned? If yes, I'd be happy to take over. (btw how package becames 
orphaned?) I think the same case will be the python-nacl and python-bcrypt

Regards,
Libor

Dne 27.01.2022 v 5:18 Marco Atzeri napsal(a):
> On 23.01.2022 23:17, Marco Atzeri wrote:
>> Michael,
>>
>> can you please add the python39
>>
>> $ cygcheck -cd |grep paramiko
>> python36-paramiko                          2.7.2-0
>> python37-paramiko                          2.7.2-0
>> python38-paramiko                          2.7.2-0
>>
>> and please avoid the usage of revision 0
>>
>> Regards
>> Marco
> 
> Michael,
> let me know if I should upload for you
> 
> 
> 
> Regards
> Marco
> 


  reply	other threads:[~2022-11-02 20:05 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-23 22:17 Marco Atzeri
2022-01-27  4:18 ` Marco Atzeri
2022-11-02 20:04   ` Libor Ukropec [this message]
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
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=b308e398-20b4-8e83-c81b-29f9f49bc71e@seznam.cz \
    --to=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).