Re: [ITA] cmake 3.12.0

2018-07-25 Thread Marco Atzeri
Am 26.07.2018 um 02:50 schrieb Tony Kelman: No, all I'm saying that there's a protocol for that.  The maintainer is supposed to monitor this list I do read the mailing list, but don't write to it very often - composing a plain-text email is overly complicated with the mobile email clients I use

Re: [ITA] cmake 3.12.0

2018-07-25 Thread Tony Kelman
> No, all I'm saying that there's a protocol for that.  The maintainer is > supposed to monitor this list I do read the mailing list, but don't write to it very often - composing a plain-text email is overly complicated with the mobile email clients I use most of the time, and I was traveling this

Re: [ITA/ITP] python-paramiko 2.4.1, python-bcrypt 3.1.4, python-PyNaCl 1.2.1

2018-07-25 Thread Yaakov Selkowitz
On Tue, 2018-07-24 at 10:17 +0200, Michael Wild wrote: > Another question: if you look at the cygport file > https://github.com/themiwi/cygwin/blob/master/python-paramiko/python-paramiko.cygport, > I jump through some hoops to get > /usr/share/doc/Cygwin/python{2,3}-paramiko.README generated from a

Re: How to package a Python script

2018-07-25 Thread Yaakov Selkowitz
On Wed, 2018-07-25 at 16:55 +0200, Michael Wild wrote: > How should I go about packaging a Python executable? Separate packages > for python2 and python3? Only one of them? If so, which? If for both, > is there any advice how to achieve this? I don't think that the > python-wheel.cygclass deals wit

How to package a Python script

2018-07-25 Thread Michael Wild
Dear all How should I go about packaging a Python executable? Separate packages for python2 and python3? Only one of them? If so, which? If for both, is there any advice how to achieve this? I don't think that the python-wheel.cygclass deals with scripts in /usr/bin/ as the docs say that scripts s

Re: [ITA/ITP] python-paramiko 2.4.1, python-bcrypt 3.1.4, python-PyNaCl 1.2.1

2018-07-25 Thread Michael Wild
On Wed, Jul 25, 2018 at 9:42 AM Marco Atzeri wrote: > Am 25.07.2018 um 09:25 schrieb Michael Wild: > > Dear all > > > > I uploaded new builds of python-nacl and python-paramiko to > > > https://www.dropbox.com/sh/a0ci3v176k2pslu/AACdPzzLadgbLcPukr7CcE3Qa?dl=0. > > > > BTW: Do I need a "good to go

Re: [ITA/ITP] python-paramiko 2.4.1, python-bcrypt 3.1.4, python-PyNaCl 1.2.1

2018-07-25 Thread Marco Atzeri
Am 25.07.2018 um 09:25 schrieb Michael Wild: Dear all I uploaded new builds of python-nacl and python-paramiko to https://www.dropbox.com/sh/a0ci3v176k2pslu/AACdPzzLadgbLcPukr7CcE3Qa?dl=0. BTW: Do I need a "good to go" or is it OK if I go ahead with uploading since I already maintain tmux and s

Re: [ITP] engauge 10.7.2

2018-07-25 Thread Corinna Vinschen
Hi Mark, On Jun 21 00:20, mark mitchell wrote: > I have moved the help documentation files, and also incorporated your > suggestions for the cygport file. The corrected versions are at > https://drive.google.com/drive/u/0/folders/0B5_zuEeNEicQY1U0dFRYWTZqblU. > Thanks! > > On Tue, Jun 19, 2018 at

Re: [ITA/ITP] python-paramiko 2.4.1, python-bcrypt 3.1.4, python-PyNaCl 1.2.1

2018-07-25 Thread Michael Wild
Dear all I uploaded new builds of python-nacl and python-paramiko to https://www.dropbox.com/sh/a0ci3v176k2pslu/AACdPzzLadgbLcPukr7CcE3Qa?dl=0. BTW: Do I need a "good to go" or is it OK if I go ahead with uploading since I already maintain tmux and ssh-pageant? Michael On Tue, Jul 24, 2018 at 1