Re: Transition tracker for rm python2 live

2019-07-23 Thread eamanu15 .
El mar., 23 de jul. de 2019 a la(s) 21:55, Drew Parsons (dpars...@debian.org)
escribió:

> Scott Kitterman wrote:
> > See https://release.debian.org/transitions/html/python2-rm.html
> >
> > The ones near the top of the stack (bottom of the page) are less likely
> > to
> > have rdepends that need to be sorted before action can be taken on
> > them.
>
>
> What should "success" or completion look like on the tracker?   I
> uploaded pyfttw (not python-fftw, which is a different package) hoping
> to get the first line of good green, but it has gone yellow rather than
> green.
>

mmm maybe yellow is ok?

>
> Drew
>
>

-- 
Arias Emmanuel
http://eamanu.com
Github/Gitlab; @eamanu
Debian: @eamanu-guest


Re: Python BoF and Python 2 removing

2019-07-22 Thread eamanu15 .
El lun., 22 de jul. de 2019 a la(s) 14:26, Ondrej Novy (n...@ondrej.org)
escribió:

> Hi,
>
> po 22. 7. 2019 v 14:23 odesílatel eamanu15 . 
> napsal:
>
>> I am debian contributor (not DM or DD) and I am helping on
>> py2 removing.
>>
>
> thanks for help.
>
> How is the process for us? We just push to salsas and send a email
>> for maintainer (ML?) or we upload the package to mentors?
>>
>
> process is same as any other sponsoring inside DPMT. Push it to Salsa and
> add sponsoring request to topic of IRC channel.
>
Great, I will write to IRC right now :-)


>
> --
> Best regards
>  Ondřej Nový
>
>

-- 
Arias Emmanuel
http://eamanu.com
Github/Gitlab; @eamanu
Debian: @eamanu-guest


Re: Python BoF and Python 2 removing

2019-07-22 Thread eamanu15 .
Hello Ondrej,

I am debian contributor (not DM or DD) and I am helping on
py2 removing.

How is the process for us? We just push to salsas and send a email
for maintainer (ML?) or we upload the package to mentors?

Cheers.

El lun., 22 de jul. de 2019 a la(s) 13:48, Ondrej Novy (n...@ondrej.org)
escribió:

> Hi,
>
> during Python BoF (yesterday) we made some progress about Python 2
> removal. We agreed this:
>
> Python 2 and PyPy support can be removed (drop binary package python-
> and/or pypy-) if it's leaf module package.
>
> Feel free to team upload this drop, but check reverse
> {build-,}dependencies first!
>
> Please DON'T remove Python2 applications and non-leaf packages now.
>
> This is team decision, so please DON'T blindly NMU non-team packages.
>
> Thanks.
>
> --
> Best regards
>  Ondřej Nový
>
>

-- 
Arias Emmanuel
http://eamanu.com
Github/Gitlab; @eamanu
Debian: @eamanu-guest


Re: Transition tracker for rm python2 live

2019-07-22 Thread eamanu15 .
Hello,

For a NMU for the PY2 remove I have just change the files on salsa and
letting know to the maintainer or, just writte here to get help on the
upload?

I am debian contributor not DM or DD

Cheers

El dom., 21 de jul. de 2019 a la(s) 17:23, Scott Kitterman (
deb...@kitterman.com) escribió:

> See https://release.debian.org/transitions/html/python2-rm.html
>
> The ones near the top of the stack (bottom of the page) are less likely to
> have rdepends that need to be sorted before action can be taken on them.
>
> Scott K
>
>
>

-- 
Arias Emmanuel
http://eamanu.com
Github/Gitlab; @eamanu
Debian: @eamanu-guest


Re: Plan for DebCamp

2019-07-16 Thread eamanu15 .
Hello Matthias

I'll be there from Wednesday.  My work time will splitted among Python 3.8
> and
> GCC 9 work ;)
>

So interest! I could help with python3.8


> Matthias
>


-- 
Arias Emmanuel
http://eamanu.com
Github/Gitlab; @eamanu
Debian: @eamanu-guest


Re: Ayuda para instalar python 3.7

2019-04-18 Thread eamanu15
El mié., 17 de abr. de 2019 18:24, Gregor Riepl 
escribió:

> > Para poder instalar py3.7 por default, tendrías que descargarlo desde
> > https://www.python.org/downloads/
> > y ejecutar ```./configure && make && make install```
>
> Alternatively, if you are patient, buster will become stable very soon.
> It comes with Python 3.7 by default.
>

That is a good alternative

>
>


Bug#925280: Fwd: Problems packaging JCC

2019-03-22 Thread eamanu15
Package: jcc
X-Debbugs-CC: cave...@debian.org, debian-python@lists.debian.org

Hello,

I am trying to package jcc to adopt it according to #922568.

But when I try to use dpkg-buildpackage I have the next error:

```
*h_missing -O--buildsystem=pybuild*
*   dh_dwz -O--buildsystem=pybuild*
*dwz -q --
debian/python-jcc/usr/lib/python2.7/dist-packages/jcc/_jcc2.x86_64-linux-gnu.so
*
*dh_dwz: dwz -q --
debian/python-jcc/usr/lib/python2.7/dist-packages/jcc/_jcc2.x86_64-linux-gnu.so
 returned exit code 1*
*make: *** [debian/rules:60: binary] Error 1*
*dpkg-buildpackage: error: debian/rules binary subprocess returned exit
status 2*
*debuild: fatal error at line 1182:*
*dpkg-buildpackage -us -uc -ui -i -I -i -I failed*

*gbp:error: 'debuild -i -I' failed: it exited with 29 *


*``` *I am a little confuse whit that error, I never see it and I don't
know what is happen.

Could any help me, please?

Regards

-- 
@eamanuhttps://eamanu.com



-- 
Arias Emmanuel
http://eamanu.com
Github/Gitlab; @eamanu
Debian: @eamanu-guest
-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEE3lnVbvHK7ir4q61+p3sXeEcY/EFAlyUuw0ACgkQ+p3sXeEc
Y/HwOg//SgmeW8qJgML7sKMCvyT0/rKDs7PoDCGDl4jdk7eo8eL21+5hb2qjVViN
cdQJjdB6CwGT4N4G8PMvgCbi+aG/Lmq/NEP/deNpnUG9POBOQf3Fz2Nchmc0Z3UP
HZTCHlx8tssGqgofYNFQBvJMRpujJCyRGlRdXKIrrNH78Se07+M/2RQJBsefvw27
6oZVRWi6gTpKINsAL7/FMH60WeOsIfmgKXiUeSetTtCtLSFJoMiUYtoOCWFPOJ0R
K6Q8A8f8cYJywlRto9bAdCGOuOSqDQzfthF069E6LSf1BJWurfBu0vaHS8IJq2IT
o0rDmwDTx9jsGzgACSZ93wJfkXeWhv6wyI0CwXx3U2mOW1pV7BkOV7IIMfa+cvgk
XVEG2FdAngbqSIqMUl+3itnqDap9YDY/vC14fqsGfRTYoD7nffqO7PE4os+NbmqF
/XRGpe+9GaFHgYuyj5hu/rFl8cNG2/kpJ+2hL+ErVHWsqw6fUoIXb8hcSKbH5pj/
IRjTLWzGHUpHt0OhYv5d8vqcd95LXIDraTlmsdIausjkqoHvN2lyWLuXVyIF3wX6
83TFIdhOofycxs0F9wSPe5RVPPHGz+60Ad8xJcrSHq/z77ShOZislUDo3oqscmiS
uubrp7JClLp7KgsDGjzWE0OnelGpQADliVXd7Hit71HExPdJWEc=
=KlAG
-END PGP SIGNATURE-


Re: Fwd: Is PyPi down ?

2019-01-13 Thread eamanu15
Hi,

hmmm no. PyPi is down right now.

Regards.

El dom., 13 de ene. de 2019 a la(s) 07:30, ant (a...@anthive.com) escribió:

> On Sun, Jan 13, 2019 at 12:01:12PM +0400, Jerome BENOIT wrote:
> ...
> > Hello, apparently
> >
> > https://pypi.debian.net/
> >
> > is down ? When will it come back ?
>
>   hello,
>
>   i looked at this this morning and it seems to
> be ok.
>
>   i did not try to upload a package but it worked
> for looking for a package and for downloading it.
>
>
>   ant
>
>

