On 03/08/2018 21:56, Michael Wild wrote:
I just tried to upload my new packages. The new python-bcrypt and
python-nacl went through, but the updated python-paramiko gives me below
error. Could it be because the existing version is not noarch? Calm sends
me below message.
Yes, that is the
On Thu, Aug 2, 2018 at 7:16 PM Michael Wild wrote:
> On Thu, 2 Aug 2018, 19:04 Marco Atzeri, wrote:
>
>> [...]
>>
>> Michael
>> you are now the maintainer for the 3 packages.
>>
>> Regards
>> Marco
>>
>> ---
>> Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
>>
On Thu, 2 Aug 2018, 19:04 Marco Atzeri, wrote:
> Am 30.07.2018 um 10:59 schrieb Marco Atzeri:
> > Am 23.07.2018 um 23:13 schrieb Yaakov Selkowitz:
> >> On Fri, 2018-07-20 at 13:15 +0200, Michael Wild wrote:
> >>> I would like to adopt the orphaned package python-paramiko. In order
> >>> to bring
Am 23.07.2018 um 23:13 schrieb Yaakov Selkowitz:
On Fri, 2018-07-20 at 13:15 +0200, Michael Wild wrote:
I would like to adopt the orphaned package python-paramiko. In order
to bring it to its current version, additional dependencies need to be
packaged, namely python-bcrypt and python-PyNaCl.
On Thu, Jul 26, 2018 at 3:15 PM Michael Wild wrote:
> On Wed, Jul 25, 2018 at 9:52 PM Yaakov Selkowitz
> wrote:
>
>> On Tue, 2018-07-24 at 10:17 +0200, Michael Wild wrote:
>> > Another question: if you look at the cygport file
>> >
>>
On Wed, Jul 25, 2018 at 9:52 PM Yaakov Selkowitz
wrote:
> 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
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
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
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
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
On Mon, 23 Jul 2018, 23:13 Yaakov Selkowitz, wrote:
> On Fri, 2018-07-20 at 13:15 +0200, Michael Wild wrote:
> > I would like to adopt the orphaned package python-paramiko. In order
> > to bring it to its current version, additional dependencies need to be
> > packaged, namely python-bcrypt and
On Fri, 2018-07-20 at 13:15 +0200, Michael Wild wrote:
> I would like to adopt the orphaned package python-paramiko. In order
> to bring it to its current version, additional dependencies need to be
> packaged, namely python-bcrypt and python-PyNaCl.
>
> Debian packages:
>
> *
12 matches
Mail list logo