-- 
Arias Emmanuel
http://eamanu.com
Github/Gitlab; @eamanu
Debian: @eamanu-guest


Packages ready for upload

2018-12-12 Thread eamanu15
Hello everybody,

I have some packages ready for upload.

I push new release on salsa of:

  * impacket
  * PyGithub
  * python-scp

And I ITA this:

  * python-cassandra-driver. (I was working with Ondrej Novy on this)
  * pcapy

Please can somebody review it and help me to upload?

Thanks very much!
Regards!

-- 
Arias Emmanuel
http://eamanu.com
Github/Gitlab; @eamanu
Debian: @eamanu-guest


Re: pytest 3.9.3 in experimental

2018-11-08 Thread eamanu15
Roger That

El jue., 8 de nov. de 2018 a la(s) 06:09, Ondrej Novy (n...@ondrej.org)
escribió:

> Hi,
>
> I uploaded pytest version 3.9.3 into experimental. Please test it with
> your packages and report me any issues. If there will be no issues I will
> upload it into unstable after ~2 weeks from now.
>
> Thanks.
>
> --
> Best regards
>  Ondřej Nový
>
> Email: n...@ondrej.org
> PGP: 3D98 3C52 EB85 980C 46A5  6090 3573 1255 9D1E 064B
>
>

-- 
Arias Emmanuel
http://eamanu.com
Github/Gitlab; @eamanu
Debian: @eamanu-guest


Re: Joining DMPT and PAPT

2018-10-12 Thread eamanu15
Welcome!

El vie., 12 de oct. de 2018 a la(s) 16:57, Ondrej Novy (n...@ondrej.org)
escribió:

> Hi,
>
> st 3. 10. 2018 v 12:39 odesílatel Peter Pentchev 
> napsal:
>
>> I find myself doing more and more Python work on my own, so I thought
>> I might also contribute to the Debian packaging.  The first benefit
>> would be to bring my gitless package under the PAPT umbrella, but
>> I also have a couple of Python modules (some of which I've written
>> myself) as candidates for DPMT packaging.
>>
>
> welcome :)
>
> --
> Best regards
>  Ondřej Nový
>
> Email: n...@ondrej.org
> PGP: 3D98 3C52 EB85 980C 46A5  6090 3573 1255 9D1E 064B
>
>

-- 
Arias Emmanuel
http://eamanu.com
Github/Gitlab; @eamanu
Debian: @eamanu-guest


Re: joining PAPT

2018-10-12 Thread eamanu15
Welcome!

El vie., 12 de oct. de 2018 a la(s) 16:57, Ondrej Novy (n...@ondrej.org)
escribió:

> Hi,
>
> pá 12. 10. 2018 v 17:15 odesílatel Félix Sipma 
> napsal:
>
>> I'm already a member of DPMT, but I'd like to join PAPT to put some of the
>> packages I maintain there (todoman and khard, and I still plan to work on
>> these), and help in at least khal packaging.
>>
>
> welcome :)
>
> --
> Best regards
>  Ondřej Nový
>
> Email: n...@ondrej.org
> PGP: 3D98 3C52 EB85 980C 46A5  6090 3573 1255 9D1E 064B
>
>

-- 
Arias Emmanuel
http://eamanu.com
Github/Gitlab; @eamanu
Debian: @eamanu-guest


Re: Request to join DPMT & PAPT Team

2018-10-12 Thread eamanu15
Welcome! =D

El vie., 12 de oct. de 2018 a la(s) 04:12, Ondrej Novy (n...@ondrej.org)
escribió:

> Hi,
>
> so 6. 10. 2018 v 17:53 odesílatel Manas Kashyap <
> manaskashyapt...@gmail.com> napsal:
>
>> ... i am asked to join dpmt and papt team so i am requesting to take me
>> in the team .
>>
>
> welcome :)
>
> --
> Best regards
>  Ondřej Nový
>
> Email: n...@ondrej.org
> PGP: 3D98 3C52 EB85 980C 46A5  6090 3573 1255 9D1E 064B
>
>

-- 
Arias Emmanuel
http://eamanu.com
Github/Gitlab; @eamanu
Debian: @eamanu-guest


Re: Joining DMPT and PAPT

2018-10-12 Thread eamanu15
Welcome Joseph! =)

El vie., 12 de oct. de 2018 a la(s) 04:12, Ondrej Novy (n...@ondrej.org)
escribió:

> Hi,
>
> st 3. 10. 2018 v 5:51 odesílatel Joseph Herlant 
> napsal:
>
>> I'm already in there as aerostitch-guest but I just got my DD account
>> so I'd like to migrate my access to my new account: aerostitch.
>>
>
> done.
>
> --
> Best regards
>  Ondřej Nový
>
> Email: n...@ondrej.org
> PGP: 3D98 3C52 EB85 980C 46A5  6090 3573 1255 9D1E 064B
>
>

-- 
Arias Emmanuel
http://eamanu.com
Github/Gitlab; @eamanu
Debian: @eamanu-guest


Re: Joining DMPT and PAPT

2018-10-11 Thread eamanu15
Hi Joseph,

Be patient. Maybe the person responsible for doing that did not have time.

Cheers,

Arias Emmanuel
eamanu.com

El jue., 11 de oct. de 2018 20:52, Joseph Herlant 
escribió:

> Hi guys,
>
> Did you have the time to consider adding me to at least the DPMT team?
> There are a few of my packages that I'd like to update and I've
> already moved my gpg key to my new account.
>
> Thanks a lot for your help,
> Joseph
>
> On Tue, Oct 2, 2018 at 8:50 PM Joseph Herlant 
> wrote:
> >
> > Hi,
> >
> > I'm already in there as aerostitch-guest but I just got my DD account
> > so I'd like to migrate my access to my new account: aerostitch.
> >
> > Of course I have read and accept the Python policy (in addition to the
> > global Debian policy).
> >
> > Thanks for your help,
> > Joseph
>
>


Re: Joining DPMT

2018-09-18 Thread eamanu15
Welcome! !

Arias Emmanuel
eamanu.com

El mar., 18 de sept. de 2018 07:12, Ondrej Novy  escribió:

> Hi,
>
> pá 14. 9. 2018 v 16:09 odesílatel Mathieu Parent 
> napsal:
>
>> As per [1], I request to join the DPMT team to package python-pyvmomi
>> (See #860285).
>>
>
> welcome :)
>
> --
> Best regards
>  Ondřej Nový
>
> Email: n...@ondrej.org
> PGP: 3D98 3C52 EB85 980C 46A5  6090 3573 1255 9D1E 064B
>
>


Re: Request for joining the team to maintain the autosuspend Debian package

2018-09-18 Thread eamanu15
Welcome!

Arias Emmanuel
eamanu.com

El mar., 18 de sept. de 2018 07:09, Ondrej Novy  escribió:

> Hi,
>
> so 8. 9. 2018 v 14:27 odesílatel Johannes Wienke 
> napsal:
>
>> currently I am maintaining the Debian packaging for autosuspend [1] on
>> Github [2]. I'd like to move this to salsa and the Python team seems to
>> be a good fit for this application. Hence, I'd like to join the team
>> such that I can manage the project within the PAPT team on salsa.
>>
>
> welcome :)
>
> --
> Best regards
>  Ondřej Nový
>
> Email: n...@ondrej.org
> PGP: 3D98 3C52 EB85 980C 46A5  6090 3573 1255 9D1E 064B
>
>


Re: Request to join DPMT

2018-09-18 Thread eamanu15
Welcome!

Arias Emmanuel
eamanu.com

El mar., 18 de sept. de 2018 07:06, Ondrej Novy  escribió:

> Hi,
>
> út 11. 9. 2018 v 21:29 odesílatel Dr. Tobias Quathamer 
> napsal:
>
>> I'd like to join the Python modules team
>
>
> welcome :)
>
> --
> Best regards
>  Ondřej Nový
>
> Email: n...@ondrej.org
> PGP: 3D98 3C52 EB85 980C 46A5  6090 3573 1255 9D1E 064B
>
>


Re: How to disable tests for Python2 only?

2018-09-10 Thread eamanu15
> ... sorry to repeat myself but having team maintained packages on
> github is not inviting to others.  Is there any reason not to
> use Salsa?
>
+1

Regards!

-- 
Arias Emmanuel
http://eamanu.com
Github/Gitlab; @eamanu
Debian: @eamanu-guest


RFS: python-scp/0.11.0-1 [ITA]

2018-09-03 Thread eamanu15
Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "python-scp".

For some reason the uploaders field on mentors.d.o is Fabian Wolff, so I CC.

* Package name: python-scp
Version : 0.11.0-1
Upstream Author : James Bardin 
* URL : https://github.com/jbardin/scp.py
* License : LGPL-2.1+
Section : python

It builds those binary packages:

python-scp - scp module for  (Python 2)
python3-scp - scp module for paramiko (Python 3)

To access further information about this package, please visit the
following URL:

  https://mentors.debian.net/package/python-scp


Alternatively, one can download the package with dget using this command:

  dget -x
https://mentors.debian.net/debian/pool/main/p/python-scp/python-scp_0.11.0-1.dsc


Changes since the last upload:

[Ondřej Nový]
  * d/changelog: Remove trailing whitespaces
  * Fixed VCS URL (https)
  * d/control: Set Vcs-* to salsa.debian.org
  * d/copyright: Use https protocol in Format field
  * d/watch: Use https protocol
  * Convert git repository from git-dpm to gbp layout

  [Emmanuel Arias]
  * Add me to Uploaders field on d/control
  * Add to DPTM to Maintainer field on d/control
  * Adopt the package (Closes: #888215)
  * Update d/watch file
  * Update d/compat from 9 to 11
  * Update debhelper to >= 11 from d/control
  * Update Standards-Version from 3.9.6 to 4.1.4 on d/control
  * Add Testsuite autopkgtest-pkg-python on d/control
  * Add me to d/copyright

Regards,
Emmanuel Arias


Ask for files created for gpb buildpackages

2018-08-29 Thread eamanu15
Hello everybody,

Sorry if this question is solve on other mail.

When I build the package using gbp:

*gbp buildpackage --git-upstream-tag="v%(version)s" --git-ignore-new*

This create some other files/folder like this:
build/
debian/.debhelper/
debian/debhelper-build-stamp
debian/files
debian/python-*
debian/python3-*
*.egg-info/

This is correct? I can create a .gitignore file for them? or I have to push
this files/folder to salsa?

Thanks for your help
Regards!
-- 
Arias Emmanuel
http://eamanu.com
Github/Gitlab; @eamanu
Debian: @eamanu-guest


Re: RFS: pcapy/0.11.3-1 [ITA]

2018-08-29 Thread eamanu15
Hello Sergio,

I made the changes!

Thanks for your help
regards!
Emmanuel

El mié., 22 de ago. de 2018 a la(s) 01:59, Sergio Durigan Junior (
sergi...@debian.org) escribió:

> Hi Emmanuel,
>
> Sorry, you still have to fix a few things before the package is ready
> for upload.  We're almost there; don't give up!
>
> On Tuesday, August 21 2018, eamanu wrote:
>
> > No problem.  However, the "License:" still doesn't reflect the license
> >> of the software.  According to LICENSE:
> >>
> >>   We provide this software under a slightly modified version of the
> >>   Apache Software License. The only changes to the document were the
> >>   replacement of "Apache" with "Pcapy" and "Apache Software Foundation"
> >>   with "CORE Security Technologies". Feel free to compare the resulting
> >>   document to the official Apache license.
> >>
> >>   The `Apache Software License' is an Open Source Initiative Approved
> >>   License.
> >>
> >> Therefore, I think a better value for the field would be:
> >>
> >>   License: Apache with Pcapy modifications
> >>
> >
> > Ready!
>
> Thanks.  The "License:" must be the same in both places, though.  Here:
>
>   Files: *
>   Copyright (C) 2014 CORE Security Technologies .
>   License: Apache Software License with Pcapy modifications
>
> and here:
>
>   License: Apache with Pcapy modifications
>We provide this software under a slightly modified version of the
>...
>
> It's OK to use "Apache with Pcapy modifications" in both places.
>
> >> I see that the contributions under the debian/ directory are released
> >> under GPL-3+.  That's absolutely fine (I am a GPL advocate as well).
> >> However, I must warn you that the Debian patches will also be released
> >> under this license, which may be problematic if/when you decide to
> >> upstream them.  But I understand this is the current situation anyway.
> >> You may want to try to contact Arnaud Fontaine and ask him if he's OK
> >> with changing the license to Apache in the future.
> >>
> >
> > Ok. I will contact Arnaud Fontaine to ask about it. I think it's ok for
> > now. In the next release of package I can update this field.
>
> Great.  It's OK for now, indeed.
>
> > Thanks, but what you did is incomplete.  In order to create a new
> >> package, you have to create an entry for it on d/control.  What you did
> >> (add ${python3:Depends} to python-pcapy's Depends) is wrong because
> >> you're basically pulling Python 3 dependencies for a Python 2 package.
> >> Please have a look at other packages under them DPMT and check their
> >> d/control; you will find many examples of how to create Python 3
> >> packages.
> >>
> >
> > Ready!
>
> Thanks, that's better, but there are still a few things that need
> fixing.
>
> 1) It's a good practice to explicitly say if the package is a Python 2
> or Python 3 module.  We do that by suffixing the short description with
> "(Python X)" (where X is 2 or 2), and by appending "This package
> installs the library for Python X." to the long description.  Like this:
>
>   Package: python-pcapy
>   Architecture: any
>   Depends: ${python:Depends}, ${shlibs:Depends}, ${misc:Depends}
>   Recommends: python-impacket
>   Description: Python interface to the libpcap packet capture library
> (Python 2)
>Pcapy is a  Python extension module that interfaces  with the libpcap
>packet capture library.
>.
>Pcapy enables Python scripts to capture packets on the network. Pcapy
>is highly  effective when used in conjunction  with a packet-handling
>package such as Impacket, which is a collection of Python classes for
>constructing and dissecting network packets.
>.
>This package installs the library for Python 2.
>
> 2) You don't need to specify "Provides:".  Please remove them from both
> packages.
>
>
> As a last note, it seems that you forgot to push the "upstream" and
> "pristine-tar" branches, so I can't really build the package locally
> here.  Please do that.
>
> Thanks,
>
> --
> Sergio
> GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
> Please send encrypted e-mail if possible
> http://sergiodj.net/
>


-- 
Arias Emmanuel
http://eamanu.com
Github/Gitlab; @eamanu
Debian: @eamanu-guest


Re: Request to join DPMT and PAPT

2018-08-27 Thread eamanu15
Welcome !

El lun., 27 de ago. de 2018 a la(s) 03:51, Ondrej Novy (n...@ondrej.org)
escribió:

> Hi,
>
> čt 23. 8. 2018 v 18:16 odesílatel Nick Morrott 
> napsal:
>
>>  would like to join the Python Modules (DPMT) and Python Applications
>> (PAPT) teams,
>
>
> welcome :).
>
> --
> Best regards
>  Ondřej Nový
>
> Email: n...@ondrej.org
> PGP: 3D98 3C52 EB85 980C 46A5  6090 3573 1255 9D1E 064B
>
>

-- 
Arias Emmanuel
http://eamanu.com
Github/Gitlab; @eamanu
Debian: @eamanu-guest


Re: RFS: pcapy/0.11.3-1 [ITA]

2018-08-21 Thread eamanu15
Hello Sergio,



No problem.  However, the "License:" still doesn't reflect the license
> of the software.  According to LICENSE:
>
>   We provide this software under a slightly modified version of the
>   Apache Software License. The only changes to the document were the
>   replacement of "Apache" with "Pcapy" and "Apache Software Foundation"
>   with "CORE Security Technologies". Feel free to compare the resulting
>   document to the official Apache license.
>
>   The `Apache Software License' is an Open Source Initiative Approved
>   License.
>
> Therefore, I think a better value for the field would be:
>
>   License: Apache with Pcapy modifications
>

Ready!


> Also, please remove the "All rights reserved." text here:
>
>   Copyright (C) 2003-2011 CORE Security Technologies .
>
>All rights reserved.
>

Ready!


> Oh, and please fix the years.  Nowhere in the code I see "2003-2011".
> Doing a basic grep, I see that the year should be 2014.
>

Ready

>
> I see that the contributions under the debian/ directory are released
> under GPL-3+.  That's absolutely fine (I am a GPL advocate as well).
> However, I must warn you that the Debian patches will also be released
> under this license, which may be problematic if/when you decide to
> upstream them.  But I understand this is the current situation anyway.
> You may want to try to contact Arnaud Fontaine and ask him if he's OK
> with changing the license to Apache in the future.
>

Ok. I will contact Arnaud Fontaine to ask about it. I think it's ok for
now. In the next release of package I can update this field.

Thanks, but what you did is incomplete.  In order to create a new
> package, you have to create an entry for it on d/control.  What you did
> (add ${python3:Depends} to python-pcapy's Depends) is wrong because
> you're basically pulling Python 3 dependencies for a Python 2 package.
> Please have a look at other packages under them DPMT and check their
> d/control; you will find many examples of how to create Python 3
> packages.
>

Ready!

Thanks for your help!
Regards!

-- 
Arias Emmanuel
https://www.linkedin.com/in/emmanuel-arias-437a6a8a
http://eamanu.com


Re: git-dpm -> gbp conversion (mass-change) [phase 1 DONE]

2018-08-14 Thread eamanu15
Hi!

What's up with the page? https://wiki.debian.org/Python/GitPackagingPQ

Regards!


El dom., 12 de ago. de 2018 a la(s) 15:21, Dmitry Shachnev <
mity...@debian.org> escribió:

> Hi,
>
> On Sun, Aug 12, 2018 at 10:20:53AM -0300, eamanu15 wrote:
> > Hello Everybody!
> >
> > Its a good idea use gbp. Its more easy to use.
> >
> > Are there some step by step of the use?
>
> There was a link in Scott’s mail:
>
> https://wiki.debian.org/Python/GitPackagingPQ
>
> This page covers the most popular operations you would need to do.
>
> --
> Dmitry Shachnev
>
-- 
Arias Emmanuel
https://www.linkedin.com/in/emmanuel-arias-437a6a8a
http://eamanu.com


Re: git-dpm -> gbp conversion (mass-change) [phase 1 DONE]

2018-08-12 Thread eamanu15
Hello Everybody!

Its a good idea use gbp. Its more easy to use.

Are there some step by step of the use?

Regards!

El sáb., 11 de ago. de 2018 a la(s) 11:16, Scott Kitterman <
deb...@kitterman.com> escribió:

>
>
> On August 11, 2018 1:54:41 PM UTC, Ondrej Novy  wrote:
> >Hi,
> >
> >pá 10. 8. 2018 v 22:29 odesílatel Scott Kitterman
> >
> >napsal:
> >
> >> Thanks.  I'm glad more is going on than people arguing about what's
> >wrong
> >> with the tool we aren't going to use anymore.
> >>
> >
> >cool :).
> >
> >What branch layout did you use?
> >>
> >
> >I kept original branch names, renaming them is "phase 2".
>
> I hope you will stick with what's in the wiki:
>
> https://wiki.debian.org/Python/GitPackagingPQ#Git_Branch_Names
>
> That's what I've been following when I hand converted repositories of
> packages I was updating.
>
> Scott K
>
> --
Arias Emmanuel
https://www.linkedin.com/in/emmanuel-arias-437a6a8a
http://eamanu.com


Problems with uscan and PyPi.debian

2018-08-11 Thread eamanu15
Hello everybody!

I am trying to adopt python-scp package. When I download the code from
salsa, and then run uscan for download the las version I have the next
error:

uscan warn: In watchfile debian/watch, reading webpage
  https://pypi.debian.net/scp/ failed: 502 Bad Gateway

I had this error with other packages. There are some problems with
PyPi.debian? we have to use other repo to download the last upstream
version?

Regards!
-- 
Arias Emmanuel
https://www.linkedin.com/in/emmanuel-arias-437a6a8a
http://eamanu.com


Re: RFS: pcapy/0.11.3-1 [ITA]

2018-08-11 Thread eamanu15
Hello Sergio!

Thanks for your comments!

I fix the problems that you say me. Please check it

1) On d/copyright, the license specified for the project is wrong.
> According to the LICENSE file, the project is released under a slightly
> modified version of the Apache license.  This is something really
> important to get right, otherwise the ftp-masters will certainly reject
> the package.  You listed the license as being "GPL-2", but the text is
> clearly not GPL-2.
>
> Ohh!!! Sorry I saw the old d/copyright file to do this.

2) Still on d/copyright: as said above, the GPL-2 license is wrong.
> However, I think it's also important to mention that the license text is
> formatted in a strange/wrong manner.  You have text like this:
>
>  [...]
>  Redistribution and use in source  and binary forms, with or without
>modification, are permitted  provided that the following conditions
>are met:
>
>1. Redistributions  of  source   code  must  retain  the  above
>  [...]
>
> The correct format for d/copyright is to indent the text using 1 space,
> and to use . (dot) for blank lines.  Like this:
>
>  [...]
>  Redistribution and use in source  and binary forms, with or without
>  modification, are permitted  provided that the following conditions
>  are met:
>  .
>  1. Redistributions  of  source   code  must  retain  the  above
>  [...]
>


Ready!

>
> 3) The package uses a *really* old version of debhelper (version 5!).
> We're at version 11 already, so you should update both d/compat and
> d/control (i.e., depend on debhelp >= 11) to reflect that.
>

Ready!

>
> 4) You haven't addressed my comment about building a Python 3 package.
> IMO you should really do that; lintian will warn you if you don't.
>

Yes, I forgot do that! Sorry!

>
> 5) You haven't answered my question about why the package has "Suggests:
> doc-base".  It seems to be a relic from this very old debhelper; I think
> you can safely remove it.
>

Yes, I remove it. Since I do not have much knowledge about doc-base and why
it is there, I left it. But now is removed.

Thanks for your help!
Regards!

-- 
Arias Emmanuel
https://www.linkedin.com/in/emmanuel-arias-437a6a8a
http://eamanu.com


Re: RFS: pcapy/0.11.3-1 [ITA]

2018-08-10 Thread eamanu15
Hello Sergio,

I am really sorry for the delay.

I finish the update of pcapy package. I push the commit, but is on
UNRELEASED status.

Please, check if whole the things are ok, and then I will make change to
unstable status on d/changelog

Thanks!
Regards!

El lun., 2 de jul. de 2018 a la(s) 21:36, eamanu15 <
emmanuelaria...@gmail.com> escribió:

> Hello Sergio,
>
> Sorry for the delay in my response.
>
> In this week I will work on your reviews. When I fix the problems I will
> push to salsa and will let it know you.
>
> Thanks!
> Regards!
> Emmanuel
>
> El sáb., 16 de jun. de 2018 a la(s) 16:38, Sergio Durigan Junior <
> sergi...@debian.org> escribió:
>
>> Control: owner -1 !
>> Control: tags -1 + moreinfo
>>
>> On Thursday, June 07 2018, eamanu wrote:
>>
>> > Dear mentors,
>> >
>> > I am looking for a sponsor for my package "pcapy"
>> >
>> > * Package name: pcapy
>> > Version : 0.11.3-1
>> > Upstream Author : Core Security 
>> > * URL : https://github.com/CoreSecurity/pcapy
>> > * License : Apache Software License
>> > Section : python
>> >
>> > It builds those binary packages:
>> >
>> > python-pcapy - Python interface to the libpcap packet capture library
>> >
>> > To access further information about this package, please visit the
>> > following URL:
>> >
>> > https://mentors.debian.net/package/pcapy
>> >
>> >
>> > Alternatively, one can download the package with dget using this
>> command:
>> >
>> > dget -x
>> > https://mentors.debian.net/debian/pool/main/p/pcapy/pcapy_0.11.3-1.dsc
>> >
>> > More information about hello can be obtained from
>> https://www.example.com.
>> >
>> > Changes since the last upload:
>> >
>> > [ Jakub Wilk ]
>> > * Use canonical URIs for Vcs-* fields.
>> >
>> > [ Ondřej Nový ]
>> > * Fixed VCS URL (https)
>> > * d/control: Set Vcs-* to salsa.debian.org
>> > * d/changelog: Remove trailing whitespaces
>> > * Remove debian/pycompat, it's not used by any modern Python helper
>> >
>> > [ Emmanuel Arias ]
>> > * new upstream version
>> > * update d/watch to download correctly the last upstream version
>> > * update d/control to add Maintainer the DPMT
>> > * update d/control to add me to Uploaders field (Closes: #895787)
>> > * update debhelper on d/contorl from 5.0.37.2 to 11
>> > * update Standards-Version from 3.9.2 to 4.1.4 on d/control
>> > * add Testsuite: autopkgtest-pkg-python on d/control
>> > * update d/compat from 5 to 11
>> > * add to copyright file the debian files copyright
>>
>> Hi Emmanuel,
>>
>> Thanks for the package, and for your interest in adopting it!  The first
>> question I have is about the VCS.  I tried finding your commits on the
>> official Salsa repo, but wasn't able to.  Are you using any other
>> repository for that?  It's much easier to review the changes when
>> there's a repository, and I strongly suggest you use the official one
>> for the packaging.
>>
>> As for the review, here's what I'd like you to address:
>>
>> 1) d/copyright should follow DEP-5.  Take a look at:
>>
>>   https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
>>
>> and you'll be able to find instructions on the format of the file.  It
>> shouldn't be too hard for you to convert the existing file.
>>
>> 2) The package doesn't need CDBS anymore, so you can safely remove it
>> from the Build-Depends line.
>>
>> 3) The "Homepage" field can have a better URL:
>>
>>   https://www.coresecurity.com/corelabs-research/open-source-tools/pcapy
>>
>> 4) You should consider packaging a Python 3 package, as well as the
>> Python 2 you're already packaging (in which case you could probably
>> split the documentation part into its own package).  If Python 3 is not
>> supported, you should contact upstream and probably file a bug against
>> it.
>>
>> 5) Any reason why the package has "Suggests: doc-base"?
>>
>> 6) It's a good habit to export the PYBUILD_NAME variable (on d/rules):
>>
>>   export PYBUILD_NAME=pcapy
>>
>> This variable tells pybuild what's the name of your project.
>>
>> 7) It's a good idea to use (on d/rules):
>>
>>   export DEB_BUILD_MAINT_OPTIONS = hardening=+all
>>
>> since your package is building a shlib.
>>
>> 8) The package is installing the LICENSE file by default, but this is
>> not needed since we have the d/copyright file.  Therefore, it'd be good
>> if you could remove this file from the package.  You can do that by
>> e.g. overriding dh_auto_install and rm'ing the file there.
>>
>>
>> I think that's basically everything I've spotted.  Please let me know if
>> you need any help.
>>
>> Cheers,
>>
>> --
>> Sergio
>> GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
>> Please send encrypted e-mail if possible
>> http://sergiodj.net/
>>
> --
> Arias Emmanuel
> https://www.linkedin.com/in/emmanuel-arias-437a6a8a
> http://eamanu.com
>
-- 
Arias Emmanuel
https://www.linkedin.com/in/emmanuel-arias-437a6a8a
http://eamanu.com


Re: Bug#900368: RFS: pygithub/1.40a3-1 [ITP]

2018-07-05 Thread eamanu15
Great!

thanks for you help!

In next updates I will contact you.

Thanks
Regards

El jue., 5 de jul. de 2018 a la(s) 07:33, Dmitry Shachnev <
mity...@debian.org> escribió:

> On Wed, Jul 04, 2018 at 09:50:51PM -0300, eamanu15 wrote:
> > Hello Dmitry,
> >
> > I just pushed the update the package to Salsa. I pushed the PyGithub_1.40
> > version.
>
> Thanks! Uploaded after fixing debian/changelog.
>
> --
> Dmitry Shachnev
>
-- 
Arias Emmanuel
https://www.linkedin.com/in/emmanuel-arias-437a6a8a
http://eamanu.com


Re: Bug#900368: RFS: pygithub/1.40a3-1 [ITP]

2018-07-04 Thread eamanu15
Hello Dmitry,

I just pushed the update the package to Salsa. I pushed the PyGithub_1.40
version.

Regards!
Emmanuel

El mié., 4 de jul. de 2018 a la(s) 10:41, eamanu15 <
emmanuelaria...@gmail.com> escribió:

> Ok! Thanks !!!
>
> El mié., 4 de jul. de 2018 a la(s) 09:13, Dmitry Shachnev <
> mity...@debian.org> escribió:
>
>> On Wed, Jul 04, 2018 at 07:09:20AM -0300, eamanu15 wrote:
>> > Hello Dmitry,
>> >
>> > I have the fixes almost already, Just, I have a doubt in this point:
>> >
>> > > - When building in the current sid, I get Lintian warnings about
>> three files
>> > >   shipped in /usr/lib/python3.7/dist-packages/.
>> >
>> > To fix this problem I could add in the d/rules the next line:
>> >
>> > override_dh_auto_install:
>> > dh_auto_install
>> > find ./debian/python3-github/usr/lib/ -type f -name python3.*
>> -delete
>> >
>> > isn't?
>>
>> It is a directory, not a file. Also you need to do it after dh_python3
>> runs.
>> So better use this:
>>
>> override_dh_python3:
>> dh_python3
>> rm -rfv debian/python3-github/usr/lib/python3.*
>>
>> --
>> Dmitry Shachnev
>>
> --
> Arias Emmanuel
> https://www.linkedin.com/in/emmanuel-arias-437a6a8a
> http://eamanu.com
>
-- 
Arias Emmanuel
https://www.linkedin.com/in/emmanuel-arias-437a6a8a
http://eamanu.com


Re: Bug#900368: RFS: pygithub/1.40a3-1 [ITP]

2018-07-04 Thread eamanu15
Ok! Thanks !!!

El mié., 4 de jul. de 2018 a la(s) 09:13, Dmitry Shachnev <
mity...@debian.org> escribió:

> On Wed, Jul 04, 2018 at 07:09:20AM -0300, eamanu15 wrote:
> > Hello Dmitry,
> >
> > I have the fixes almost already, Just, I have a doubt in this point:
> >
> > > - When building in the current sid, I get Lintian warnings about three
> files
> > >   shipped in /usr/lib/python3.7/dist-packages/.
> >
> > To fix this problem I could add in the d/rules the next line:
> >
> > override_dh_auto_install:
> > dh_auto_install
> > find ./debian/python3-github/usr/lib/ -type f -name python3.* -delete
> >
> > isn't?
>
> It is a directory, not a file. Also you need to do it after dh_python3
> runs.
> So better use this:
>
> override_dh_python3:
> dh_python3
> rm -rfv debian/python3-github/usr/lib/python3.*
>
> --
> Dmitry Shachnev
>
-- 
Arias Emmanuel
https://www.linkedin.com/in/emmanuel-arias-437a6a8a
http://eamanu.com


Re: Bug#900368: RFS: pygithub/1.40a3-1 [ITP]

2018-07-04 Thread eamanu15
Hello Dmitry,

I have the fixes almost already, Just, I have a doubt in this point:

- When building in the current sid, I get Lintian warnings about three files
>   shipped in /usr/lib/python3.7/dist-packages/.
>
>   That probably happens because of output of 2to3 is slightly different in
>   Python 3.6 and 3.7 (e.g. files.items() vs. iter(files.items())), and
>   dh_python3 does not remove the file if it does not match.
>
>   I would recommend removing debian/python3-github/usr/lib/python3.*
> manually
>   in debian/rules. Keeping debian-python@ in Cc in case someone has a
> better
>   idea.
>

To fix this problem I could add in the d/rules the next line:

override_dh_auto_install:
dh_auto_install
find ./debian/python3-github/usr/lib/ -type f -name python3.* -delete

isn't?

Regards!
Thanks!
Emmanuel
-- 
Arias Emmanuel
https://www.linkedin.com/in/emmanuel-arias-437a6a8a
http://eamanu.com


Re: Bug#900368: RFS: pygithub/1.40a3-1 [ITP]

2018-07-03 Thread eamanu15
Hello Dimitry,

Thanks for you email. I Will make the changes that you recommend.

I have a cuestion for you. When I update to the version 1.40, Do I merge
all the changelog entries, including 1.35-1 upload, isn't?

Thanks
Regards

Arias Emmanuel
eamanu.com


El mar., 3 de jul. de 2018 17:17, Dmitry Shachnev 
escribió:

> Control: merge 898416 898811 900368
>
> Hi Emmanuel!
>
> On Tue, May 29, 2018 at 12:35:25PM -0300, eamanu15 wrote:
> > Package: sponsorship-requests
> > Severity: normal
> >
> > Dear mentors,
> >
> > I am looking for a sponsor for my package "pygithub"
>
> Note that I am merging your three RFS bugs. If you want to ping, just reply
> to the existing bug, not file a new one.
>
> Here are my comments about your changes.
>
> - It would be nice if you based the repository on the existing Git
>   repository [1], rather than starting from scratch.
>
>   Also for new team repositories as this one, it is better to use Gbp-Pq
>   workflow as described in the team wiki [2].
>
> - Please merge the last three changelog entries, as 1.35-1 upload did not
>   happen.
>
> - When building in the current sid, I get Lintian warnings about three
> files
>   shipped in /usr/lib/python3.7/dist-packages/.
>
>   That probably happens because of output of 2to3 is slightly different in
>   Python 3.6 and 3.7 (e.g. files.items() vs. iter(files.items())), and
>   dh_python3 does not remove the file if it does not match.
>
>   I would recommend removing debian/python3-github/usr/lib/python3.*
> manually
>   in debian/rules. Keeping debian-python@ in Cc in case someone has a
> better
>   idea.
>
> - A new stable 1.40 release has been released on June 26th [3].
>   Can you update from alpha to the stable version?
>
>   Also please add uversionmangle to debian/watch (like here [4]), to make
> it
>   treat 1.40 as a higher version than 1.40aN.
>
> [1]:
> https://alioth-archive.debian.org/git/users/kaction-guest/pygithub.git.tar.xz
> [2]: https://wiki.debian.org/Python/GitPackagingPQ
> [3]: https://pypi.org/project/PyGithub/1.40/
> [4]: https://pypi.debian.net/PyGithub/watch
>
> --
> Dmitry Shachnev
>


Re: RFS: pcapy/0.11.3-1 [ITA]

2018-07-02 Thread eamanu15
Hello Sergio,

Sorry for the delay in my response.

In this week I will work on your reviews. When I fix the problems I will
push to salsa and will let it know you.

Thanks!
Regards!
Emmanuel

El sáb., 16 de jun. de 2018 a la(s) 16:38, Sergio Durigan Junior <
sergi...@debian.org> escribió:

> Control: owner -1 !
> Control: tags -1 + moreinfo
>
> On Thursday, June 07 2018, eamanu wrote:
>
> > Dear mentors,
> >
> > I am looking for a sponsor for my package "pcapy"
> >
> > * Package name: pcapy
> > Version : 0.11.3-1
> > Upstream Author : Core Security 
> > * URL : https://github.com/CoreSecurity/pcapy
> > * License : Apache Software License
> > Section : python
> >
> > It builds those binary packages:
> >
> > python-pcapy - Python interface to the libpcap packet capture library
> >
> > To access further information about this package, please visit the
> > following URL:
> >
> > https://mentors.debian.net/package/pcapy
> >
> >
> > Alternatively, one can download the package with dget using this command:
> >
> > dget -x
> > https://mentors.debian.net/debian/pool/main/p/pcapy/pcapy_0.11.3-1.dsc
> >
> > More information about hello can be obtained from
> https://www.example.com.
> >
> > Changes since the last upload:
> >
> > [ Jakub Wilk ]
> > * Use canonical URIs for Vcs-* fields.
> >
> > [ Ondřej Nový ]
> > * Fixed VCS URL (https)
> > * d/control: Set Vcs-* to salsa.debian.org
> > * d/changelog: Remove trailing whitespaces
> > * Remove debian/pycompat, it's not used by any modern Python helper
> >
> > [ Emmanuel Arias ]
> > * new upstream version
> > * update d/watch to download correctly the last upstream version
> > * update d/control to add Maintainer the DPMT
> > * update d/control to add me to Uploaders field (Closes: #895787)
> > * update debhelper on d/contorl from 5.0.37.2 to 11
> > * update Standards-Version from 3.9.2 to 4.1.4 on d/control
> > * add Testsuite: autopkgtest-pkg-python on d/control
> > * update d/compat from 5 to 11
> > * add to copyright file the debian files copyright
>
> Hi Emmanuel,
>
> Thanks for the package, and for your interest in adopting it!  The first
> question I have is about the VCS.  I tried finding your commits on the
> official Salsa repo, but wasn't able to.  Are you using any other
> repository for that?  It's much easier to review the changes when
> there's a repository, and I strongly suggest you use the official one
> for the packaging.
>
> As for the review, here's what I'd like you to address:
>
> 1) d/copyright should follow DEP-5.  Take a look at:
>
>   https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
>
> and you'll be able to find instructions on the format of the file.  It
> shouldn't be too hard for you to convert the existing file.
>
> 2) The package doesn't need CDBS anymore, so you can safely remove it
> from the Build-Depends line.
>
> 3) The "Homepage" field can have a better URL:
>
>   https://www.coresecurity.com/corelabs-research/open-source-tools/pcapy
>
> 4) You should consider packaging a Python 3 package, as well as the
> Python 2 you're already packaging (in which case you could probably
> split the documentation part into its own package).  If Python 3 is not
> supported, you should contact upstream and probably file a bug against
> it.
>
> 5) Any reason why the package has "Suggests: doc-base"?
>
> 6) It's a good habit to export the PYBUILD_NAME variable (on d/rules):
>
>   export PYBUILD_NAME=pcapy
>
> This variable tells pybuild what's the name of your project.
>
> 7) It's a good idea to use (on d/rules):
>
>   export DEB_BUILD_MAINT_OPTIONS = hardening=+all
>
> since your package is building a shlib.
>
> 8) The package is installing the LICENSE file by default, but this is
> not needed since we have the d/copyright file.  Therefore, it'd be good
> if you could remove this file from the package.  You can do that by
> e.g. overriding dh_auto_install and rm'ing the file there.
>
>
> I think that's basically everything I've spotted.  Please let me know if
> you need any help.
>
> Cheers,
>
> --
> Sergio
> GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
> Please send encrypted e-mail if possible
> http://sergiodj.net/
>
-- 
Arias Emmanuel
https://www.linkedin.com/in/emmanuel-arias-437a6a8a
http://eamanu.com


Re: [Python-modules-team] Bug#901621: src:python-gnutls: please support python3

2018-06-18 Thread eamanu15
El sáb., 16 de jun. de 2018 a la(s) 18:19, Mattia Rizzolo 
escribió:

> On Fri, Jun 15, 2018 at 04:08:19PM -0300, eamanu15 wrote:
> > Hello Daniel,
> >
> > I am available to work on maintain python-gnutls package.
> >
> > But this package is not in wnpp list. I don't know if a could make update
> > or maintain for python3.
> >
> > I copy on this mail to Debian-python list and the actual maintainer.
>
> The changelog doesn't know of any change done by Dan Pascu you CCed,
> so I'm not sure how you decided he was "the actual maintainer" :)
>
> Anyway, this package is maintained by DPMT, so you cou provide a patch
> for this bug and find a DPMT member to sponsor it.
>

Okas! Great! I will work with this package, and will search a sponsor.

thanks!
Regards!


>
> --
> regards,
> Mattia Rizzolo
>
> GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
> more about me:  https://mapreri.org : :'  :
> Launchpad user: https://launchpad.net/~mapreri  `. `'`
> Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-
>
-- 
Arias Emmanuel
https://www.linkedin.com/in/emmanuel-arias-437a6a8a
http://eamanu.com


Re: [Python-modules-team] Bug#901621: src:python-gnutls: please support python3

2018-06-15 Thread eamanu15
Hello Daniel,

I am available to work on maintain python-gnutls package.

But this package is not in wnpp list. I don't know if a could make update
or maintain for python3.

I copy on this mail to Debian-python list and the actual maintainer.

Regards!
Emmanuel

El vie., 15 de jun. de 2018 a la(s) 15:39, Daniel Kahn Gillmor <
d...@fifthhorseman.net> escribió:

> Package: src:python-gnutls
> Version: 3.0.0-1
> Severity: wishlist
>
> i want to be able to use gnutls with python3.  at the moment, the
> package appears to only be built for python2.  upstream doesn't seem
> to claim any incomaptibility fwict.  please support py3 with this
> package too!
>
> thanks for maintaining python-gnutls in debian,
>
>--dkg
>
> -- System Information:
> Debian Release: buster/sid
>   APT prefers testing-debug
>   APT policy: (500, 'testing-debug'), (500, 'testing'), (500,
> 'oldstable'), (200, 'unstable-debug'), (200, 'unstable'), (1,
> 'experimental-debug'), (1, 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 4.16.0-1-amd64 (SMP w/4 CPU cores)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
> LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
>
> ___
> Python-modules-team mailing list
> python-modules-t...@alioth-lists.debian.net
>
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team

-- 
Arias Emmanuel
https://www.linkedin.com/in/emmanuel-arias-437a6a8a
http://eamanu.com


RFS: pcapy/0.11.3-1 [ITA]

2018-06-07 Thread eamanu15
Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "pcapy"

* Package name: pcapy
Version : 0.11.3-1
Upstream Author : Core Security 
* URL : https://github.com/CoreSecurity/pcapy
* License : Apache Software License
Section : python

It builds those binary packages:

python-pcapy - Python interface to the libpcap packet capture library

To access further information about this package, please visit the
following URL:

https://mentors.debian.net/package/pcapy


Alternatively, one can download the package with dget using this command:

dget -x
https://mentors.debian.net/debian/pool/main/p/pcapy/pcapy_0.11.3-1.dsc

More information about hello can be obtained from https://www.example.com.

Changes since the last upload:

[ Jakub Wilk ]
* Use canonical URIs for Vcs-* fields.

[ Ondřej Nový ]
* Fixed VCS URL (https)
* d/control: Set Vcs-* to salsa.debian.org
* d/changelog: Remove trailing whitespaces
* Remove debian/pycompat, it's not used by any modern Python helper

[ Emmanuel Arias ]
* new upstream version
* update d/watch to download correctly the last upstream version
* update d/control to add Maintainer the DPMT
* update d/control to add me to Uploaders field (Closes: #895787)
* update debhelper on d/contorl from 5.0.37.2 to 11
* update Standards-Version from 3.9.2 to 4.1.4 on d/control
* add Testsuite: autopkgtest-pkg-python on d/control
* update d/compat from 5 to 11
* add to copyright file the debian files copyright

Regards,
Emmanuel
-- 
Arias Emmanuel
https://www.linkedin.com/in/emmanuel-arias-437a6a8a
http://eamanu.com
-- 
Arias Emmanuel
https://www.linkedin.com/in/emmanuel-arias-437a6a8a
http://eamanu.com


RFS: pygithub/1.40a3-1 [ITP]

2018-05-29 Thread eamanu15
Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "pygithub"

* Package name: pygithub
   Version : 1.40a3-1
   Upstream Author : Author : Adam Dangoor 
   Vincent Jacques <
vinc...@vincent-jacques.net>
Jeremy Phelps <
jphe...@linuxfoundation.org>
* URL : https://pypi.python.org/pypi/PyGithub
* License : LGPL-3+
  Section : python

 It builds those binary packages:

python-github - Access to full Github API v3 from Python2
python3-github - Access the full Github API v3 from Python3

To access further information about this package, please visit the
following URL:

https://mentors.debian.net/package/pygithub
or https://salsa.debian.org/python-team/modules/pygithub

Alternatively, one can download the package with dget using this command:

dget -x
https://mentors.debian.net/debian/pool/main/p/pygithub/pygithub_1.40a3-1.dsc
or
git clone g...@salsa.debian.org:python-team/modules/pygithub.git

More information about pygithub can be obtained from
http://pygithub.readthedocs.io/

Changes since the last upload:
  * New upstream release
  * Update Standards-Version from 4.1.3 to 4.1.4 version
  * Add Uploaders field from debian/control to intent to adopt the
 package (Closes: #851187)


Regards,
Emmanuel Arias
-- 
Arias Emmanuel
https://www.linkedin.com/in/emmanuel-arias-437a6a8a
http://eamanu.com


Re: Asking for packaging

2018-05-10 Thread eamanu15
Ah! yes!

I understand Ondrej

Thank you very much!

El jue., 10 de may. de 2018 a la(s) 13:15, Ondrej Novy <n...@ondrej.org>
escribió:

> Hi,
>
> 2018-05-10 16:49 GMT+02:00 eamanu15 <emmanuelaria...@gmail.com>:
>
>> Ok, I could see that all agree with upload to mentors for sponsorship, I
>> push to git.
>>
>
> no, I don't agree :). I'm sponsoring just from git. I don't care mentors
> website at all.
>
>
>> I think, that this steps, for DPMT shall be writing in the policy or in a
>> "how to do" file to avoid confusing and to all the members do the same step.
>>
>
> because not all agrees, it's nothing we can put inside DPMT policy. Every
> sponsor have own "policy".
>
> It's simple: Find a sponsor (mentors ML, IRC, IRL, private message, ...)
> and ask how he wants it. Different DD have different habits.
>
> --
> Best regards
>  Ondřej Nový
>
> Email: n...@ondrej.org
> PGP: 3D98 3C52 EB85 980C 46A5  6090 3573 1255 9D1E 064B
>
> --
Arias Emmanuel
https://www.linkedin.com/in/emmanuel-arias-437a6a8a
http://eamanu.com


Re: Asking for packaging

2018-05-10 Thread eamanu15
Hi!


Ok, I could see that all agree with upload to mentors for sponsorship, I
push to git.

I think, that this steps, for DPMT shall be writing in the policy or in a
"how to do" file to avoid confusing and to all the members do the same step.

That is my humble opinion.

Regards!

El jue., 10 de may. de 2018 a la(s) 11:57, Thomas Goirand 
escribió:

> On 05/10/2018 09:36 AM, Ondrej Novy wrote:
> > Typically it's not needed to push it to
> > debian-mentors, because sponsor will pull package from our git.
>
> That's probably the way *you* do, which is a fine way to do it.
>
> Though I, and I know a lot of other DDs, prefer to sponsor the resulting
> source package, rather than just being pointed at the Git. As the
> mentors site gives lintian results, it saves a lot of time when dealing
> with new comers that might not know well lintian.
>
> So I don't agree here. I'd say, just push to mentors.debian.net first,
> just in case your sponsor likes it, and then see if your sponsor prefers
> Git only. Later on, if you get into the habits of having only 1 or 2
> sponsors, then maybe you'll arrange with them to use only Git.
>
> Cheers,
>
> Thomas Goirand (zigo)
>
> --
Arias Emmanuel
https://www.linkedin.com/in/emmanuel-arias-437a6a8a
http://eamanu.com


Re: Asking for packaging

2018-05-10 Thread eamanu15
Hello!

El jue., 10 de may. de 2018 a la(s) 04:36, Ondrej Novy <n...@ondrej.org>
escribió:

> Hi,
>
> 2018-05-09 16:02 GMT+02:00 eamanu15 <emmanuelaria...@gmail.com>:
>
>> When I make a push to the package that I maintain on salsa repo. Is
>> necessary upload the package to debian-mentors too?
>>
>
> after you push changes to salsa repo, you need sponsor for upload. Best
> way to find sponsor for DPMT packages is to join IRC #debian-python and ask
> for sponsoring there. Typically it's not needed to push it to
> debian-mentors, because sponsor will pull package from our git.
>

Ok!! Thanks very much!
Best Regards!

> --
> Best regards
>  Ondřej Nový
>
> Email: n...@ondrej.org
> PGP: 3D98 3C52 EB85 980C 46A5  6090 3573 1255 9D1E 064B
>
> --
Arias Emmanuel
https://www.linkedin.com/in/emmanuel-arias-437a6a8a
http://eamanu.com


Re: Asking for packaging

2018-05-09 Thread eamanu15
Great! Thanks!

El mié., 9 de may. de 2018 a la(s) 12:43, Thomas Goirand <z...@debian.org>
escribió:

> On 05/09/2018 04:02 PM, eamanu15 wrote:
> > Hello everybody,
> >
> > When I make a push to the package that I maintain on salsa repo. Is
> > necessary upload the package to debian-mentors too?
> >
> > Thanks for your response
>
> Hi there!
>
> Indeed, just pushing a change to Salsa will *not* upload the package to
> Debian, so you will need to find a sponsor to push your changes to the
> actual Debian repositories.
>
> However, it's fine if you have commits that aren't yet uploaded to
> Debian, for example if you think it's worse pushing the change to Git,
> but you think it's ok to upload to Debian later.
>
> I hope this helps,
> Cheers,
>
> Thomas Goirand (zigo)
>
> --
Arias Emmanuel
https://www.linkedin.com/in/emmanuel-arias-437a6a8a
http://eamanu.com


Re: Request access on salsa project

2018-05-09 Thread eamanu15
Thank you!

Arias Emmanuel
eamanu.com

El mié., 9 de may. de 2018 06:59, Ondrej Novy <n...@ondrej.org> escribió:

> Hi,
>
> 2018-05-03 12:13 GMT+02:00 eamanu15 <emmanuelaria...@gmail.com>:
>>
>> But, I lost my privileges when the project was migrate to salsa. Could
>> you give me access to pygithub?
>>
>
> added, welcome again :)
>
> --
> Best regards
>  Ondřej Nový
>
> Email: n...@ondrej.org
> PGP: 3D98 3C52 EB85 980C 46A5  6090 3573 1255 9D1E 064B
>
>


Request for acces to salsa project

2018-05-07 Thread eamanu15
Hello everybody,

I resend this mail.

I was maintaining pygtihub project (
https://salsa.debian.org/python-team/modules/pygithub/)

But, I lost my privileges when the project was migrate to salsa. Could you
give me access to pygithub?

I have some commits.

My salsa user is: eamanu-guest

Thanks very much!
Regards!
-- 
Arias Emmanuel
https://www.linkedin.com/in/emmanuel-arias-437a6a8a
http://eamanu.com


Request access on salsa project

2018-05-03 Thread eamanu15
Hello everybody,

I was maintaining pygtihub project (
https://salsa.debian.org/python-team/modules/pygithub/)

But, I lost my privileges when the project was migrate to salsa. Could you
give me access to pygithub?

My salsa user is: eamanu-guest

Thanks very much!
Regards!
-- 
Arias Emmanuel
https://www.linkedin.com/in/emmanuel-arias-437a6a8a
http://eamanu.com


Re: Request Joining the team

2018-01-24 Thread eamanu15 .
Thank you!!!

El mié., 24 de ene. de 2018 a la(s) 05:08, Piotr Ożarowski <pi...@debian.org>
escribió:

> [eamanu15 ., 2018-01-18]
> > I send this mail requesting join to the team for many reason. Fist, I
> love
> > Python, I use it on my job and for my hobbies. Second, I am new on
> Debian,
> > so I am enthusiastic about learn to work collaboratily in a open source.
> > Furthermore I am maintainer of cligh, a python debian package.
> >
> > My Alioth User is: eamanu-guest
> >
> > I read https://python-modules.alioth.debian.org/policy.html and I acept
> it.
>
> Welcome in the team! :)
> --
> GPG: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645
>
>

-- 
Arias Emmanuel
https://www.linkedin.com/in/emmanuel-arias-437a6a8a
http://eamanu.com


Request Joining the team

2018-01-18 Thread eamanu15 .
Dears DPMT members,

I send this mail requesting join to the team for many reason. Fist, I love
Python, I use it on my job and for my hobbies. Second, I am new on Debian,
so I am enthusiastic about learn to work collaboratily in a open source.
Furthermore I am maintainer of cligh, a python debian package.

My Alioth User is: eamanu-guest

I read https://python-modules.alioth.debian.org/policy.html and I acept it.

Thank for your time
Regards!
Emmanuel



-- 
Arias Emmanuel
https://www.linkedin.com/in/emmanuel-arias-437a6a8a
http://eamanu.com


FYI: Fwd: RFS: pygithub/1.35-1[ITA]

2018-01-17 Thread eamanu15 .
FYI

-- Forwarded message -
From: eamanu15 . <emmanuelaria...@gmail.com>
Date: mié., 17 de ene. de 2018 a la(s) 18:37
Subject: RFS: pygithub/1.35-1[ITA]
To: Debian Mentors List <debian-ment...@lists.debian.org>


Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "pygithub"

* Package name: pygithub
  Version : 1.35-1
  Upstream Author : Adam Dangoor <adamdang...@gmail.com>
Vincent Jacques <vinc...@vincent-jacques.net>
Jeremy Phelps <jphe...@linuxfoundation.org>
* URL : https://pypi.python.org/pypi/PyGithub
* License : LGPL-3+
  Section : python

It builds those binary packages:
python-github - Access to full Github API v3 from Python2
python3-github - Access the full Github API v3 from Python3

To access further information about this package, please visit the
following URL:
https://mentors.debian.net/package/pygithub

Alternatively, one can download the package with dget using this command:
dget -x
https://mentors.debian.net/debian/pool/main/p/pygithub/pygithub_1.35-1.dsc

Changes since the last upload:
   * New upstream release
   * Update Maintainer field from debian/control to intent to adopt
the package (Closes: #851187)
   * Update Standards-Version from  3.9.6 to 4.1.3 from debian control
according to the up-to-date standards
   * Add new maintainer on copyright debian/* files field from
debian/copyright to stay up-to-date
   * Remove override_dh_installchangelogs target from debian/rules due to
the new version (1.35) do not have README.rst file

Regards,
Emmanuel


-- 
Arias Emmanuel
https://www.linkedin.com/in/emmanuel-arias-437a6a8a
http://eamanu.com


-- 
Arias Emmanuel
https://www.linkedin.com/in/emmanuel-arias-437a6a8a
http://eamanu.com


Re: Python 2 removal strategy

2018-01-10 Thread eamanu15 .
Hi Ole,

It would be great have two different package. One of them, the python3
version and maintain the python2 version.

Regards!
Emmanuel

El mié., 10 de ene. de 2018 a la(s) 18:03, Matthias Klose 
escribió:

> On 10.01.2018 17:06, Ole Streicher wrote:
> > Hi,
> >
> > I am the maintainer of the "python-astropy" package, that currently
> > creates packages for both Python 2 and Python 3. Both packages have a
> > number of reverse dependencies.
> >
> > Recently, upstream announced a new version 3.0 of astropy, which
> > supports Python 3 only, and I think of the best mid-term strategy: The
> > old version 2.0 is supported upstream for ~2 years, and I want to have a
> > smooth migration path. I checked the wiki, but could not find good
> > information about migration.
>
> Currently discussed. See "Python2 EOL and moving towards Python3" on this
> ML.
>
> > I thought of a temporary package split: create a new source package
> > "astropy" that inherits of the current python-astropy package, but only
> > builds python3-astropy (and the utils + doc, which depend on
> > python3-astropy), and update this to version 3.0. Then I would remove
> > these binary packages from the python-astropy package. In parallel, I
> > would file bugs (severity: important) to remove the reverse dependencies
> > of the Python 2 packages (many of them are mine, but also may have
> > reverse dependencies).
> >
> > As long as there are substantial problems with the removal of the Python
> > 2 support, I then keep the "old" python-astropy package updated. Once
> > everything is figured out and we decide to finally kick out Python 2
> > support (from Debian-Astro, or from Debian), I would set the remaining
> > bugs as RC, and (once they are solved) remove the "python-astropy"
> > package.
> >
> > Does this sound reasonable? And how should I do this technically?
>
> well, astropy is not such a mainstream package that I would mind removing
> some
> of it's reverse dependencies.  If you want to add the additional pain
> having a
> separate Python2 source stack, go for it. I wouldn't want to do that
> myself.  If
> not, just go ahead with Python3 after having identified the reverse
> dependencies
> which are not maintained by yourself.
>
> Matthias
>
>

-- 
Arias Emmanuel
https://www.linkedin.com/in/emmanuel-arias-437a6a8a
http://eamanu.com