Re: Updated package list with packages open for adoption (Was: morph's abandoned packages (list))

[Emmanuel Arias]

Hi

On 3/28/24 6:24 AM, Andreas Tille wrote:

[snip]


? #1065244 O: kiwisolver -- fast implementation of the Cassowary constraint 
solver
 Build-Dep: geophar (Maintainer: Georges Khaznadar )
turing (Georges Khaznadar )
python3-vispy 
(debian-science-maintain...@lists.alioth.debian.org
   Ghislain Antony Vaillant )
python3-matplotlib (Taken by alexandre.deti...@gmail.com, 
deba...@debian.org)

I just adopted it.

[snip]

Cheers,
Emmanuel

Re: Updated package list with packages open for adoption (Was: morph's abandoned packages (list))

[Emmanuel Arias]

Hello Andreas!

Thanks for the list.

With this we cover all packages? I'm asking because I'm looking other 
list with more packages [0]


On 3/28/24 6:24 AM, Andreas Tille wrote:

[snip]


? #1065246 O: contourpy -- Python library for calculating contours of 2D 
quadrilateral grids
 rdepends: python3-matplotlib
   Taken by alexandre.deti...@gmail.com, deba...@debian.org
oops! sorry! I've just make an upload adopting this package before read 
this mail, please add you as Uploaders. I did not package new upstream 
release because it is a matplotlib dependency. My plan was upload new 
upstream version to experimental, but I prefer wait for tchet and 
debacle opinion. Sorry again.

[snip]



? #1065224 O: mysql-connector-python -- pure Python implementation of MySQL 
Client/Server protocol
 ??> Emmanuel Arias  - I did not fully understood
 whether you want to take this.
 In the light of the discussion of bug #923347 I wonder whether we need
 this package.  Its not part of any stable release listed at tracker.d.o
Yes, I will add myself as uploader right now, but I will leave this 
package in unstable only because is a dependency of mysql-workbench.



[snip]


[0] https://lists.debian.org/debian-python/2024/03/msg00045.html


--
cheers,
    Emmanuel Arias

 ⢀⣴⠾⠻⢶⣦⠀
 ⣾⠁⢠⠒⠀⣿⡁  eam...@debian.org
 ⢿⡄⠘⠷⠚⠋⠀  OpenPGP: 13796755BBC72BB8ABE2AEB5 FA9DEC5DE11C63F1 


 ⠈⠳⣄

Re: Maintenance of python-tomlkit

[Emmanuel Arias]

Hi Scott,

I can take it.


cheers,
Emmanuel Arias

 ⢀⣴⠾⠻⢶⣦⠀
 ⣾⠁⢠⠒⠀⣿⡁  eam...@debian.org
 ⢿⡄⠘⠷⠚⠋⠀  OpenPGP: FA9DEC5DE11C63F1
 ⠈⠳⣄


On Fri, Mar 15, 2024 at 2:50 PM Scott Kitterman 
wrote:

> This is another one I don't use anymore where I'm the sole uploader.
>
> It's got a fair number of rdepends, most notably poetry.  Any takers
> before I
> orphan it?
>
> Scott K

Re: Maintenance of python-cryptography

[Emmanuel Arias]

Hi!




On Fri, Mar 15, 2024 at 4:19 AM Thomas Goirand  wrote:

> On 3/13/24 18:34, Scott Kitterman wrote:
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064979
> >
> > Would some of you who are pushing so hard to change the policy for
> Uploaders/
> > Maintainer in the team please step up and take over this package.  It
> really
> > needs updated to the new upstream release (blocking both aioquic and
> > dnspythong for me, I don't know about others).
> >
> > I haven't done a comprehensive check, but I think morph asked for all
> the leaf
> > packages he was maintaining in the team to be removed from the archive
> and is
> > removing himself from uploaders/maintainer on others.
> >
> > You all made this mess.  Please clean it up.
>
> Absolutely not. Sandro did. There's btw absolutely no reason to declare
> a package as "orphan" if it is supposed to be team maintained. It's also
> a very bad behavior to do this silently, without telling the team about
> it, or taking part of the thread. I very much regret things are
> happening this way, but I don't think the rest of the team should be
> held responsible.
>
> If you have the list of the packages matching what you are saying,
> please do share.
>

I think you are looking for this
https://lists.debian.org/debian-python/2024/03/msg00045.html

>
> On 3/14/24 08:52, Andreas Tille wrote:
>  > I would have prefered to
>  > read constructive arguments instead of silent leaving the team (in the
>  > sense of not informing the team mailing list about the leave).
>
> Me too. But I'm not surprised.
>
>
> Cheers,
>
> Thomas Goirand (zigo)
>
>

Re: Suggesting change in DPT policy

[Emmanuel Arias]

 to be MIA.  This means the packages are
> de-facto not maintained which is most probably an unwanted effect of the
> current policy.  I know other maintainers from other teams to be fine
> with stronger team understanding.
> 
> Since I consider the current situation as demotivating for newcomers
> as well as long standing contributors I would like to suggest to drop
> this "weak statement of collaboration" option from policy.  I've attached
> an according patch to the team policy[5].  I'm fine with creating a MR
> to be discussed rather in Salsa than this mailing list - whatever seems
> worthwhile to you.


+1 for this DPT policy change.

When I started to contribute I received these kind of comments that made
me think if I could really start contributing to Debian. As time went
by, I learned to read first who is the maintainer of the package before
read the bug reported, no matter if the package is (apparently) under the
DPT umbrella.



-- 
cheers,
Emmanuel Arias

 ⢀⣴⠾⠻⢶⣦⠀
 ⣾⠁⢠⠒⠀⣿⡁  eam...@debian.org
 ⢿⡄⠘⠷⠚⠋⠀  OpenPGP: 13796755BBC72BB8ABE2AEB5 FA9DEC5DE11C63F1
 
 ⠈⠳⣄


signature.asc
Description: PGP signature

Re: RFS: filecheck

[Emmanuel Arias]

Hi!

Uploaded! Thanks for you contribution to Debian :-)

Cheers,
Emmanuel

On Sun, Oct 15, 2023 at 11:24:20PM +0800, Bo YU wrote:
> Hi!
> 
> On Sat, Oct 14, 2023 at 5:27 AM Emmanuel Arias  wrote:
> >
> > Hi!
> >
> > On Thu, Oct 12, 2023 at 05:03:45PM +0800, Bo YU wrote:
> > > Hi！
> > >
> > > Thanks for reviewing my package!
> > >
> > >
> > > On Tue, Oct 10, 2023 at 3:51 AM Emmanuel Arias  wrote:
> > > >
> > > > On Mon, Oct 09, 2023 at 02:46:36PM -0300, Emmanuel Arias wrote:
> > > > > Hi!
> > > > >
> > > > > On Sat, Oct 07, 2023 at 09:34:43PM +0800, Bo YU wrote:
> > > > > > Hi team!
> > > > > >
> > > > > > Due to rfs bot maybe not work on debian-python irc, So I am seeking 
> > > > > > help
> > > > > > to review/upload my new python package:
> > > > > >
> > > > > > https://salsa.debian.org/python-team/packages/filecheck
> > > > > >
> > > > > > TIA.
> > > > > To avoid duplicated work from another team member, I mention here, I'm
> > > > > going to review this package.
> > > > >
> > > > > Cheers,
> > > > > Emmanuel
> > > >
> > > > Hi!,
> > > >
> > > > Me again.
> > > >
> > > > I leave you some comments regarding to FileCheck
> > > >
> > > > * Binary package suggests install the docs package, but is not in
> > > >   d/control.
> > > Done. Here the ideal situation should be a docs package on there, but if 
> > > we use
> > > sphinx-build to build its doc, there is one guzzle_sphinx_theme does
> > > not in Debian.
> > > So I package its manpage to binary package.
> >
> > OK.
> >
> > >
> > > > * Package should depends on python3-poetry-core instead of 
> > > > python3-poetry
> > > Done.
> > >
> > > > * d/copyright: upstream does not specify a range of date 2019-2023, 
> > > > only in
> > > >   docs/conf.py the copyright says 2019.
> > > Yeah, although there are only one file flaged its date on 2019, but
> > > how to judge the
> > > whole project copyright date range? I just follow its the first commit:
> > >
> > > https://github.com/mull-project/FileCheck.py/commits/main?after=195aa1527a2572b4697ae0d5c604f0baceba805c+419=main_name=refs%2Fheads%2Fmain
> > >
> > > Not sure this is right.
> >
> > I'd just use 2019, not a range.
> 
> Ok, done.
> >
> > >
> > > > * The package synopsis should not finished with a period. Please remove 
> > > > it.
> > > Sorry, I am not very clear about here. Do you mean here:
> > > https://salsa.debian.org/python-team/packages/filecheck/-/blob/debian/main/debian/control#L30
> > > If yes, I think the synopsis solution should be more robust here.
> > > Because it saves more space than
> > > specially descriptions.
> > >
> > > please let me know if there is not true.
> >
> > Sorry, perhaps I was not clear, I mean remove the period at the end of
> > line 20 [0].
> 
> Okay, done. :)
> >
> > >
> > > > * The binary package should not be python3-filecheck?
> > > You hint me here. So I spilted the origin package into python3 library
> > > package and
> > > its binary tool binary. this should be working.
> > >
> > > I have updated the package on salsa:
> > > https://salsa.debian.org/python-team/packages/filecheck
> > >
> > > Thanks again for reviewing the package!
> > >
> > > BR,
> > > Bo
> > > >
> > > > Cheers,
> > > > Emmanuel
> > > > > >
> > > > > > BR,
> > > > > > Bo
> > > > > >
> > > >
> > > >
> >
> > The rest looks good to me.
> 
> Thanks.
> I updated the package here:
> https://salsa.debian.org/python-team/packages/filecheck/-/tree/debian/main/debian
> 
> Thanks,
> BR,
> Bo
> >
> > [0] 
> > https://salsa.debian.org/python-team/packages/filecheck/-/blob/debian/main/debian/control#L20


signature.asc
Description: PGP signature

Re: RFS: filecheck

[Emmanuel Arias]

Hi!

On Thu, Oct 12, 2023 at 05:03:45PM +0800, Bo YU wrote:
> Hi！
> 
> Thanks for reviewing my package!
> 
> 
> On Tue, Oct 10, 2023 at 3:51 AM Emmanuel Arias  wrote:
> >
> > On Mon, Oct 09, 2023 at 02:46:36PM -0300, Emmanuel Arias wrote:
> > > Hi!
> > >
> > > On Sat, Oct 07, 2023 at 09:34:43PM +0800, Bo YU wrote:
> > > > Hi team!
> > > >
> > > > Due to rfs bot maybe not work on debian-python irc, So I am seeking help
> > > > to review/upload my new python package:
> > > >
> > > > https://salsa.debian.org/python-team/packages/filecheck
> > > >
> > > > TIA.
> > > To avoid duplicated work from another team member, I mention here, I'm
> > > going to review this package.
> > >
> > > Cheers,
> > > Emmanuel
> >
> > Hi!,
> >
> > Me again.
> >
> > I leave you some comments regarding to FileCheck
> >
> > * Binary package suggests install the docs package, but is not in
> >   d/control.
> Done. Here the ideal situation should be a docs package on there, but if we 
> use
> sphinx-build to build its doc, there is one guzzle_sphinx_theme does
> not in Debian.
> So I package its manpage to binary package.

OK.

> 
> > * Package should depends on python3-poetry-core instead of python3-poetry
> Done.
> 
> > * d/copyright: upstream does not specify a range of date 2019-2023, only in
> >   docs/conf.py the copyright says 2019.
> Yeah, although there are only one file flaged its date on 2019, but
> how to judge the
> whole project copyright date range? I just follow its the first commit:
> 
> https://github.com/mull-project/FileCheck.py/commits/main?after=195aa1527a2572b4697ae0d5c604f0baceba805c+419=main_name=refs%2Fheads%2Fmain
> 
> Not sure this is right.

I'd just use 2019, not a range.

> 
> > * The package synopsis should not finished with a period. Please remove it.
> Sorry, I am not very clear about here. Do you mean here:
> https://salsa.debian.org/python-team/packages/filecheck/-/blob/debian/main/debian/control#L30
> If yes, I think the synopsis solution should be more robust here.
> Because it saves more space than
> specially descriptions.
> 
> please let me know if there is not true.

Sorry, perhaps I was not clear, I mean remove the period at the end of
line 20 [0].

> 
> > * The binary package should not be python3-filecheck?
> You hint me here. So I spilted the origin package into python3 library
> package and
> its binary tool binary. this should be working.
> 
> I have updated the package on salsa:
> https://salsa.debian.org/python-team/packages/filecheck
> 
> Thanks again for reviewing the package!
> 
> BR,
> Bo
> >
> > Cheers,
> > Emmanuel
> > > >
> > > > BR,
> > > > Bo
> > > >
> >
> >

The rest looks good to me.

[0] 
https://salsa.debian.org/python-team/packages/filecheck/-/blob/debian/main/debian/control#L20


signature.asc
Description: PGP signature

Re: RFS: filecheck

[Emmanuel Arias]

On Mon, Oct 09, 2023 at 02:46:36PM -0300, Emmanuel Arias wrote:
> Hi!
> 
> On Sat, Oct 07, 2023 at 09:34:43PM +0800, Bo YU wrote:
> > Hi team!
> > 
> > Due to rfs bot maybe not work on debian-python irc, So I am seeking help
> > to review/upload my new python package:
> > 
> > https://salsa.debian.org/python-team/packages/filecheck
> > 
> > TIA.
> To avoid duplicated work from another team member, I mention here, I'm
> going to review this package.
> 
> Cheers,
> Emmanuel

Hi!, 

Me again.

I leave you some comments regarding to FileCheck

* Binary package suggests install the docs package, but is not in 
  d/control.
* Package should depends on python3-poetry-core instead of python3-poetry
* d/copyright: upstream does not specify a range of date 2019-2023, only in
  docs/conf.py the copyright says 2019.
* The package synopsis should not finished with a period. Please remove it.
* The binary package should not be python3-filecheck?

Cheers,
Emmanuel
> > 
> > BR,
> > Bo
> > 




signature.asc
Description: PGP signature

Re: RFS: filecheck

[Emmanuel Arias]

Hi!

On Sat, Oct 07, 2023 at 09:34:43PM +0800, Bo YU wrote:
> Hi team!
> 
> Due to rfs bot maybe not work on debian-python irc, So I am seeking help
> to review/upload my new python package:
> 
> https://salsa.debian.org/python-team/packages/filecheck
> 
> TIA.
To avoid duplicated work from another team member, I mention here, I'm
going to review this package.

Cheers,
Emmanuel
> 
> BR,
> Bo
> 


signature.asc
Description: PGP signature

Re: Maintenance of gtts (python3-gtts)

[Emmanuel Arias]

Hello Scott,

I don't use it, but seems an interested project. I can work on it, but
it would be great if you have a maintainer that already know the project.

Cheers,
Emmanuel

On Sun, Aug 06, 2023 at 05:23:53PM -0400, Scott Kitterman wrote:
> The gtts package is, at least nominally, maintained by the Debian Python 
> Team, 
> but has no human uploader.  As a practical matter, I think someone should 
> either adopt it (add themselves to uploaders) or we should formally orphan 
> the 
> package so we aren't pretending.
> 
> It has two rdepends:
> 
> Reverse-Depends
> ===
> * dialect [amd64 arm64 armel armhf i386 mips64el mipsel ppc64el]
> * mnemosyne
> 
> I personally track mnemosyne, even though it's not team maintained, because i 
> have an interest in the package.  I noticed it was going to be removed from 
> Testing because of a FTBFS bug in gtts, so I fixed gtts by updating it to the 
> current upstream release.  Looking at the upload history, it's been this way 
> for awhile.
> 
> One consequence of it not being actually maintained is that we released 
> bookworm with a non-functional gtts package (see #1030290).  If anyone had 
> been paying attention to the package, they would have noticed that should 
> have 
> been an RC bug (it is now) and it would have either been fixed or removed.
> 
> The package is now in not awful shape in Unstable (and barring surprises 
> Testing later today), but it could still use some work.  The major immediate 
> task for a potential maintainer would be working with the Stable Release 
> Managers to get bookworm fixed.
> 
> If you're interested in the package and wiling to watch over it, please let 
> me 
> know via email.  If I don't hear back, I'll assume no one is interested and 
> orphan it in a week or two.
> 
> Thanks,
> 
> Scott K




signature.asc
Description: PGP signature

Re: [mic...@michel-slm.name: Bug#1037174: RFS: damo/1.8.4-1 [ITP] -- Data Access Monitoring Operator]

[Emmanuel Arias]

On Tue, Jun 06, 2023 at 09:56:09PM -0500, Michel Alexandre Salim wrote:
> Dear fellow Python team members,
> 
> Please find forwarded my RFS for damo (LWN write-up:
> https://lwn.net/Articles/931769/)
> 
> I can't add it to the TODO page on the wiki yet, as I'm waiting for my
> wiki account to be manually approved.
> 
You can ask in #debian-python irc channel as well (if you don't do it).

Cheers,
Emmanuel
> Thanks,
> 
> Michel
> 
> - Forwarded message from Michel Alexandre Salim  
> -
> 
> Date: Tue, 6 Jun 2023 21:45:25 -0500
> From: Michel Alexandre Salim 
> To: sub...@bugs.debian.org
> Subject: Bug#1037174: RFS: damo/1.8.4-1 [ITP] -- Data Access Monitoring
>   Operator
> 
> Package: sponsorship-requests
> Severity: wishlist
> 
> Dear mentors,
> 
> I am looking for a sponsor for my package "damo":
> 
>  * Package name : damo
>Version  : 1.8.4-1
>Upstream contact : SeongJae Park 
>  * URL  : https://damonitor.github.io/
>  * License  : GPL-2
>  * Vcs  : https://salsa.debian.org/python-team/packages/damo
>Section  : devel
> 
> The source builds the following binary packages:
> 
>   damo - Data Access Monitoring Operator
> 
> To access further information about this package, please visit the following 
> URL:
> 
>   https://mentors.debian.net/package/damo/
> 
> Alternatively, you can download the package with 'dget' using this command:
> 
>   dget -x https://mentors.debian.net/debian/pool/main/d/damo/damo_1.8.4-1.dsc
> 
> Changes for the initial release:
> 
>  damo (1.8.4-1) unstable; urgency=medium
>  .
>* Initial release. (Closes: #1037157)
> 
> Regards,
> 
> -- 
> Michel Alexandre Salim
> identities: https://keyoxide.org/5dce2e7e9c3b1cffd335c1d78b229d2f7ccc04f2
> 
> 
> 
> - End forwarded message -
> 
> -- 
> Michel Alexandre Salim
> identities: https://keyoxide.org/5dce2e7e9c3b1cffd335c1d78b229d2f7ccc04f2




signature.asc
Description: PGP signature

Re: twitterwatch - upload needed

[Emmanuel Arias]

Hi,

On Tue, Jan 17, 2023 at 6:16 PM Malik  wrote:

> Hello Emmanuel,
>
> currently upstream-author has no plan to update or release any further
> releases for this project [1]
>
Ok

>
>

> [1] https://gitlab.com/chaica/twitterwatch/-/issues/1
>
> kind regards,
> Malik
>

If you leave the package as is it now, when a new release exists, d/watch
won't note it.
So, I'd change the d/watch to the Gitlab repository. Also Homepage link.

Cheers,
Emmanuel

Re: twitterwatch - upload needed

[Emmanuel Arias]

Hi,

On Sun, Jan 15, 2023 at 12:24:43PM +0100, Malik wrote:
> Hello Emannauel,
> 
> Thank you for the suggestions.
> 
> I was not sure how to handle the new homepage [1]  since there are no tags
> or releases maintained by the upstream maintainer, should I delete the
> watchfile? or can I watch the version in the setup.py ?

Oh, I didn't note it. Perhaps it's a good reason to contact to upstream
and ask for them. Don't remove d/watch file.

> 
> And for the tests, should I mock the calls to the "internet" since those
> would be skipped if conceited to the internet

Yes, or skip them.
> 
> 
> [1]: https://gitlab.com/chaica/twitterwatch/-/tags
> 
> regards,
> Malik
> 

Cheers,
Emmanuel


signature.asc
Description: PGP signature

Re: twitterwatch - upload needed

[Emmanuel Arias]

Hi,


On Fri, Jan 13, 2023 at 09:49:15PM +0100, Malik wrote:
> Hello DPT,
> 
> I have created a patch to close #996799 in twitterwatch package [1]
> I need a mainter to upload the current version (0.1-3) to the tftp-master

As Timo mentioned in the bug report. It would be great if the Homepage can
be updated as well.

Also, the package doesn't have tests (if I'm not wrong). Could you add
autopkgtests?

Cheers,
Emmanuel
> 
> [1] https://salsa.debian.org/python-team/packages/twitterwatch
> 
> Thank you in  advance
> -- 
> Malik Mlitat




signature.asc
Description: PGP signature

Re: build package

[Emmanuel Arias]

Hi,

Cannot be because of the i386 arch?

Cheers,

Emmanuel

On Thu, Nov 17, 2022 at 2:58 PM Nilson Silva 
wrote:

> Hello guys!
>
> Could someone help me to find out the error of this package?
>
> https://salsa.debian.org/nilsonfsilva/librosa/-/jobs/3528766
>
> Thanks!
>
> Nilson F. Silva
>
>
>
>
>
>

Re: Python in the Debian infrastructure

[Emmanuel Arias]

Hi,

Thanks Julien, Antonio.

So many projects! Thanks for the information. And thanks Antonio
for pointing me to your presentation, I missed it.

Cheers,
Emmanuel

On Fri, Aug 19, 2022 at 11:03 AM Julien Cristau  wrote:

> On Fri, Aug 19, 2022 at 10:25:25AM -0300, Antonio Terceiro wrote:
> > On Fri, Aug 19, 2022 at 09:29:40AM -0300, Emmanuel Arias wrote:
> > > Hi,
> > >
> > > I'm very interested :-)
> > >
> > >
> > > On Wed, Aug 17, 2022 at 9:23 PM Louis-Philippe Véronneau <
> po...@debian.org>
> > > wrote:
> > [...]
> > > > - patching tracker.debian.org (Django) to show pending MRs [10] [11]
> > > >
> > >  I'm just curious, we know or it's easy to know  if there're more
> parts of
> > > the Debian
> > > infrastructure where Python is used and we can help?
> >
> > Lots of it. I made a talk about contributing with the Debian
> > infrastructure in 2020 online minidebconf, and here is the contents of
> > my summary slide:
> >
> > 
> > ## Summary
> >
> > Project  | Ruby | OCaml | Python | Shell | Perl | JS
> > -|::|:-:|:--:|:-:|::|:---
> > [ci.debian.net][]|  x   |   ||   x   |  |
> > [dose3][]|  |   x   ||   |  |
> > [botch][]|  |   x   ||   |  |
> > [devscripts][]   |  |   |   x|   x   |  x   |
> > [licensecheck][] |  |   ||   |  x   |
> > [Debian Keyring][]   |  x   |   |   x|   x   |  |
> > [sources.debian.org][]   |  |   |   x|   |  |
> > [contributors.debian.org][]  |  |   |   x|   |  |
> > [Security Team][]|  |   |   x|   |  |
> > [debtags.debian.org][]   |  |   |   x|   |  |  x
> > [moinmoin][] |  |   |   x|   |  |
> > [nm.debian.org][]|  |   |   x|   |  |
> > [sso.debian.org][]   |  |   |   x|   |  |
> > [tracker.debian.org][]   |  |   |   x|   |  |
> >
> I'll add a few:
> - dak / ftp-master
> - snapshot
> - pybuildd
> - planet
> - security-tracker
> - release tools (britney, transitions, queue-viewer, ...)
> - udd
> - userdir-ldap
> - piuparts
> - mirror-status
> - veyepar.debian.org
> - debconf websites
> - debdelta
>
> Cheers,
> Julien
>
>

Re: Are YOU interested in a potential remote sprint sometime in October/November? (yes YOU!)

[Emmanuel Arias]

Hi,

I'm very interested :-)


On Wed, Aug 17, 2022 at 9:23 PM Louis-Philippe Véronneau 
wrote:

> Hello folks,
>
> At DC22, a few people seemed interested in a potential Python Team
> remote sprint, sometime between October and early December.
>
> I'm thus writing to the list to see if there is indeed interest for
> this. If only 2 people reply, I won't push this further :)
>
> Here are a few potential ideas of things people could work on, in no
> particular order:
>
> - working on testing and merging the pybuild-autodep8 feature [1]
> - fixing the ~50 packages that are still using 'python3 setup.py' [2]
> - reviewing and merging unnoticed salsa MRs on the Team's packages [3]
> - fixing policy violations [4]
> - upstreaming CPython patches [5]
> - trying to remove all remaining Python 2 packages [6]
> - working on PEP 668 [7] [8]
> - working on lintian tags for the team [9]
> - patching tracker.debian.org (Django) to show pending MRs [10] [11]
>
 I'm just curious, we know or it's easy to know  if there're more parts of
the Debian
infrastructure where Python is used and we can help?


Cheers!
Emmanuel

>
> People are of course welcome to work on whatever other things they see
> fit for the betterment of the Team :)
>
> I've done a remote sprint for the Clojure Team back in May and it went
> great.
>
> Each people registered and we asked for a food budget, based on the
> "Meals and Incidentals Rate" the US government publishes for most cities
> in the world [12] [13]. I encourage you to look up your city, but I know
> I ended up eating pretty well :)
>
> I would envision a 3 day sprint (Friday, Saturday, Sunday) being long
> enough yet not too long for most of us to make progress on key issues
> without being over-tiring.
>
> Happy to hear back from y'all (please do if you're interested). If I see
> people are interested, I'll send a poll to find the most suitable dates.
>
> Cheers,
>
>
> [1]:
> https://salsa.debian.org/python-team/tools/dh-python/-/merge_requests/27
> [2]: https://lists.debian.org/debian-python/2022/08/msg00046.html
> [3]: https://salsa.debian.org/groups/python-team/packages/-/merge_requests
> [4]:
> https://github.com/sandrotosi/dpt-repos-check/blob/main/violations.txt
> [5]: see https://pad.riseup.net/p/dc22pythonsprint-keep
> [6]: see https://lists.debian.org/debian-python/2022/07/msg00065.html
> [7]:
>
> https://discuss.python.org/t/pep-668-marking-python-base-environments-as-externally-managed/
> [8]: https://peps.python.org/pep-0668/
> [9]: see https://lists.debian.org/debian-python/2022/07/msg00065.html
> [10]: https://tracker.debian.org/teams/python/
> [11]: https://salsa.debian.org/qa/distro-tracker
>
> [12]:
> https://www.gsa.gov/travel/plan-book/per-diem-rates/per-diem-rates-lookup
> [13]: https://aoprals.state.gov/web920/per_diem.asp
>
> --
>⢀⣴⠾⠻⢶⣦⠀
>⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
>⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
>⠈⠳⣄
>

Asking for help for python-xlib

[Emmanuel Arias]

Hello everybody,

I'm working on the new upstream release 0.31 and I'm looking for this 
bug [0].
But, I can not reproduce it. If I run in 0.29 and 0.31 the tests finish 
successfully,
but in [1] fails in different archs. Could you reproduce it? Could you 
give me some

advice/tips/clues about why I cannot reproduce it, please?

Anyway I created this patch, because I suspect that for some reason, the
self.display.flush() is raising the Exception before pytest can catch 
it, but

I don't think that is possible.

```
From: Emmanuel Arias 
Date: Wed, 6 Jul 2022 18:10:50 -0300
Subject: Use context manager to avoid error in test.

Use context manager in tests to avoid an error during the Build in
Debian.

Bug-Debian: https://bugs.debian.org/1006033
---
 test/test_xlib_display.py | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/test/test_xlib_display.py b/test/test_xlib_display.py
index a41c53b..a2e31f3 100644
--- a/test/test_xlib_display.py
+++ b/test/test_xlib_display.py
@@ -52,8 +52,9 @@ class TestXlibDisplay(unittest.TestCase):
 self.assertEqual(str(self.display.display.socket_error), 
"Display connection closed by client")


 def test_can_close_display_and_check_for_error(self):
-    self.display.close()
-    self.assertRaises(Xlib.error.ConnectionClosedError, 
self.display.flush)

+    with self.assertRaises(Xlib.error.ConnectionClosedError):
+    self.display.close()
+    self.display.flush()

 def test_return_fileno(self):
 self.assertTrue(isinstance(self.display.fileno(), int))

```

[0] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006033
[1] 
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-xlib.html


Thanks!
Cheers,
Emmanuel


OpenPGP_0xFA9DEC5DE11C63F1.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature

Re: Making py2dsp/pypi2deb the default tool to create Python-based packages in Debian

[Emmanuel Arias]

Hi!

El vie, 8 jul 2022 a la(s) 00:10, Sandro Tosi (mo...@debian.org) escribió:

> Hello,
> Piotr has kindly moved pypi2deb to salsa[1] and given me access to the
> project so i was able to merge my changes and release[2] a new version
> of this tool in Debian.
>
> [1] https://salsa.debian.org/python-team/tools/pypi2deb
> [2]
> https://tracker.debian.org/news/1343951/accepted-pypi2deb-320220707-source-into-unstable/
>
> My goal is to make py2dsp (contained in pypi2deb) the default tool
> used to create Python packages in Debian (like many other
> language-specific tools already do f.e. for go, rust, npm, etc). The
> new release contains several enhancements that should cover many of
> the packaging needs, in particular:
>
> * the ability to package directly from a github project url
> * create the salsa project in the DPT group
>

Great, this is a very useful tool. I used your fork and cover all that I
need


> Please let me know if you think something is missing, or should be
> expanded/fix, you can also open bugs against the package or directly
> MR to the salsa project.
>
> Should we start advertising this tool in other locations, like the
> python policy, guidelines, wiki, etc? what do y'all think?
>

I think that it should be mentioned at least here [0][1]. IMO they're the
first
resources that are checked when someone starts packaging Python modules in
Debian.

[0] https://www.debian.org/doc/packaging-manuals/python-policy/
[1] https://wiki.debian.org/Python/LibraryStyleGuide

Cheers,
Emmanuel

>
> Thanks,
> --
> Sandro "morph" Tosi
> My website: http://sandrotosi.me/
> Me at Debian: http://wiki.debian.org/SandroTosi
> Twitter: https://twitter.com/sandrotosi
>
>

Bug#1008619: ITP: mdurl -- Python port of the JavaScript mdurl pacakge

[Emmanuel Arias]

Package: wnpp
Severity: wishlist
Owner: Emmanuel Arias 
X-Debbugs-Cc: debian-python@lists.debian.org

* Package name: mdurl
  Version : 0.1.0
  Upstream Author : Taneli Hukkinen 
* URL : https://github.com/executablebooks/mdurl
* License : expat
  Programming Lang: Python
  Description : Python port of the JavaScript mdurl pacakge

The JavaScript mdurl package is a set of URL utilities for markdown-it.
This package is a Python port needed for markdown-it-py package.

mdurl is need for markdown-it-py from v2.0.0. I plan maintain
mdurl under Debian Python Team umbrella.

Re: Should we allow Janitor to commit directly to all DPT packages?

[Emmanuel Arias]

On Thu, Feb 17, 2022 at 2:48 PM Louis-Philippe Véronneau 
wrote:

> On 2022-02-17 12 h 39, Sandro Tosi wrote:
> > Hello all,
> > the question is essentially all in the subject line, and my answer is
> yes.
> >
> > I receive notifications for all MRs opened against DPT packages, and
> > Janitor's are always pretty much ready to merge as is, and so i think
> > we should let Janitor commit directly to the team packages.
> >
> > Jelmer is in CC (not sure if he's subscribed), in case he wants to
> > chime in on the implication of this discussion.
> >
> > Regards,
>
> You sent a mail on the list on 2020-07-27 about this and the general
> consensus (3-4 replies) was that it was a good idea.
>
> Anyway, I also vote yes!
>

I also vote yes :-)


>
> --
>   ⢀⣴⠾⠻⢶⣦⠀
>   ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
>   ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
>   ⠈⠳⣄
>
>

Re: python-anyio failing testsuite on buildd, not locally

[Emmanuel Arias]

Hi,

Most of the tests that fail use *-ipv4 parameter. With ipv6 seems to be ok.
I don't know if that can give us some clues.

Cheers,

On Wed, Jan 19, 2022 at 12:52 PM Julien Puydt 
wrote:

> Hi,
>
> I check my packages in a schroot on my computer before uploading ; that
> way I detect problems like missing deps or network access, and I'm
> pretty confident things will go well on the buildd network.
>
> But today's upload of python-anyio is broken... and I'm clueless as to
> why. From the repeated error, it looks like 'localhost' isn't known,
> which doesn't make sense.
>
> Here is a link to the full log:
>
> https://buildd.debian.org/status/fetch.php?pkg=python-anyio=all=3.5.0-1=1642600026=0
>
> and a sample error:
>
> __ TestTCPListener.test_accept[asyncio-ipv4]
> ___
> tests/test_sockets.py:464: in test_accept
> async with await create_tcp_listener(local_host='localhost',
> family=family) as multi:
> anyio/_core/_sockets.py:236: in create_tcp_listener
> gai_res = await getaddrinfo(local_host, local_port, family=family,
> # type: ignore[arg-type]
> anyio/_core/_sockets.py:419: in getaddrinfo
> gai_res = await get_asynclib().getaddrinfo(encoded_host, port,
> family=family, type=type,
> anyio/_backends/_asyncio.py:1570: in getaddrinfo
> result = await get_running_loop().getaddrinfo(
> /usr/lib/python3.9/asyncio/base_events.py:856: in getaddrinfo
> return await self.run_in_executor(
> /usr/lib/python3.9/concurrent/futures/thread.py:58: in run
> result = self.fn(*self.args, **self.kwargs)
> /usr/lib/python3.9/asyncio/base_events.py:839: in _getaddrinfo_debug
> addrinfo = socket.getaddrinfo(host, port, family, type, proto,
> flags)
> /usr/lib/python3.9/socket.py:954: in getaddrinfo
> for res in _socket.getaddrinfo(host, port, family, type, proto,
> flags):
> E   socket.gaierror: [Errno -2] Name or service not known
>
> If someone has a lead on the issue...
>
> Thanks,
>
> J.Puydt
>
>

Re: Status of poetry

[Emmanuel Arias]

Hi!

On Fri, Dec 31, 2021 at 2:31 PM Taihsiang Ho (tai271828) 
wrote:

>
> More details regarding my testing if you are interested in:
> I was aware that the package with the fixed python 3.10 testing error[1]
> has been published when trying to fix the 3.10 testing error[1] during my
> Christmas holidays, so I gave the published package a try instead by using
> the binary deb.
>

Yes! Thanks for reporting the error, and yes, that was fixed by Sandro in
version 1.1.11+dfsg-3.


> The overall testing of the deb looks good for me. I used the binary deb
> "python3-poetry"[2] to re-build my blog, which is a pelican-based project
> managed by poetry, with Sid. I can smoothly re-build my blog and
> publish/host it with an Apache server.
>

That is amazing. Thanks for testing it!

Cheers!

Re: Request for review for Poetry(Was: Re: Asking for help Poetry)

[Emmanuel Arias]

Hi Tai,

First of all thanks for the mail, and for the work in the poetry package.
Very
detailed mail, amazing  :)

As mentioned Andrey, yes there's a test that failed with py3.10. The
package is
already in NEW, so we need to wait. In spite of this we can work to fix it.
I didn't investigate yet, So feel free to send a patch if you have one :).

For point [2] , call gbp with the b-depends are no longer needed, because
all of them
are already in Debian.

Cheers,
Emmanuel

On Fri, Nov 19, 2021 at 12:36 PM Taihsiang Ho (tai271828) 
wrote:

> Hi Andrey,
>
> Thank you for your information. I will have a look at the failure. If
> anyone has been working on this error, it would be appreciated to let me
> know how I can help.
>
> Besides, I found this thread
> https://lists.debian.org/debian-python/2021/11/msg00025.html soon after I
> sent out my previous email. I believe I have followed up the latest process
> and status of poetry packaging for now. My apologies for not checking the
> email threads carefully enough.
>
> -tai
>
> On Fri, Nov 19, 2021 at 4:19 PM Andrey Rahmatullin 
> wrote:
>
>> On Fri, Nov 19, 2021 at 03:54:48PM +0100, Taihsiang Ho (tai271828) wrote:
>> > [5] Some of the error messages from latest package source:
>> >
>> > short test summary info 
>> > 
>> > FAILED
>> tests/inspection/test_info.py::test_info_setup_complex_pep517_error
>> > - ...
>> > 1 failed, 587 passed, 5 skipped, 23 deselected, 15 warnings in 22.23s
>> > -
>> > 
>> > 588 passed, 5 skipped, 23 deselected, 14 warnings in 24.06s ==
>> > ==
>> > dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p
>> > "3.10 3.9" returned exit code 13
>> > make: *** [debian/rules:44: binary] Error 25
>> >
>> > dpkg-buildpackage: error: debian/rules binary subprocess returned exit
>> > status 2
>> Yes, one test fails with 3.10 which isn't unexpected because the package
>> wasn't tested with it.
>>
>> --
>> WBR, wRAR
>>
>

Status of poetry

[Emmanuel Arias]

Hello everybody,

I write to let you know that poetry (1.1.11) is already in NEW [0].

Thanks everybody for helping me to package it. Thanks pollo for
the first reviews. And a lot of thanks to morph to push me to finish
this work and for the sponsorship.

[0] https://ftp-master.debian.org/new/poetry_1.1.11+dfsg-1.html

Cheers,
Emmanuel

Bug#997970: RFP: linkify-it-py -- links recognition library with full unicode support

[Emmanuel Arias]

Package: wnpp
Severity: wishlist
X-Debbugs-Cc: debian-python@lists.debian.org

* Package name: linkify-it-py
  Version : 1.0.2
  Upstream Author : tsutsu3
* URL : https://github.com/tsutsu3/linkify-it-py
* License : expat
  Programming Lang: Python
  Description : links recognition library with full unicode support

Python port of linkify-it project. This markdown-it-py is a links
recognition library with full unicode support. This is focused on high
quality link pattern detection in plain text.
.
This package is used by markdown-it-py (see #997044), and this one is a
build dependency of myst-parser.
.
I plan mantain linkify-it-py under DPT umbrella.

Cheers,
Emmanuel

Bug#997044: ITP: markdown-it-py -- a Python port of markdown-it and some its associated plugins

[Emmanuel Arias]

Package: wnpp
Severity: wishlist
Owner: Emmanuel Arias 
X-Debbugs-Cc: debian-python@lists.debian.org

* Package name: markdown-it-py
  Version : 1.1.0
  Upstream Author : Chris Sewell 
* URL : https://github.com/executablebooks/markdown-it-py
* License : Expat
  Programming Lang: Python
  Description : a Python port of markdown-it and some its associated
plugins
.
markdown-it-py is a Python port of markdown-it and its associated plugins.
The
design philosophy of the port has been to change as little of the
fundamental code
structure (file names, function name, etc) as possible. just sprinkling in
a little Python
syntactic sugar.
.
I plan to maintain it under the DPT umbrella.


Chers,
Emmanuel

Re: request to join python-team/packages group on salsa

[Emmanuel Arias]

El lun, 11 de oct. de 2021 a la(s) 01:49, Nilesh Patra (
nil...@nileshpatra.info) escribió:

>
>
> On 11 October 2021 4:17:48 am IST, Emmanuel Arias <
> emmanuelaria...@gmail.com> wrote:
> >El dom, 10 de oct. de 2021 a la(s) 17:36, Afif Elghraoui (a...@debian.org
> )
> >escribió:
> >Hi,
> >
> >You need to be patient.
> >that a good exercise to understand the "upload process", also some DD
> >prefer
> >use mentors.
>
> Hi, Afif is already a DD since some years.
>

:O :/ \o/ so soorrry!

>
> @Afif, you might want to ping once on #debian-python IRC. Maybe someone
> could do it quickly that way.
>

+1


>
> Nilesh
>
> --
> Sent from my Android device with K-9 Mail. Please excuse my brevity.
>

Re: request to join python-team/packages group on salsa

[Emmanuel Arias]

El dom, 10 de oct. de 2021 a la(s) 17:36, Afif Elghraoui (a...@debian.org)
escribió:

>
>
> On 10/3/21 7:18 PM, Afif Elghraoui wrote:
> >
> >
> > On 10/3/21 6:50 PM, Sandro Tosi wrote:
> >>> I sometimes need to add or make updates to python packages. Currently,
> I
> >>> just uploaded a newer upstream version of httpbin and I'd like to push
> >>> the changes to the git repository, which resides in
> python-team/packages.
> >>
> >> httpbin has been orphaned, so it appears as if this repo should be
> >> moved from the python-team to the debian namespace (only admins can do
> >> that).
> >>
> >> please let us know if you still want to join the team.
> >>
> >
> > I'd still like to join.
> >
>
> ...so may I join? My salsa login again: afif
>
> thanks and regards
> Afif
>

Hi,

You need to be patient.

But meanwhile, you can proceed working in the package :) push it to your
own repository in salsa. Also you can upload it to
https://mentors.debian.net
that a good exercise to understand the "upload process", also some DD
prefer
use mentors.

If you push it to your salsa profile, please let us know to make some
review :)

Cheers,
eamanu

Re: Wiki: Debian Python Policy docu not on team site

[Emmanuel Arias]

Hi,

I added in the Wiki [0], the link to the python3-defaults
docs and policy [1].

Please review it.

[0] https://wiki.debian.org/Teams/PythonTeam#preview
[1] https://www.debian.org/doc/packaging-manuals/python-policy/

Cheers
Emmanuel

Re: Wiki: Debian Python Policy docu not on team site

[Emmanuel Arias]

Hi!

On Fri, Oct 1, 2021 at 7:43 AM  wrote:

> Hello,
>
> this is about the wiki page of that team.
> https://wiki.debian.org/Teams/PythonTeam
>
> I accidentally found the "Debian Python Policy documentation".
> https://www.debian.org/doc/packaging-manuals/python-policy/


Also we have this Policy [0]. But the python-policy that you mention
seems to be part of the docs of python3-defaults package.

Should we add it in the DPT wiki?

Cheers,
Emmanuel

[0]
https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst


>
> Looks nice and very important for new team members.
>
> Maybe it would help if it is linked on the team wiki page.
>
> Kind
> Christian Buhtz
>
>

Re: xlsxwriter: How to change homepage url

[Emmanuel Arias]

Hello everybody,

> This sounds like a task that should be taken by someone more
> experienced then me.

Looking in the salsa repo [0], it is very old. And that shouldn't happen. I
can updated
to the last unstable version tonight/tomorrow. If There's no objections.
Or, perhaps
Christian (the initial of this thread) can/want to do it (Christian, write
to me if you
need help)?

> So where does the "homepage" url in the "link" box on the right side of
> the tracker page comes from. And how can I fix it?

You need to modify the debian/control file on the "Homepage" key.

> btw: I am not sure if this list is the right place. But the DPMT is
> named as "uploaders" of that package. And I am confused about that the
> "maintainer" is a ubuntu-list (Team?).

That would be great, but I would leave it to the current maintainer to do
that, also seems
to be a group ¿?.  I cc to the maintainer(s).


[0] https://salsa.debian.org/python-team/packages/xlsxwriter

Cheers,
Emmanuel

Bug#993553: ITP: myst-parser -- rich and extensible flavor of Markdown meant for technical documentation and publishing

[Emmanuel Arias]

Package: wnpp
Severity: wishlist
Owner: Emmanuel Arias 
X-Debbugs-Cc: debian-python@lists.debian.org

* Package name: myst-parser
  Version : 0.15.2
  Upstream Author : Executable Book Project 
* URL : https://github.com/executablebooks/MyST-Parser
<https://github.com/manrajgrover/py-spinners>
* License : Expat
  Programming Lang: Python
  Description : rich and extensible flavor of Markdown meant for
technical documentation
and publishing
.
MyST is a flavor of markdown that is designed for simplicity, flexibility,
and extensibility. It contains
an extended CommonMark-compliant parser using markdown-it-py, as well as a
Sphinx extension
that allows you to write MyST Markdown in Sphinx.
.
I plan to maintain it under the DPT umbrella.

Chers,
Emmanuel

Re: How should learning to program in Python be approached, if learning objectives are sought to be customised?

[Emmanuel Arias]

Hi,

On Mon, Aug 30, 2021 at 12:24 PM Susmita/Rajib 
wrote:

> Thank you, Mr. Pokoradi, for your informative reply.
>
> I use either Knoppix or Debian. So everything is pre-installed.
>
> I don't know about pydev in Eclipse. So thank you for this bit of
> information. I am not sure if PyChem could be installed in my system.
> In Debian. So please advise,
>

I'm currently use Debian and PyCharm, you just need to download and use it.
I don't remember if I needed to install something, but I'm almost sure
that don't

>
> I am not a book person. I say they talk a lot and deliver very little.
> Tire me. I would rather like tough programs than beginners' programs
> that provide insights, while running on the system.
>
> Is there something similar to GDB (or DDD)?
>

pdb?

Cheers,
Emmanuel

>
> Thank you for your reply.
>
> Best.
> Rajib
>
>

Re: Request for review for Poetry(Was: Re: Asking for help Poetry)

[Emmanuel Arias]

Hello!!!

I just push some updates to salsa


Here are my comments:
>
> 1. d/control:
>
> You haven't set the Python Team either in Maintainer or Uploaders.
>
> Ready my bad! Also I note that some dependencies that I package for Poetry
were uploaded and DPT was not the Maintainer, I'll change those.

> -
>
> 2. d/control:
>
> If you require specific dependencies, you should make it clear in
> d/control. It's the kind of thing that helps a lot if people decide to
> backport it.
>
> Ready

> -
>
> 3. tests/repositories/fixtures
>
> This directory contains a bunch of tarballs from other projects. I'm not
> sure what should be done with this, as I guess they are used in the
> testsuite
>
> My first reflex would be to exclude them from the imported tarball and
> disable the tests that require them, but I don't know how much of the
> testsuite depends on those tarballs.
>
> Maybe someone else from the team can chime-in?
>
> I will look at that these days. I can try to remove them and "turn off"
the test
that uses the tarballs.  Some days ago, I started to look at the pypy
package,
and it has the suittest in another package (btw, that is new for me).
Maybe poetry can have that approach? Also, I don't know if that makes sense.

> -
>
> 4. d/tests
>
> There are no autopkgtests. This being a large project that's kinda hard
> to package, I don't really mind for now.
>
> I think it's fair to wait to have at least 1 version in unstable before
> working on that.
>
yes, that was my idea.

>
> -
>
> 5. d/rules
>
> Isn't the step in execute_after_dh_auto_install better suited in
> execute_after_dh_clean instead? At least, it seems to me you're cleaning
> the ./foo dir you patched in.
>
> yes you're right, that makes more sense, thanks!

> -
>
> 6. Lintian: W: python3-poetry: no-manual-page usr/bin/poetry
>
> Again, not something that needs to be fixed, but each subcommand of
> poetry should probably get a man page:
>
> https://python-poetry.org/docs/cli/
>
> I looked at the code and I have no idea how this website is built (they
> don't use sphinx). It seems like they do something manual?
>
> https://github.com/python-poetry/poetry/issues/3382
>
> Anyway, here's an example of how I added man pages to a program with
> multiple commands:
>
> https://github.com/spl0k/supysonic/tree/master/docs/man
>
>
thanks for note it, I'll take a look these days.

> -
>
> Overall it's very good! The trickiest part to fix will likely be #3 :S
>
> > I need to skip some tests because use a non versioned python, so that
> > give me some troubles like "python don't exist".
> >
> > Also, there're some package (or package version) that aren't in Debian
> > yet. So, to save your time looking which are them I tell you that I run
> > the buildpackage in this way:
> >
> > ```
> >
> > gbp buildpackage --git-ignore-new
> >
> --extra-package=/home/eamanu/Debian/DEPENDENCIES/python3-cleo_0.8.1-1_all.deb
> >
> --extra-package=/home/eamanu/Debian/DEPENDENCIES/python3-httpretty_1.0.5-0.1_all.deb
> >
> --extra-package=/home/eamanu/Debian/DEPENDENCIES/python3-pkginfo_1.7.0-1_all.deb
>
> This package has not been updated on Salsa, or at least, I couldn't find
> version 1.7.0-1 anywhere. Maybe you forgot to push?
>
> Oh yes, I'm just psuh to salsa. Sorry!


Cheers!
Emmanuel

Re: Python BoF at DebConf2021

[Emmanuel Arias]

On Sat, Aug 14, 2021 at 5:01 PM Louis-Philippe Véronneau 
wrote:

> On 2021-06-15 14 h 32, Louis-Philippe Véronneau wrote:
> > On 2021-06-12 16 h 20, Louis-Philippe Véronneau wrote:
> >> Hey folks,
> >>
> >> The deadline to submit talks for DebConf21 is June 20th and I was
> >> thinking it would be a good idea to have a Python BoF, as we always do.
> >>
> >> Anyone opposed to the idea?
> >>
> >
> > I've submitted the BoF. Chances are it will be approved :P
> >
>
> The Python BoF will be on Aug 27, from 21:00 to 21:45 UTC [1].
>
> Sadly, I have prior engagements and I won't be able to make it. Could
> someone else take on the task of coming up with an agenda and chairing
> the BoF?
>

oh :(. I hope somebody can do that (I will happy to do that, but my english
and expertise are not good)


> [1]: https://debconf21.debconf.org/talks/20-python-team-bof/
>
> --
>   ⢀⣴⠾⠻⢶⣦⠀
>   ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
>   ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
>   ⠈⠳⣄
>
>

Re: RFS: new version of sentry-python (#990519)

[Emmanuel Arias]

Hi,

Please, can you push to salsa the changes?

Thanks

Cheers,
Arias Emmanuel
@eamanu
yaerobi.com


On Mon, Aug 23, 2021 at 2:09 PM Eberhard Beilharz  wrote:

> Would someone please sponsor the new version of sentry-python (1.3.1)?
> The version currently available in Debian (0.13.2) is not compatible
> with the latest version and thus breaks any software that depends on the
> 1.x version.
>
> Thanks,
>  Eberhard
>
> https://mentors.debian.net/package/sentry-python/
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990519
>
>
>

Re: [RFC] DPT Policy: Canonise recommendation against PyPi-provided upstream source tarballs

[Emmanuel Arias]

Hola everybody,

On 6/26/21 7:51 PM, Louis-Philippe Véronneau wrote:
> To me, the most important thing is that all packages must at least run
> the upstream testsuite when it exists (I'm planning on writing a policy
> proposal saying this after the freeze). If PyPi releases include them, I
> think it's fine (but they often don't).

I was a little surprised because in all discussion anyone take account
the tests (or if a missed sorry) thanks pollo to get it in discussion. I
don't have the correct numbers but I saw  many python package without
autopkgtest, and if we package from PyPi, that don't contain the
testsuite, that result in packages with any test, and that isn't good.

Also, I'm not sure, but the docs aren't in PyPi, isn't?

In the other hand, files like .git* or CI files, can be easily remove
it. So, I don't see any problems with that.

cheers

-- 
Emmanuel Arias
@eamanu
yaerobi.com



OpenPGP_0xFA9DEC5DE11C63F1.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature

Re: RFS: colorzero/2.0-1 [ITP] -- Construct, convert, and manipulate colors in a Pythonic manner.

[Emmanuel Arias]

Hi

On 6/21/21 11:06 AM, Dave Jones wrote:
> Hi Emmanuel,
>
> On Sat, Jun 19, 2021 at 06:40:58PM -0300, Emmanuel Arias wrote:
>>
>> On 6/19/21 9:03 AM, Peter Green wrote:
>>> Just done some reviewing/tweaking. I've pushed the following changes
>>> to the git repo, please tell me if you have any objections.
>>>
>>> I added a gpb.conf to make git-buildpackage actually use pristine
>>> tar and hence result in an orig tarball that was consistent with
>>> what is already in Ubuntu.
>>
>> Also, you can try to follow DEP-14 (although is mark as candidate)
>> and add debian/master as default branch.
>
> Ah, this was something that confused me a bit when initially working
> on this. I'd read through DEP-14, but then figured a simple way to
> start would be to grab my existing packaging for Raspbian and use gbp
> import-dsc on it. This set up the repo with a "master" branch rather
> than "debian/master" and I then wondered if I'd mis-interpreted
> DEP-14's prescription to use "debian/master", and whether it meant one
> should use "debian" branch or alternatively a "master" branch.
I think that I don't understand you, sorry :(. But DEP-14 recommend the
use of /* for name the branchs, so for debian the branch should
be debian/*, for ubuntu ubuntu/*, etc.
>
> Anyway, given it should be "debian/master" I'll get that corrected (I
> assume I'm right in thinking that'll need a
> "debian-branch=debian/master" addition to gbp.conf).
>
yes. (and also create it first)
>> What about enable salsa-ci?
>
> Certainly something on the todo list, but not something I'd read up on
> yet. I'll have a look at that this afternoon.
>
I see that you already add the file. Don't forget activate ci in the
repository configuration :)

Cheers,

-- 
Emmanuel Arias
@eamanu
yaerobi.com



OpenPGP_0xFA9DEC5DE11C63F1.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature

Request for review for Poetry(Was: Re: Asking for help Poetry)

[Emmanuel Arias]

Hello everybody,

I want to tell you that I push to salsa an advances of poetry packaging.

Now, we have a complete package of poetry, so I'm requesting some more
experienced reviewers.

I need to skip some tests because use a non versioned python, so that
give me some troubles like "python don't exist".

Also, there're some package (or package version) that aren't in Debian
yet. So, to save your time looking which are them I tell you that I run
the buildpackage in this way:

```

gbp buildpackage --git-ignore-new
--extra-package=/home/eamanu/Debian/DEPENDENCIES/python3-cleo_0.8.1-1_all.deb
--extra-package=/home/eamanu/Debian/DEPENDENCIES/python3-httpretty_1.0.5-0.1_all.deb
--extra-package=/home/eamanu/Debian/DEPENDENCIES/python3-pkginfo_1.7.0-1_all.deb

```


Thanks for your help :)

Cheers,


-- 

Emmanuel Arias
@eamanu
yaerobi.com



OpenPGP_0xFA9DEC5DE11C63F1.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature

Re: RFS: colorzero/2.0-1 [ITP] -- Construct, convert, and manipulate colors in a Pythonic manner.

[Emmanuel Arias]

On 6/19/21 9:03 AM, Peter Green wrote:
> Just done some reviewing/tweaking. I've pushed the following changes
> to the git repo, please
> tell me if you have any objections.
>
> I added a gpb.conf to make git-buildpackage actually use pristine tar
> and hence result in an orig
> tarball that was consistent with what is already in Ubuntu.

Also, you can try to follow DEP-14 (although is mark as candidate) and
add debian/master as default branch.

What about enable salsa-ci?

> Finally would you consider adding me as a co-maintainer.
You are in the DPT so you already are a co-maintainer. You can add you
as uploaders I guess.


Cheers,


-- 
Emmanuel Arias
@eamanu
yaerobi.com



OpenPGP_0xFA9DEC5DE11C63F1.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature

Re: Python BoF at DebConf2021

[Emmanuel Arias]

On Sat, Jun 12, 2021 at 5:20 PM Louis-Philippe Véronneau 
wrote:

> Hey folks,
>
> The deadline to submit talks for DebConf21 is June 20th and I was
> thinking it would be a good idea to have a Python BoF, as we always do.
>

Amazing! Thanks!

>
> Anyone opposed to the idea?
>
> --
>   ⢀⣴⠾⠻⢶⣦⠀
>   ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
>   ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
>   ⠈⠳⣄
>
>

Re: RFS: python-click-log/0.3.2-1 -- Logging integration for Click - Python 3.x

[Emmanuel Arias]

Hi,

I'm not DD, but I send you some review, to gain time:

* d/changelog says: `Bump debhelper from old 10 to 12.` but actually
debhelper-compat version is 13.
* Please use UNRELEASED instead of unstable, that can be confused.
* What about enable salsa-ci?
* What about adding an autopkgtest?

Cheers,

El vie, 4 de jun. de 2021 a la(s) 20:30, Fabrice Bauzac-Stehly (
n...@mykolab.com) escribió:

> Package: sponsorship-requests
> Severity: normal
>
> Dear mentors,
>
> I am looking for a sponsor for my package "python-click-log":
>
>  * Package name: python-click-log
>Version : 0.3.2-1
>Upstream Author : [fill in name and email of upstream]
>  * URL : https://github.com/click-contrib/click-log
>  * License : Expat
>  * Vcs :
> https://salsa.debian.org/python-team/packages/python-click-log
>Section : python
>
> It builds those binary packages:
>
>   python3-click-log - Logging integration for Click - Python 3.x
>
> To access further information about this package, please visit the
> following URL:
>
>   https://mentors.debian.net/package/python-click-log/
>
> Alternatively, one can download the package with dget using this command:
>
>   dget -x
> https://mentors.debian.net/debian/pool/main/p/python-click-log/python-click-log_0.3.2-1.dsc
>
> Changes since the last upload:
>
>  python-click-log (0.3.2-1) unstable; urgency=medium
>  .
>[ Debian Janitor ]
>* Bump debhelper from old 10 to 12.
>* Set upstream metadata fields: Bug-Database, Repository, Repository-
>  Browse.
>* Remove constraints unnecessary since stretch:
>  + Build-Depends: Drop versioned constraint on dh-python.
>  .
>[ Ondřej Nový ]
>* d/control: Update Maintainer field with new Debian Python Team
>  contact address.
>* d/control: Update Vcs-* fields with new Debian Python Team Salsa
>  layout.
>  .
>[ Fabrice Bauzac-Stehly ]
>* New upstream release.
>* Upgrade d/watch to version 4.
>* Upgrade the Standards-Version to 4.5.1.
>* Declare Rules-Requires-Root: no.
>
> Best regards
>
> --
> Fabrice Bauzac-Stehly
> PGP 01EEACF8244E9C14B551C5256ADA5F189BD322B6
>
>

Bug#989471: python-pytest-lazy-fixture: New upstream release 0.6.3

[Emmanuel Arias]

Source: python-pytest-lazy-fixture
Severity: wishlist
X-Debbugs-Cc: debian-python@lists.debian.org

Hello Team, 

New upstream release is need for marshmallow-sqlalchemy new version.
I've just push the new upstream release to salsa, but I left this bugs
open until freeze end and anyone can sponsorship it. 

Cheers,


-- System Information:
Debian Release: 11.0
  APT prefers testing
  APT policy: (990, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-6-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Re: Asking for help Poetry

[Emmanuel Arias]

Hello Everybody,

I left some advances on poetry. Happily (from my point of view) we are near
to
having poetry packaged. I've just push some new commits to salsa [0].

After spend several times with the tests (see patches), we just have two
test that still fail (I didn't looking it yet):

tests/installation/test_pip_installer.py - fail one unit test
tests/utils/test_env.py -  fail several unit tests.

To build poetry, you will also need to build locally python3-cleo still in
NEW [1], python-httpretty 1.0.5:
I prepare a new upstream release and a member of OpenStack sponsored its  to
experimental (thanks Michal Arbet) [2] and pkginfo 1.7.0, I ping @jandd on
#debian-python
for a new upstream release packaging, but if I haven't got news about it
these days, I will push
my work and I'll ask for sponsorship.

[0] https://salsa.debian.org/python-team/packages/poetry
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958366
[2]
https://tracker.debian.org/news/1241115/accepted-python-httpretty-105-01-source-into-experimental/

Cheers,
Emmanuel

On Tue, May 11, 2021 at 8:55 AM Emmanuel Arias  wrote:

> Hello!
>
> On 5/11/21 1:25 AM, Sandro Tosi wrote:
> > On Sat, May 8, 2021 at 9:56 PM Emmanuel Arias 
> wrote:
> >> On 5/8/21 10:37 PM, Sandro Tosi wrote:
> >>> On Mon, Mar 15, 2021 at 10:29 AM Emmanuel Arias 
> wrote:
> >>>> On Mon, Mar 15, 2021 at 4:22 AM Sandro Tosi  wrote:
> >>>>>> * poetry-core failing https://ci.debian.net/packages/p/poetry-core/
> >>>>> are you handling this failure?
> >>> looks like this is fixed in git: do you need a sponsor?
> >> Yes, please. Thanks!
> > sounds good, i'll have a look at this package soon and let you know
> Thanks!
> >
> >>>>>> * python-cleo in review
> https://salsa.debian.org/python-team/packages/cleo I hope finished this
> week
> >>> stefanor uploaded it a few days ago
> >> Yes.
> >>>>>> * poetry still in progress
> https://salsa.debian.org/python-team/packages/poetry -> need help and
> reviews
> >>> for this one it looks like you imported a new upstream release a week
> >>> ago: is there something we can help/check about poetry?
> >> I've just push some advances. Currently, I'm working on tests, if you
> >> want to take a look.
> > maybe just ask here (or directly to me) if you have questions and
> > what's failing/needs work, so we dont duplicate work
> ok!
> >
> >> We need new upstream release for python-httpretty (for tests), that I
> >> upload to mentors [0]. @zigo ask me about test that this new upstream
> >> release doesn't break
> >> cloud-init and python3-scciclient (I would like to take a look to ratt
> >> for that).
> > ratt is pretty great, and rather simple to use:
> >
> > - setup a sbuild schroot for unstable
> > - build a binary package from the source you're working on
> > - `ratt _amd64.changes`
> >
> > and then you'll get on screen the results for each package + a
> > directory with the build results and logs
> >
> > https://github.com/Debian/ratt
> >
> > keep in mind it rebuilds packages sequentially, so it can take some
> > time if the number of reverse deps is high.
>
> Thanks for the advice!
>
> >
> >> Perhaps a good help from a more experienced person would be check if all
> >> is ok with DFSG,that's my biggest concern.
> > for which package specifically? while it's boring and long work, it's
> > also rather trivial: look at every single file (yep, all of them) from
> > the upstream source, and document their copyright and license in
> > d/copyright -- happy to answer questions if you have something
> > specific in mind about this
>
> Thanks, I hope have more news at the finish of the week
>
> Cheers!
>
>
> >
> > Regards,
>

Re: Asking for help Poetry

[Emmanuel Arias]

Hello!

On 5/11/21 1:25 AM, Sandro Tosi wrote:
> On Sat, May 8, 2021 at 9:56 PM Emmanuel Arias  wrote:
>> On 5/8/21 10:37 PM, Sandro Tosi wrote:
>>> On Mon, Mar 15, 2021 at 10:29 AM Emmanuel Arias  wrote:
>>>> On Mon, Mar 15, 2021 at 4:22 AM Sandro Tosi  wrote:
>>>>>> * poetry-core failing https://ci.debian.net/packages/p/poetry-core/
>>>>> are you handling this failure?
>>> looks like this is fixed in git: do you need a sponsor?
>> Yes, please. Thanks!
> sounds good, i'll have a look at this package soon and let you know
Thanks!
>
>>>>>> * python-cleo in review 
>>>>>> https://salsa.debian.org/python-team/packages/cleo I hope finished this 
>>>>>> week
>>> stefanor uploaded it a few days ago
>> Yes.
>>>>>> * poetry still in progress 
>>>>>> https://salsa.debian.org/python-team/packages/poetry -> need help and 
>>>>>> reviews
>>> for this one it looks like you imported a new upstream release a week
>>> ago: is there something we can help/check about poetry?
>> I've just push some advances. Currently, I'm working on tests, if you
>> want to take a look.
> maybe just ask here (or directly to me) if you have questions and
> what's failing/needs work, so we dont duplicate work
ok!
>
>> We need new upstream release for python-httpretty (for tests), that I
>> upload to mentors [0]. @zigo ask me about test that this new upstream
>> release doesn't break
>> cloud-init and python3-scciclient (I would like to take a look to ratt
>> for that).
> ratt is pretty great, and rather simple to use:
>
> - setup a sbuild schroot for unstable
> - build a binary package from the source you're working on
> - `ratt _amd64.changes`
>
> and then you'll get on screen the results for each package + a
> directory with the build results and logs
>
> https://github.com/Debian/ratt
>
> keep in mind it rebuilds packages sequentially, so it can take some
> time if the number of reverse deps is high.

Thanks for the advice!

>
>> Perhaps a good help from a more experienced person would be check if all
>> is ok with DFSG,that's my biggest concern.
> for which package specifically? while it's boring and long work, it's
> also rather trivial: look at every single file (yep, all of them) from
> the upstream source, and document their copyright and license in
> d/copyright -- happy to answer questions if you have something
> specific in mind about this

Thanks, I hope have more news at the finish of the week

Cheers!


>
> Regards,


OpenPGP_0xFA9DEC5DE11C63F1.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature

Re: Asking for help Poetry

[Emmanuel Arias]

Hello Sandro,


Thanks for write me.

On 5/8/21 10:37 PM, Sandro Tosi wrote:
> On Mon, Mar 15, 2021 at 10:29 AM Emmanuel Arias  wrote:
>> On Mon, Mar 15, 2021 at 4:22 AM Sandro Tosi  wrote:
>>>> * poetry-core failing https://ci.debian.net/packages/p/poetry-core/
>>> are you handling this failure?
> looks like this is fixed in git: do you need a sponsor?
Yes, please. Thanks!
>>>> * python-cleo in review https://salsa.debian.org/python-team/packages/cleo 
>>>> I hope finished this week
> stefanor uploaded it a few days ago
Yes.
>>>> * poetry still in progress 
>>>> https://salsa.debian.org/python-team/packages/poetry -> need help and 
>>>> reviews
> for this one it looks like you imported a new upstream release a week
> ago: is there something we can help/check about poetry?

I've just push some advances. Currently, I'm working on tests, if you
want to take a look.

We need new upstream release for python-httpretty (for tests), that I
upload to mentors [0]. @zigo ask me about test that this new upstream
release doesn't break
cloud-init and python3-scciclient (I would like to take a look to ratt
for that).

Perhaps a good help from a more experienced person would be check if all
is ok with DFSG,that's my biggest concern.

[0] https://mentors.debian.net/package/python-httpretty/

Cheers!

Emmanuel



OpenPGP_0xFA9DEC5DE11C63F1.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature

Bug#986205: RFS: python-cleo/0.8.1-1 [ITP] -- create beautiful and testable command-line interfaces

[Emmanuel Arias]

Package: sponsorship-requests
Severity: wishlist
X-Debbugs-Cc: debian-python@lists.debian.org

Dear mentors,

I am looking for a sponsor for my package "python-cleo":

 * Package name: python-cleo
   Version : 0.8.1-1
   Upstream Author : Sébastien Eustace 
 * URL : https://github.com/sdispater/cleo
 * License : expat
 * Vcs :
https://salsa.debian.org/python-team/packages/python-cleo
   Section : python

It builds those binary packages:

  python-cleo-doc - create beautiful and testable command-line interfaces
(documentation)
  python3-cleo - create beautiful and testable command-line interfaces

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

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

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

  dget -x
https://mentors.debian.net/debian/pool/main/p/python-cleo/python-cleo_0.8.1-1.dsc

Changes for the initial release:

 python-cleo (0.8.1-1) unstable; urgency=medium
 .
   * Initial release (Closes: #958366)

Regards,
-- 
  Emmanuel Arias

Re: Asking for help Poetry

[Emmanuel Arias]

Hi,

On Mon, Mar 15, 2021 at 4:22 AM Sandro Tosi  wrote:

> > * poetry-core failing https://ci.debian.net/packages/p/poetry-core/
>
> are you handling this failure?
>
> > * python-cleo in review
> https://salsa.debian.org/python-team/packages/cleo I hope finished this
> week
> > * poetry still in progress
> https://salsa.debian.org/python-team/packages/poetry -> need help and
> reviews
>
> what kind of help do you need here?
>

Basically, with tests. There're so many setup.py on tests cases and we
should identify
if that test has some internet connections or not.  Also, each setup.py has
its Copyright and License
so that should be added to d/copyright, or repack?

Cheers,
Emmanuel

>
> --
> Sandro "morph" Tosi
> My website: http://sandrotosi.me/
> Me at Debian: http://wiki.debian.org/SandroTosi
> Twitter: https://twitter.com/sandrotosi
>

Re: Asking for help Poetry

[Emmanuel Arias]

On Mon, Mar 15, 2021 at 5:50 AM Bastian Venthur  wrote:

> Hi Emmanuel,
>
> I find it amazing that you went through all the hassle of un-bundeling
> and actually packaging all the dependencies for poetry!
>
>
> Good job and thank you very much for your efforts!
>

Thanks!!

>
> Bastian
>
> --
> Dr. Bastian Venthur https://venthur.de
> Debian Developer venthur at debian org
>
>

Re: Bug#985102: RFS: jupyter-packaging/0.7.12-1 [ITP] -- tools to help build and install Jupyter Python packages

[Emmanuel Arias]

Hi thanks!
On Sat, Mar 13, 2021 at 3:57 AM Nilesh Patra  wrote:

> Hi,
>
> I uploaded the one on salsa. It looked nice to me.
> I am closing the RFS bug, then.
> Thanks a lot for your work on this!
>
> PS: Next time, please consider to first import, and then commit all your
> changes systematically - for example, adding autopkgtests, modifying
> copyright et. al. rather than a huge bulk of changes in "initial
> commit"
>
> Thanks for the advice.

Cheers,
Emmanuel

> Nilesh
>
>

Re: Asking for help Poetry

[Emmanuel Arias]

Hi everyone,

I leave an update about poetry packaging status.

* poetry-core failing https://ci.debian.net/packages/p/poetry-core/
* pastel in testing https://tracker.debian.org/pkg/pastel
* pylev in testing https://tracker.debian.org/pkg/pylev
* crashtest in testing https://tracker.debian.org/pkg/crashtest
* clikit in testing https://tracker.debian.org/pkg/clikit
* shellingham in testing https://tracker.debian.org/pkg/shellingham

* python-cleo in review https://salsa.debian.org/python-team/packages/cleo
I hope finished this week
* poetry still in progress
https://salsa.debian.org/python-team/packages/poetry -> need help and
reviews

My goal is to finish poetry package before april.

Cheers,
Emmanuel

On Fri, Mar 12, 2021 at 2:03 PM Sandro Tosi  wrote:

> Hello Emmanuel,
>
> > From the missing dependencies we have:
> > * poetry-core in NEW [0]
> > * pastel in NEW need for clikit [1]
> > * pylev in NEW need for clikit [2]
> > * crashtest has RFS need for clikit [3]
> > * clikit is ready on salsa but waiting for crashtest before RFS [4]
> > * cleo ready but waiting for clikit [5]
> > * shellingham not ready nor ITP yet.
> > * poetry some advances on salsa [6]
> >
> > For experience in the other packages (pylev, paste, etc) and for
> recommendation of DDs,
> > poetry package use upstream github repository where we have important
> things like
> > tests. I was looking and exist lot of setup.py that makes me think that
> we will need
> > repack the upstream package.
> >
> > I will continue working on it but after my reset week, I will be offline
> until 9 january
>
> can you provide a status update on poetry packaging? more and more
> upstreams are moving (or planning) to poetry, so having it available
> asap is definitely important.
>
> Regards,
> --
> Sandro "morph" Tosi
> My website: http://sandrotosi.me/
> Me at Debian: http://wiki.debian.org/SandroTosi
> Twitter: https://twitter.com/sandrotosi
>

Bug#985102: RFS: jupyter-packaging/0.7.12-1 [ITP] -- tools to help build and install Jupyter Python packages

[Emmanuel Arias]

Package: sponsorship-requests
Severity: wishlist
X-Debbugs-Cc: debian-python@lists.debian.org

Dear mentors,

I am looking for a sponsor for my package "jupyter-packaging":

 * Package name: jupyter-packaging
   Version : 0.7.12-1
   Upstream Author : Project Jupyter 
 * URL : https://github.com/jupyter/jupyter-packaging
 * License : BSD-3-Clause
 * Vcs :
https://salsa.debian.org/python-team/packages/jupyter-packaging
   Section : python

It builds those binary packages:

  python3-jupyter-packaging - tools to help build and install Jupyter
Python packages

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

  https://mentors.debian.net/package/jupyter-packaging/

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

  dget -x
https://mentors.debian.net/debian/pool/main/j/jupyter-packaging/jupyter-packaging_0.7.12-1.dsc

Changes for the initial release:

 jupyter-packaging (0.7.12-1) unstable; urgency=low
 .
   * Initial release (Closes: #985077)

Regards,
-- 
  Emmanuel Arias

Bug#985077: ITP: jupyter-packaging -- tools to help build and install Jupyter Python packages

[Emmanuel Arias]

Package: wnpp
Severity: wishlist
Owner: Emmanuel Arias 
X-Debbugs-Cc: debian-python@lists.debian.org

* Package name: jupyter-packaging
  Version : 0.7.12
  Upstream Author : Project Jupyter 
* URL : https://github.com/jupyter/jupyter-packaging
* License : BSD-3-Clause
  Programming Lang: Python
  Description : tools to help build and install Jupyter Python packages

tool to help with the building and installation of Jupyter Python packages.
This tool is starting to be used for many Jupyter Python packages.
.
This package is needed to package ipytree (see #985001).
.
This package will be maintained as part of the Debian Python modules team.

Cheers,
Emmanuel

Bug#985001: ITP: ipytree -- a tree widget using Jupyter-widget protocol and jsTree

[Emmanuel Arias]

Package: wnpp
Severity: wishlist
Owner: Emmanuel Arias 
X-Debbugs-Cc: debian-python@lists.debian.org

* Package name    : ipytree
  Version         : 0.2.1
  Upstream Author : Martin Renou 
* URL             : https://github.com/QuantStack/ipytree
* License         : MIT
  Programming Lang: Python
  Description     : a Tree Widget using Jupyter-widgets protocol and jsTree

Widget that allow create trees for visualization on Jupyter. This
package use Jupyter-widgets protocol and jsTree.
.
This package is need to fix #979625.
.
This package will be maintained as part of the Debian Python modules team.

Cheers,
Emmanuel

Re: How can I override module name in autopkgtest-pkg-python

[Emmanuel Arias]

I note that my last mail can be confuse

The use of debian/tests/pkg-python/import-name is deprecated.

But the use of debian/tests/autopkgtest-pkg-python.conf is
mentioned on man autodep8. So this can be used.

On Wed, Mar 3, 2021 at 7:15 PM Emmanuel Arias  wrote:

> Hi,
>
> Maybe this can be useful [0] but that is deprecated. You can create
> debian/tests/autopkgtest-pkg-python.conf file and use import_name
> variable to change the name. Here an example [1]
>
>
> [0] https://salsa.debian.org/ci-team/autodep8/-/merge_requests/17
> [1]
> https://salsa.debian.org/python-team/packages/python-xlib/-/blob/master/debian/tests/autopkgtest-pkg-python.conf
>
> Cheers,
> Emmanuel
>
> On Wed, Mar 3, 2021 at 5:49 PM Gregor Riepl  wrote:
>
>> > autopkgtest [19:46:36]: test autodep8-python3: set -e ; for py in
>> $(py3versions -r 2>/dev/null) ; do cd "$AUTOPKGTEST_TMP" ; echo "Testing
>> with $py:" ; $py -c "import cython_blis; print(cython_blis)" ; done
>> > autopkgtest [19:46:36]: test autodep8-python3: [---
>> > Testing with python3.9:
>> > Traceback (most recent call last):
>> >   File "", line 1, in 
>> > ModuleNotFoundError: No module named 'cython_blis'
>> > autopkgtest [19:46:37]: test autodep8-python3: ---]
>> >
>> >
>> > The actual module that needs to be importet is just blis.  How can
>> > I teach autodep8-python3 the correct module name?
>>
>> Simply write a suitable debian/tests/control file that uses
>>
>> import blis; print(blis)
>>
>> instead of
>>
>> import cython_blis; print(cython_blis)
>>
>> See here for an example:
>>
>> https://salsa.debian.org/3dprinting-team/libarcus/-/blob/master/debian/tests/control
>>
>> Although, it looks like this sort of trivial autopkgtest is now
>> considered "superficial" and will no longer reduce the time until a
>> package is autopromoted to testing.
>>
>>

Re: How can I override module name in autopkgtest-pkg-python

[Emmanuel Arias]

Hi,

Maybe this can be useful [0] but that is deprecated. You can create
debian/tests/autopkgtest-pkg-python.conf file and use import_name
variable to change the name. Here an example [1]


[0] https://salsa.debian.org/ci-team/autodep8/-/merge_requests/17
[1]
https://salsa.debian.org/python-team/packages/python-xlib/-/blob/master/debian/tests/autopkgtest-pkg-python.conf

Cheers,
Emmanuel

On Wed, Mar 3, 2021 at 5:49 PM Gregor Riepl  wrote:

> > autopkgtest [19:46:36]: test autodep8-python3: set -e ; for py in
> $(py3versions -r 2>/dev/null) ; do cd "$AUTOPKGTEST_TMP" ; echo "Testing
> with $py:" ; $py -c "import cython_blis; print(cython_blis)" ; done
> > autopkgtest [19:46:36]: test autodep8-python3: [---
> > Testing with python3.9:
> > Traceback (most recent call last):
> >   File "", line 1, in 
> > ModuleNotFoundError: No module named 'cython_blis'
> > autopkgtest [19:46:37]: test autodep8-python3: ---]
> >
> >
> > The actual module that needs to be importet is just blis.  How can
> > I teach autodep8-python3 the correct module name?
>
> Simply write a suitable debian/tests/control file that uses
>
> import blis; print(blis)
>
> instead of
>
> import cython_blis; print(cython_blis)
>
> See here for an example:
>
> https://salsa.debian.org/3dprinting-team/libarcus/-/blob/master/debian/tests/control
>
> Although, it looks like this sort of trivial autopkgtest is now
> considered "superficial" and will no longer reduce the time until a
> package is autopromoted to testing.
>
>

Re: Ressurrecting freevial as the new upstream

[Emmanuel Arias]

Hi!

> It turns out that I personally know the people behind freevial
> because it was born as a game for the Catalan Ubuntu LoCoTeam,
> which I was part of some time back. So I contacted the main
> developer and he agreed for me to take over the project and
> try[2] to port it to Python 3.

Interesting project, I've never see (in my short life in FOSS projects)
freevial but sound awesome.

> 
> My python3 branch[3] currently works fine, though the code still
> needs more refactoring to make it fit Python 3 style guides. I'm
> also trying to build the package myself but I've never packaged a
> Python program before and it doesn't build successfully so far.>
> Now I'm wondering if your team would like to keep maintaining
> freevial or should I join your team and take care of it myself
> (I don't plan to maintain any other Python packages for now).

Personally, this weeks I cannot work on freevial, but next week I will
happy to help on packaging and maintain it.

But you can join to the team
https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst

Cheers,
Emmanuel


OpenPGP_0xFA9DEC5DE11C63F1.asc
Description: application/pgp-keys


OpenPGP_signature
Description: OpenPGP digital signature

Re: Requesting adopter for Lollypop

[Emmanuel Arias]

> However:
> - I am not a DPT member, so would need to be granted some privileges on the
> salsa repo (my username is hntourne). Maybe I should apply for that, since
> I
> maintain already about a dozen packages under the DPT umbrella, but that's
> not
> really related to this RFA.
>
Hi, you can join to the team :)
https://salsa.debian.org/python-team/tools/python-modules/-/blob/master/policy.rst

Re: python3-mastodon fails CI due to bad magic?

[Emmanuel Arias]

Seems that reprotest on salsa, is not installing the python3-magic.

I don't think that can be a problem with cpython.

On Thu, Jan 28, 2021 at 8:39 AM Håvard Flaget Aasen 
wrote:

> tor. 28. jan. 2021 kl. 10:48 skrev Craig Small :
> >
> > Hi,
> > I'm trying to understand why python3-mastodon fails the unit tests.
>
> I'm not sure what you found out so far. When I grepped the log you
> linked, I  couldn't find python3-magic or libmagic. I believe the
> packages isn't installed and the test therefore fails.
> I'm guessing now, but I think this has to do with reproducible build in
> salsa.
>
> >
> > An example is at [1] and it seems that importing magic is enough to
> trigger it. The compat line is to handle both python3-magic and a libmagic
> module both wanting magic.
> >
> > Is this a cpython thing? I'm not sure what I can do to fix this.
> >
> >   File
> "/tmp/reprotest.7a4W2G/build-experiment-1/build-experiment-1/.pybuild/cpython3_3.9_mastodon/build/mastodon/Mastodon.py",
> line 55, in 
> > import magic
> >   File "/usr/lib/python3/dist-packages/magic/__init__.py", line 361, in
> 
> > add_compat(globals())
> >   File "/usr/lib/python3/dist-packages/magic/__init__.py", line 325, in
> add_compat
> > from magic import compat
> >   File "/usr/lib/python3/dist-packages/magic/compat.py", line 61, in
> 
> > _open = _libraries['magic'].magic_open
> >   File "/usr/lib/python3.9/ctypes/__init__.py", line 387, in __getattr__
> > func = self.__getitem__(name)
> >   File "/usr/lib/python3.9/ctypes/__init__.py", line 392, in __getitem__
> > func = self._FuncPtr((name_or_ordinal, self))
> > AttributeError: python3.9: undefined symbol: magic_open
> >
> >
> >
> >
> >
> > 1: https://salsa.debian.org/python-team/packages/mastodon/-/jobs/1312190
> >
>
>

Bug#980562: RFS: shellingham/1.3.2-1 [ITP] -- Tool to Detect Surrounding Shell

[Emmanuel Arias]

Package: sponsorship-requests
Severity: wishlist
X-Debbugs-Cc: debian-python@lists.debian.org

Dear mentors,

I am looking for a sponsor for my package "shellingham":

 * Package name: shellingham
   Version : 1.3.2-1
   Upstream Author : Tzu-ping Chung 
 * URL : https://github.com/sarugaku/shellingham
 * License : ISC
 * Vcs :
https://salsa.debian.org/python-team/packages/shellingham
   Section : python

It builds those binary packages:

  python3-shellingham - Tool to Detect Surrounding Shell

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

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

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

  dget -x
https://mentors.debian.net/debian/pool/main/s/shellingham/shellingham_1.3.2-1.dsc

Changes for the initial release:

 shellingham (1.3.2-1) unstable; urgency=medium
 .
   * Initial release (Closes: #980483)

Regards,
-- 
  Emmanuel Arias

Bug#980483: ITP: shellingham -- Tool to Detect Surrounding Shell

[Emmanuel Arias]

Package: wnpp
Severity: wishlist
Owner: Emmanuel Arias 
X-Debbugs-Cc: debian-python@lists.debian.org

* Package name: shellingham
  Version : 1.3.2
  Upstream Author : Tzu-ping Chung 
* URL : https://github.com/sarugaku/shellingham
* License : ISC License
  Programming Lang: Python
  Description :  Tool to Detect Surrounding Shell

Shellingham detects what shell the current Python executable is running in.
.
This package is needed for poetry packaging.
.
This package will be maintained as part of the Debian Python modules team.

Cheers,
Emmanuel

Bug#980008: RFS: clikit/0.6.2-1 [ITP] -- utilities to build beautiful command lines interfaces

[Emmanuel Arias]

Package: sponsorship-requests
Severity: wishlist
X-Debbugs-Cc: debian-python@lists.debian.org

Dear mentors,

I am looking for a sponsor for my package "clikit":

 * Package name: clikit
   Version : 0.6.2-1
   Upstream Author : Sébastien Eustace 
 * URL : https://github.com/sdispater/clikit
 * License : expat
 * Vcs : https://salsa.debian.org/python-team/packages/clikit
   Section : python

It builds those binary packages:

  python3-clikit - utilities to build beautiful command lines interfaces

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

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

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

  dget -x
https://mentors.debian.net/debian/pool/main/c/clikit/clikit_0.6.2-1.dsc

Changes for the initial release:

 clikit (0.6.2-1) unstable; urgency=medium
 .
   * Initial release (Closes: #977675)

Regards,
-- 
  Emmanuel Arias

Re: Looking for a Sponsor - Papereshaper

[Emmanuel Arias]

Hi,

After read [0] I'm a little confused. Do you want to package gpapershaper
by yourself? or do you want someone to package papershaper?

Because, the subject of this mail is "looking for a sponsor", but when you
look for a sponsor that means that you already have the Debian package
and need a Debian Developer review and upload. Commonly this is the ITP
(intent to package) way*.

If you send a RFP (request for package) you are looking for someone else
(volunteer) to create the Debian package.

* Just to not confuse, you need a sponsor for other tasks, but
I'm talking about this situation, for instance.

[0] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976174

On Wed, Dec 30, 2020 at 1:50 PM Devops PK Carlisle LLC <
dev...@pkcarlisle.com> wrote:

> I wrote a small Python utility for wallpaper swapping, it has been
> working flawlessly for a couple of years on my Linux boxes, and I am
> looking to include it in Debian.
>
> I have spent the last week or so tweaking docs and comments to be as
> Debian package friendly as I know how, I have a git uploaded, and an RFP
> submitted, and at this point I should probably stop messing with it and
> ask about a sponsor.
>
> The RFP is here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976174
>
> The git is here: https://github.com/pkcarlislellc/git-papershaper
>
> Thanks!
>
>

Bug#978702: RFS: crashtest/0.3.1-1 [ITP] -- makes exceptions handling and inspection easier

[Emmanuel Arias]

Package: sponsorship-requests
Severity: wishlist
X-Debbugs-Cc: debian-python@lists.debian.org

Dear mentors,

I am looking for a sponsor for my package "crashtest":

 * Package name: crashtest
   Version : 0.3.1-1
   Upstream Author : Sébastien Eustace 
 * URL : https://github.com/sdispater/crashtest
 * License : expat
 * Vcs : https://salsa.debian.org/python-team/packages/crashtest
   Section : python

It builds those binary packages:

  python3-crashtest - makes exceptions handling and inspection easier

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

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

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

  dget -x
https://mentors.debian.net/debian/pool/main/c/crashtest/crashtest_0.3.1-1.dsc

Changes for the initial release:

 crashtest (0.3.1-1) unstable; urgency=medium
 .
   * Initial release (Closes: #977917)

Regards,
-- 
  Emmanuel Arias

Bug#977917: ITP: crashtest -- makes exceptions handling and inspection easier

[Emmanuel Arias]

Package: wnpp
Severity: wishlist
Owner: Emmanuel Arias 
X-Debbugs-Cc: debian-python@lists.debian.org

* Package name: crashtest
  Version : 0.3.1
  Upstream Author : Sébastien Eustace 
* URL : https://github.com/sdispater/crashtest
* License : MIT
  Programming Lang: Python
  Description :  makes exceptions handling and inspection easier

Python library that makes exceptions handling and inspection easier.
.
This is a dependency of clickit's tests.
.
This package is needed for poetry packaging.
.
This package will be maintained as part of the Debian Python modules team.

Cheers,
Emmanuel

Bug#977850: RFS: pylev/1.2.0-1 [ITP] -- pure Python Levenshtein implementation

[Emmanuel Arias]

Package: sponsorship-requests
Severity: wishlist
X-Debbugs-Cc: debian-python@lists.debian.org

Dear mentors,

I am looking for a sponsor for my package "pylev":

 * Package name: pylev
   Version : 1.2.0-1
   Upstream Author : Daniel Lindsley 
 * URL : https://github.com/toastdriven/pylev
 * License : BSD-3-Clause
 * Vcs : https://salsa.debian.org/python-team/packages/pylev
   Section : python

It builds those binary packages:

  python3-pylev - pure Python Levenshtein implementation

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

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

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

  dget -x
https://mentors.debian.net/debian/pool/main/p/pylev/pylev_1.2.0-1.dsc

Changes for the initial release:

 pylev (1.2.0-1) unstable; urgency=medium
 .
   * Initial release (Closes: #977846).

Regards,
-- 
  Emmanuel Arias

Bug#977846: ITP: pylev -- pure Python Levenshtein implementation

[Emmanuel Arias]

Package: wnpp
Severity: wishlist
Owner: Emmanuel Arias 
X-Debbugs-Cc: debian-python@lists.debian.org

* Package name: pylev
  Version : 1.3.0
  Upstream Author : Daniel Lindsley 
* URL : https://github.com/toastdriven/pylev
* License : BSD-3-Clause
  Programming Lang: Python
  Description :  pure Python Levenshtein implementation

A pure Python Levenshtein implementation that's not freaking GPL'd.
Based off the Wikipedia code samples at
http://en.wikipedia.org/wiki/Levenshtein_distance.
.
This is a dependency of clickit.
.
This package is needed for poetry packaging.
.
This package will be maintained as part of the Debian Python modules team.

Cheers,
Emmanuel

Bug#977823: RFS: pastel/0.2.1-1 [ITP] -- bring colors to your terminal

[Emmanuel Arias]

Package: sponsorship-requests
Severity: wishlist
X-Debbugs-Cc: debian-python@lists.debian.org

Dear mentors,

I am looking for a sponsor for my package "pastel":

 * Package name: pastel
   Version : 0.2.1-1
   Upstream Author : Sébastien Eustace 
 * URL : https://github.com/sdispater/pastel
 * License : MIT
 * Vcs : https://salsa.debian.org/python-team/packages/pastel
   Section : python

It builds those binary packages:

  python3-pastel - bring colors to your terminal (Python 3)

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

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

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

  dget -x
https://mentors.debian.net/debian/pool/main/p/pastel/pastel_0.2.1-1.dsc

Changes for the initial release:

 pastel (0.2.1-1) unstable; urgency=medium
 .
   * Initial release (Closes: #977741).

Regards,
-- 
  Emmanuel Arias

Bug#977741: ITP: pastel -- bring colors to your terminal

[Emmanuel Arias]

Package: wnpp
Severity: wishlist
Owner: Emmanuel Arias 
X-Debbugs-Cc: debian-python@lists.debian.org

* Package name: pastel
  Version : 0.2.1
  Upstream Author : Sébastien Eustace 
* URL : https://github.com/sdispater/pastel
* License : MIT
  Programming Lang: Python
  Description :  bring colors to your terminal

Pastel is a simple library to help you colorize strings in your terminal.
.
This is a dependency of clickit.
.
This package is needed for poetry packaging.
.
This package will be maintained as part of the Debian Python modules team.

Cheers,
Emmanuel

Bug#977675: ITP: clikit -- utilities to build command line interfaces

[Emmanuel Arias]

Package: wnpp
Severity: wishlist
Owner: Emmanuel Arias 
X-Debbugs-Cc: debian-python@lists.debian.org

* Package name: clikit
  Version : 0.6.2
  Upstream Author : Sébastien Eustace 
* URL : https://github.com/sdispater/clikit
* License : MIT
  Programming Lang: Python
  Description :  utilities to build command line interfaces

CliKit is a group of utilities to build beautiful and testable command line
interfaces.
.
This is at the core of Cleo.
.
This is a dependency for poetry packaging.
.
This package will be maintained as part of the Debian Python modules team.

Cheers,
Emmanuel

Bug#977524: RFS: poetry-core/1.0.0-1 [ITP] -- Poetry PEP 517 Build Backend

[Emmanuel Arias]

Package: sponsorship-requests
Severity: wishlist
X-Debbugs-Cc: debian-python@lists.debian.org

Dear mentors,

I am looking for a sponsor for my package "poetry-core":

 * Package name: poetry-core
   Version : 1.0.0-1
   Upstream Author : Sébastien Eustace 
 * URL : https://github.com/python-poetry/poetry-core
 * License : BSD-2-Clause, BSD-3-Clause, MIT
 * Vcs :
https://salsa.debian.org/python-team/packages/poetry-core
   Section : python

It builds those binary packages:

  python3-poetry-core - Poetry PEP 517 Build Backend

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

  https://mentors.debian.net/package/poetry-core/

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

  dget -x
https://mentors.debian.net/debian/pool/main/p/poetry-core/poetry-core_1.0.0-1.dsc

Changes for the initial release:

 poetry-core (1.0.0-1) unstable; urgency=low
 .
   * Initial release (Closes: #977483)

Regards,
-- 
  Emmanuel Arias

Bug#977483: ITP: poetry-core -- Poetry PEP 517 Build Backend

[Emmanuel Arias]

Package: wnpp
Severity: wishlist
Owner: Emmanuel Arias 
X-Debbugs-Cc: debian-python@lists.debian.org

* Package name: poetry-core
  Version : 1.0.0
  Upstream Author : Sébastien Eustace 
* URL : https://github.com/python-poetry/poetry-core
* License : MIT
  Programming Lang: Python
  Description :  Poetry PEP 517 Build Backend

A PEP 517 build backend implementation developed for Poetry.
This project is intended to be a light weight, fully compliant,
self-contained package allowing PEP 517 compatible build frontends
to build Poetry managed projects.
.
This is a dependency for poetry packaging.
.
This package will be maintained as part of the Debian Python modules team.

Cheers,
Emmanuel

Re: New Python project

[Emmanuel Arias]

https://www.debian.org/doc/manuals/maint-guide/ is very useful for me.
and these https://www.debian.org/doc/devel-manuals and
https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst

But as mention wRAR, that phrase is important.

cheers!

Re: Asking for help Poetry

[Emmanuel Arias]

Hi everyone,

After read [0] and thinking about it, IMO the best solution is try to
package python-poetry,
and its dependencies. I make a very simple (and probably wrong) script [1]
to verify the
package that will be need package into Debian, before poetry package.

[{'name': 'cleo'}, {'name': 'clikit'}, {'name': 'crashtest'}, {'name':
'shellingham'}, {'name': 'pastel'}, {'name': 'pylev'}]

Please feel free to ITP them :)

[0] https://github.com/python-poetry/poetry/issues/2346
[1] https://github.com/eamanu/pydebdep

On Sun, Nov 22, 2020 at 11:03 AM Emmanuel Arias  wrote:

> Hi everyone,
>
> In the last week I re-take this work.
>
> But, we need to discuss the poetry situation. First of all, poetry
> upstream doesn't consider
> adding vendor libs to the source. They have their reasons about this
> situation. I recommend
> you read this [0] [1].
>
> The problem here, is that poetry need some dependencies that are not in
> Debian yet,
> and that dependencies have more dependencies (not in Debian).
>
> Here there're some possibilities that from my point of view we can follow.
> If you read [0] @abn recommend use `sonnet` script to build poetry
> but is not maintained. In the other hand we can can try to package
> poetry-core
> that is a more pip similar case with the vendor libs.
>
> In this week I want to make some tests using `sonnet` and look poetry-core
> with the aim to  package poetry before freezing Debian.
>
> I can send you (not today) the list of the dependencies that will be need
> package if we want poetry in Debian.
>
> This is my analysis about poetry (from a not so experienced DM) I will
> happy to listen to more experienced people about this, and if you consider
> correct that I mention, please.
>
> Thanks!
>
> [0] https://github.com/python-poetry/poetry/issues/2607
> [1] https://github.com/python-poetry/poetry/issues/2346
>
>
> Cheers,
> Arias Emmanuel
> @eamanu
> yaerobi.com
>
>
> On Thu, Nov 19, 2020 at 12:16 PM Bastian Venthur 
> wrote:
>
>> Hi,
>>
>> I see some updates on the salsa repository, any chance we can get this
>> package ready before the next freeze so we'll have it in the next stable
>> release?
>>
>>
>> Cheers,
>>
>> Bastian
>>
>> On 29.06.20 06:04, Scott Kitterman wrote:
>> >
>> >
>> > On June 29, 2020 3:08:53 AM UTC, Emmanuel Arias 
>> wrote:
>> >> Hi,
>> >>
>> >> I'm working on poetry packaging, I created on salsa de repository [0].
>> >>
>> >> Note that there are many packages that are not in Debian like cachy,
>> >> cleo,
>> >> etc.
>> >>
>> >> I RFS python-cachy [1] and now I'm working on cleo, which depends on
>> >> clikit
>> >> that is not on Debian (if I search correctly).
>> >>
>> >> Bastian Venthur note me that pienv, pip have vendors folder with the
>> >> dependencies
>> >> but looking on poetry that _vendor folder is empty.
>> >>
>> >> So, looking for I more experienced opinion, do you think that we would
>> >> try
>> >> convince
>> >> to upstream to make available vendors on the release (if that is
>> >> necessary)
>> >> or
>> >> we need to package all the missing dependencies?
>> >
>> > Definitely they should be packaged.
>> >
>> > At least for pip none of the vendored libs are used in Debian's
>> package.  Fortunately upstream supports use of system libs with only minor
>> patching.
>> >
>> > Scott K
>> >
>> >
>>
>>
>> --
>> Dr. Bastian Venthur  http://venthur.de
>> Debian Developer venthur at debian org
>>
>>

Re: Asking for help Poetry

[Emmanuel Arias]

Hi everyone,

In the last week I re-take this work.

But, we need to discuss the poetry situation. First of all, poetry upstream
doesn't consider
adding vendor libs to the source. They have their reasons about this
situation. I recommend
you read this [0] [1].

The problem here, is that poetry need some dependencies that are not in
Debian yet,
and that dependencies have more dependencies (not in Debian).

Here there're some possibilities that from my point of view we can follow.
If you read [0] @abn recommend use `sonnet` script to build poetry
but is not maintained. In the other hand we can can try to package
poetry-core
that is a more pip similar case with the vendor libs.

In this week I want to make some tests using `sonnet` and look poetry-core
with the aim to  package poetry before freezing Debian.

I can send you (not today) the list of the dependencies that will be need
package if we want poetry in Debian.

This is my analysis about poetry (from a not so experienced DM) I will
happy to listen to more experienced people about this, and if you consider
correct that I mention, please.

Thanks!

[0] https://github.com/python-poetry/poetry/issues/2607
[1] https://github.com/python-poetry/poetry/issues/2346


Cheers,
Arias Emmanuel
@eamanu
yaerobi.com


On Thu, Nov 19, 2020 at 12:16 PM Bastian Venthur  wrote:

> Hi,
>
> I see some updates on the salsa repository, any chance we can get this
> package ready before the next freeze so we'll have it in the next stable
> release?
>
>
> Cheers,
>
> Bastian
>
> On 29.06.20 06:04, Scott Kitterman wrote:
> >
> >
> > On June 29, 2020 3:08:53 AM UTC, Emmanuel Arias 
> wrote:
> >> Hi,
> >>
> >> I'm working on poetry packaging, I created on salsa de repository [0].
> >>
> >> Note that there are many packages that are not in Debian like cachy,
> >> cleo,
> >> etc.
> >>
> >> I RFS python-cachy [1] and now I'm working on cleo, which depends on
> >> clikit
> >> that is not on Debian (if I search correctly).
> >>
> >> Bastian Venthur note me that pienv, pip have vendors folder with the
> >> dependencies
> >> but looking on poetry that _vendor folder is empty.
> >>
> >> So, looking for I more experienced opinion, do you think that we would
> >> try
> >> convince
> >> to upstream to make available vendors on the release (if that is
> >> necessary)
> >> or
> >> we need to package all the missing dependencies?
> >
> > Definitely they should be packaged.
> >
> > At least for pip none of the vendored libs are used in Debian's
> package.  Fortunately upstream supports use of system libs with only minor
> patching.
> >
> > Scott K
> >
> >
>
>
> --
> Dr. Bastian Venthur  http://venthur.de
> Debian Developer venthur at debian org
>
>

Bug#975243: ITP: aiodogstatsd -- asyncio-based client for sending metrics to StatsD with support of DogStatsD extension

[Emmanuel Arias]

Package: wnpp
Severity: wishlist
X-Debbugs-Cc: debian-python@lists.debian.org

* Package name: aiodogstatsd
  Version : 0.14.0-1
  Upstream Author : Nikita Grishko 
* URL : https://github.com/Gr1N/aiodogstatsd
* License : MIT
  Programming Lang: Python3
  Description : asyncio-based client for sending metrics to StatsD with
support of DogStatsD extension
.
Library fully tested with statsd_exporter and supports gauge, counter,
histogram,
distribution and timing types.
.
aiodogstatsd client by default uses 9125 port. It's a default port for
statsd_exporter
and it's different from 8125 which is used by default in StatsD and DataDog.
Initialize the client with the proper port you need if it's different from
9125.

Re: Policy proposal: Consistent use of UNRELEASED in debian/changelog

[Emmanuel Arias]

On Tue, Oct 6, 2020 at 1:03 PM Jonathan Carter  wrote:

> On 2020/10/06 17:53, Louis-Philippe Véronneau wrote:
> > Thanks for all the comments and improvements people proposed.
> >
> > Ondřej merged my MR last night, so it's now part of policy.
>
Great!

>
> Yay! Thanks!
>
> -Jonathan
>
> --
>   ⢀⣴⠾⠻⢶⣦⠀  Jonathan Carter (highvoltage) 
>   ⣾⠁⢠⠒⠀⣿⡁  https://wiki.debian.org/highvoltage
>   ⢿⡄⠘⠷⠚⠋   https://debian.org | https://jonathancarter.org
>   ⠈⠳⣄  Debian, the universal operating system.
>
>

Re: Newcomers project: DPMT/PAPT pristine-tar verification

[Emmanuel Arias]

Hi,

IMO this is a good job for Janitor. I don't know if I would like to add the
possibility to make the
merge without human approval, but for me a MR from Janitor could be enough.



On Tue, Oct 6, 2020 at 1:14 PM Louis-Philippe Véronneau 
wrote:

> On 2020-10-06 12 h 07, Louis-Philippe Véronneau wrote:
> > On 2020-10-03 15 h 35, Sandro Tosi wrote:
> >> attached the dd-list of the packages missing the pristine-tar branch
> (some
> >> may have been moved/removed, but these are actual repos in DPT)
> >>
> >> On Fri, Jul 10, 2020 at 12:38 AM Sandro Tosi  wrote:
> >>
> >>> Hello,
> >>> i would like to propose a project to make sure our teams (DPMT/PAPT)
> >>> repos are using pristine-tar properly.
> >>>
> >>> The checks i have in mind for now, are:
> >>>
> >>> * pristine-tar branch must exist, if not -> it's a bug
> >>> * pristine-tar + upstream branch must produce the same tarball as
> >>> downloaded from the archive, if not -> it's a bug
> >>> * bonus point: fix the repo if it doesn't generate the right tarball
> >>> and or the branch is missing.
> >>> * bonus point: make this into a service that runs regularly (not
> >>> strictly necessary to be limited to us)
> >>>
> >>> i guess we should have a brief discussion about additional checks
> >>> and/or procedures before "assigning" it to a volunteer. let's say up
> >>> to 2 weeks of discussion, and during the same period volunteers can
> >>> nominate themselves.
> >>>
> >>> I marked this project as newcomers as it doesn't require to be a DD/DM
> >>> to work on it, you just need a salsa account and access to our teams.
> >>> a handy tool to retrieve all our repos is at
> >>>
> >>> https://salsa.debian.org/python-team/tools/python-modules
> >>> https://salsa.debian.org/python-team/tools/python-apps
> >>>
> >>> that contains a config file for `mr` and a `checkout` script to fetch
> >>> the repos registered in that config file.
> >>>
> >>> Please feel free to discuss this project now :)
> >
> > I had a chat with folks in #debian-qa last night, as I agree such checks
> > would be nice to have.
> >
> > 1. Lintian is not suited for that kind of checks, as it does not have
> > network access. Frankensteining lintian to do that kind of stuff would
> > surely be met with fierce opposition.
> >
> > 2. The vcswatch script [1] from the QA team already does something akin
> > to what we would want. It's written in Perl [2], but doesn't look
> > terribly complicated. When a check doesn't pass, it issues an
> > action-item like this one [3].
> >
> > I think the first step would be modifying vcswatcher to issue warnings
> for:
> >
> > * the absence of pristine-tar branches
> > * missing git tags
> > * repositories using 'master' instead of 'debian/master' as the main
> branch
> >
> > Once these are flagged, we can easily script a way to fix them, maybe
> > even using lintian-brush?
>
> I meant Debian Janitor here.
>
> I don't know the codebase enough, but in my mind, having the thing that
> fixes problems and the thing that flags them be separate is valuable. I
> don't know if Janitor follows that philosophy though.
>
> --
>   ⢀⣴⠾⠻⢶⣦⠀
>   ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
>   ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
>   ⠈⠳⣄
>
>
>
>

Re: Policy proposal: Consistent use of UNRELEASED in debian/changelog

[Emmanuel Arias]

Hi,



El dom., 27 de sep. de 2020 a la(s) 21:08, Louis-Philippe Véronneau (
po...@debian.org) escribió:

> Hi!
>
> I am proposing a minor addition to the DPT policy to try to make the use
> of UNRELEASED in debian/changelog more consistent. The full diff can be
> found here [1].
>
> The problem this tries to solves is inconsistent use of UNRELEASED in
> debian/changelog. Some people do not use it at all, and it can make
> working on team packages harder.
>
> Indeed, if you try to modify a package, if people don't use UNRELEASED,
> you first need to check if the current VCS version has been uploaded to
> the archive or not. This complicates the life of people doing mass
> updates, as they can't rely on packages with `unstable` having been
> uploaded.
>
> This be can seen for example in the latest batch of updates by onovy,
> where new versions of a package were made instead of marking changes as
> addition to a yet to be released version, because some packages were
> marked `unstable` but hadn't been uploaded.
>
> I don't think it's a lot to ask and will surely make team contributions
> more pleasant :)
>
>
Yes, +1 for this please.

Cheers,
eamanu

Cheers,
>
> [1]:
>
> https://salsa.debian.org/python-team/tools/python-modules/-/merge_requests/15
>
> --
>   ⢀⣴⠾⠻⢶⣦⠀
>   ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
>   ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
>   ⠈⠳⣄
>
>

Re: Merging the PAPT and the DMPT

[Emmanuel Arias]

Hi,
On Mon, Sep 14, 2020 at 5:15 AM Ondrej Novy  wrote:

> Hi,
>
> I prepared scripts for:
>
>- cloning ACLs from modules+applications subgroups to newly created
>packages subgroup
>- transferring all project from modules+applications to packages
>subgroup
>- tested on one project:
>https://salsa.debian.org/python-team/packages/alembic
>
> It looks like old web URLs works just fine:
> https://salsa.debian.org/python-team/modules/alembic
>

So, we shouldn't be worried about changing the VCS-*  path during the
migration process, isn't it?

>
>
> and cloning too:
> $ git clone ssh://g...@salsa.debian.org/python-team/modules/alembic.git
> Cloning into 'alembic'...
> remote: Enumerating objects: 1141, done.
> remote: Counting objects: 100% (1141/1141), done.
> remote: Compressing objects: 100% (558/558), done.
> remote: Total 1141 (delta 720), reused 932 (delta 543), pack-reused 0
> Receiving objects: 100% (1141/1141), 882.54 KiB | 989.00 KiB/s, done.
> Resolving deltas: 100% (720/720), done.
> $
>
> $ git clone https://salsa.debian.org/python-team/modules/alembic.git
> Cloning into 'alembic'...
> remote: Enumerating objects: 1141, done.
> remote: Counting objects: 100% (1141/1141), done.
> remote: Compressing objects: 100% (558/558), done.
> remote: Total 1141 (delta 720), reused 932 (delta 543), pack-reused 0
> Receiving objects: 100% (1141/1141), 882.54 KiB | 3.33 MiB/s, done.
> Resolving deltas: 100% (720/720), done.
> $
>
> Any thoughts?
>
> pá 28. 8. 2020 v 15:36 odesílatel Ondrej Novy  napsal:
>
>> Hi,
>>
>> pá 28. 8. 2020 v 15:27 odesílatel Louis-Philippe Véronneau <
>> po...@debian.org> napsal:
>>
>>> I think changing the path would be a good idea, as I don't see the point
>>> between the libraries and applications divide.
>>
>>
>> +1. GitLab will take care with redirects. It's a mess now :)
>>
>> --
>> Best regards
>>  Ondřej Nový
>>
>>
>
> --
> S pozdravem/Best regards
>  Ondřej Nový
>
>

Re: Bug#969081: gyp should not stay under pkg-js umbrella

[Emmanuel Arias]

Hi,

IMO seems to be a package that could be perfectly into python-team

But would be nice listen to a more experienced team member.

Cheers,
Emmanuel

On 8/30/20 8:45 AM, Jérémy Lal wrote:
> 
> 
> Le jeu. 27 août 2020 à 11:48, Xavier Guimard  > a écrit :
> 
> Package: gyp
> Version: 0.1+20200513gitcaa6002-1
> Severity: normal
> 
> Hi,
> 
> gyp is currently maintain under pkg-js umbrella. This package is a cross
> platform tool written in Python and stored in salsa.d.o/debian/ area.
> Then I don't understand the link with pkg-js team.
> 
> 
> Good point !
> 
> Let's ask debian-python if gyp could be team-maintained there.
> 
> Jérémy
> 


0xFA9DEC5DE11C63F1.asc
Description: application/pgp-keys


signature.asc
Description: OpenPGP digital signature

Re: I'll be offline for an indefinite period

[Emmanuel Arias]

Hi,

Thanks for warn about this.

If there aren't any objections I can add me as uploader and taking care
the package.

However,  the packages are into the team so any team member can
take care it.


Cheers,
Arias Emmanuel
@eamanu
yaerobi.com


‪On Thu, Aug 27, 2020 at 2:20 AM ‫أحمد المحمودي‬‎ <
aelmahmo...@users.sourceforge.net> wrote:‬

> Hello,
>
>  Unfortunately, I will be offline for an indefinite period.
> I maintain those packages in python team: wikitrans, pyfribidi, okasha,
> and python-uinput.
>
> --
> ‎أحمد المحمودي (Ahmed El-Mahmoudy)
>  Digital design engineer
> GPG KeyIDs: 4096R/A7EF5671 2048R/EDDDA1B7
> GPG Fingerprints:
>  6E2E E4BB 72E2 F417 D066  6ABF 7B30 B496 A7EF 5761
>  8206 A196 2084 7E6D 0DF8  B176 BC19 6A94 EDDD A1B7
>

Re: Merging the PAPT and the DMPT

[Emmanuel Arias]

oops, I forgot, I think we must update the line

```
Copyright (c) 2005-2019 Debian Python Team. All rights reserved.
```

to 2020, isn't?

On Fri, Aug 28, 2020 at 11:52 AM Emmanuel Arias  wrote:

> Hi everybody!
>
> +1 for the merge.
>
> I think it's easy to change the link to vcs-* in bulk? (Talking from my
> ignorance)
>
> Cheers!
> Emmanuel
>
>
> On Fri, Aug 28, 2020 at 10:54 AM Ondrej Novy  wrote:
>
>> Hi,
>>
>> pá 28. 8. 2020 v 15:27 odesílatel Louis-Philippe Véronneau <
>> po...@debian.org> napsal:
>>
>>> I think changing the path would be a good idea, as I don't see the point
>>> between the libraries and applications divide.
>>
>>
>> +1. GitLab will take care with redirects. It's a mess now :)
>>
>> --
>> Best regards
>>  Ondřej Nový
>>
>>

Re: Merging the PAPT and the DMPT

[Emmanuel Arias]

Hi everybody!

+1 for the merge.

I think it's easy to change the link to vcs-* in bulk? (Talking from my
ignorance)

Cheers!
Emmanuel


On Fri, Aug 28, 2020 at 10:54 AM Ondrej Novy  wrote:

> Hi,
>
> pá 28. 8. 2020 v 15:27 odesílatel Louis-Philippe Véronneau <
> po...@debian.org> napsal:
>
>> I think changing the path would be a good idea, as I don't see the point
>> between the libraries and applications divide.
>
>
> +1. GitLab will take care with redirects. It's a mess now :)
>
> --
> Best regards
>  Ondřej Nový
>
>

Re: [PATCH] Tell source location of policy.

[Emmanuel Arias]

Hi,

+1  for this patch. I dared to make a MR [0]. Please, consider
review it.

[0] https://salsa.debian.org/cpython-team/python3-defaults/-/merge_requests/5

Cheers,
Arias Emmanuel
@eamanu
http://eamanu.com

Re: Request to join Python Modules Team

[Emmanuel Arias]

Geert,

it's more easy and polite ping to admins and ask for the status of
the request.

IMHO it's not so funny to ask "Who is waiting on who?"

Why do we have to wait 75 hours?

Re: DebConf20 @ Home -- Python Team Bof & Sprint ?

[Emmanuel Arias]

On Mon, Jul 6, 2020 at 4:23 PM Louis-Philippe Véronneau 
wrote:

> On 2020-07-01 09 h 59, Louis-Philippe Véronneau wrote:
> > On 2020-06-24 21 h 13, Louis-Philippe Véronneau wrote:
> >> Hello folks!
> >>
> >> As some of you might have seen, DebConf20 @ Home will be happening end
> >> of August.
> >>
> >> I was wondering if others would be interested in having a Python Team
> >> BoF to talk about ongoing work/issues (the Python 2 removals comes to my
> >> mind but I'm sure there are other discussion-worthy topics).
> >>
> >> If there is interest, I'd be happy to submit something to the DebConf
> >> Content team.
> >>
> >> Maybe it would also be good to set aside half a day during the conf
> >> (preferably after the BoF) for a sprint to try and fix things?
> >>
> >> Cheers,
> >>
> >
> > FWIW, I haven't sent a BoF proposal to the DebConf Content team yet, as
> > I don't feel 3 people (including me) is enough to interest.
> >
> > If you'd like to see a Python BoF + Sprint happen during DebConf20@Home,
> > please show your support.
> >
>
>
> Thanks for all of those who showed interest, and to Stefano for the
> extra poke.
>
> I submitted a BoF + Sprint proposal to the DebConf20 Content Team.
>

\O/

>
>
>
> --
>   ⢀⣴⠾⠻⢶⣦⠀
>   ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
>   ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
>   ⠈⠳⣄
>
>

Re: py2removal - make all leaf applications RC

[Emmanuel Arias]

On Sun, Jul 5, 2020 at 9:09 AM Ondrej Novy  wrote:

> Hi,
>
> ne 5. 7. 2020 v 7:38 odesílatel Sandro Tosi  napsal:
>
>> I propose to raise the severity of all leaf applications in 3 days
>>
>
> +1
>

Also +1 :)

Cheers,
Emmanuel

>
> Thanks!
>
> --
> S pozdravem/Best regards
>  Ondřej Nový
>
>

Re: Offer to help with packaging

[Emmanuel Arias]

Hi,


On Thu, Jul 2, 2020 at 12:48 AM Pablo Mestre  wrote:

> Hi
>
> El 7/1/20 a las 10:58 PM, Nicholas D Steeves escribió:
> > Awesome, thank you :-) I expect it will be a popular package too!
> [.]
> > If you're committed to packaging python lsp, then set yourself as the
> > owner of #96360, and retitle it, replacing "RFP" with "ITP".
> Yes, I committed to packaging
> > If the absence of a python-jsonrpc-server package is a blocker for
> > #963605, and you want to work on it, then file an ITP for
> > python-jsonrpc-server, set yourself as owner, and also set up a blocks
> > relationship between the two bugs.
>
> You mean
>
> Control: block 946035 by -1
> Control: block #[newcode] by -1
>
> Something like this?
>

yes go ahead.

I don't see the ITP for python-jsonrpc-server. Do you need some help?

Cheers,
Emmanuel

>
> >
> > Tools for doing this more conveniently are "bts" from devscripts, and
> > "reportbug" for filing the ITP.  IIRC bts requires an MTA (mail
> > transport agent) and for this I'd recommend msmtp-mta, because most
> > people find it easier to configure authentication with it than with
> > Postfix, Exim, etc.
> >
> > If you'd like to do it manually for now, see:
> >   https://www.debian.org/Bugs/server-control
>
> Ok
>
> Thanks for all
>
> P.
>
>
>

Re: Request to join Python Modules Team

[Emmanuel Arias]

Hi,

You just need to be patient. Some administrator from the team will join you.

Cheers,
Arias Emmanuel
@eamanu
http://eamanu.com

El sáb., 4 de jul. de 2020 a la(s) 04:17, Sao I Kuan
(saoik...@gmail.com) escribió:
>
> On Fri, Apr 10, 2020 at 6:22 PM Sao I Kuan  wrote:
> >
> > On Fri, Apr 10, 2020 at 6:16 PM Sao I Kuan  wrote:
> > >
> > > Hiya o/,
> > >
> > > I would like to join the Python Modules Team.
> > >
> > > I'm a newcomer into Debian from this March, and doing the packaging
> > > which is COVID-19 related, with COVID-19 Biohackathon[0].
> > >
> > > [0] https://lists.debian.org/debian-devel-announce/2020/03/msg00010.html
> > >
> > > Now I'm trying to packaging the new python application idseq-bench[1]
> > > (which will be team-maintained inside debian-med), which needs a
> > > module smart_open[2]. I think [2] could be team maintained inside
> > > DPMT.
> > >
> > > [1] https://github.com/chanzuckerberg/idseq-bench
> > > [2] https://github.com/RaRe-Technologies/smart_open
> > >
> > > I read the Debian Python Policy[3].
> > >
> > > [3] https://www.debian.org/doc/packaging-manuals/python-policy/
> >
> > I now found and accept the DPMT Policy[4]. My Salsa handle is @sikuan-guest.
> >
> > [4] 
> > https://salsa.debian.org/python-team/tools/python-modules/-/blob/master/policy.rst
>
> Ping o/ Or am I missing any necessary information?
>
> My Salsa handle was changed to @sikuan.
> Thank you!
>
> Sincerely,
>
> Sao I Kuan
> saoik...@gmail.com
>

Re: Request to join DPMT

[Emmanuel Arias]

Hi


On Mon, Jun 29, 2020 at 8:41 AM Michael Hanke  wrote:

> Hi again,
>
> On Wed, Jun 24, 2020 at 11:27 AM Michael Hanke  wrote:
> > I would like to join DPMT, specifically to provide a Debian package for
> > annexremote (https://bugs.debian.org/963593).
>
> The package is ready. Would it be acceptable, if I upload it to NEW with
>
> ```
> Maintainer: Debian Python Modules Team
> 
> Uploaders: Michael Hanke 
> ```
>
> even though my request to join the team has not been approved yet?
>

You must wait until an administrator on the DPMT could read your request

Be patient :)


>
> For interested parties: the package is hosted on Github for the
> moment: https://github.com/mih/debian-annexremote
>
> Cheers,
>
> Michael
>
>

Asking for help Poetry

[Emmanuel Arias]

Hi,

I'm working on poetry packaging, I created on salsa de repository [0].

Note that there are many packages that are not in Debian like cachy, cleo,
etc.

I RFS python-cachy [1] and now I'm working on cleo, which depends on clikit
that is not on Debian (if I search correctly).

Bastian Venthur note me that pienv, pip have vendors folder with the
dependencies
but looking on poetry that _vendor folder is empty.

So, looking for I more experienced opinion, do you think that we would try
convince
to upstream to make available vendors on the release (if that is necessary)
or
we need to package all the missing dependencies?


[0] https://salsa.debian.org/python-team/applications/poetry
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956819

Many thanks for your help

Cheers,
Arias Emmanuel
@eamanu
yaerobi.com

Re: Python-trezor

[Emmanuel Arias]

Hi Michael,

I contacted Tristan and Richard some months ago. Tristan said to me he
was going to change
the maintainer field on d/control. But lookin on the salsa repository,
that was not updated.
I've  already contacted them again.

I'll be very happy to update python-trezor, but IMO the maintainer (or
uploader) must change the d/control
files. At least one other DD DPMT team member give me the ok to go ahead.


Cheers,
Arias Emmanuel
@eamanu
http://eamanu.com


El dom., 21 de jun. de 2020 a la(s) 14:21, Michael Robinson
(mich...@felinefamily.org) escribió:
>
> Hello again,
>
> The forthcoming upgrade of Electrum to 4.x will require python-trezor0.12 to 
> maintain trezor compatibility. Is there someone that can upload that update? 
> I tried contacting Richard Ulrich and Tristan Seligmann but haven’t been able 
> to make contact.
>
> The primary roadblock to 0.12 was python-libusb1, which is now upgraded to 
> 1.8 and should be compatible.
>
> Any help you can provide would be greatly appreciated
>
> Mike

Re: Re: Sponsorship backlog

[Emmanuel Arias]

Hi everybody!

Forgive my daring but I think the backlog
in irc topic is growthing again :)

If anyone need some help, always, I am to
help.

Cheers!
Emmanuel

Re: Fwd: [covid] New Contributor for biohackathon

[Emmanuel Arias]

Hello everybody,

I am available to help. I will be working on the TODO list [0].

[0]
https://salsa.debian.org/med-team/community/2020-covid19-hackathon/-/wikis/COVID-19-Hackathon-packages-needing-work

Cheers,
Arias Emmanuel
@eamanu
yaerobi.com


On Fri, Apr 10, 2020 at 3:10 AM Olek Wojnar  wrote:

> On 4/9/20 7:37 PM, fancycade wrote:
> > Thank you for the assistance with this!
> >
> > I have uploaded my package to the appropriate repository under the
> > Python Modules team and will reach out for a RFS.
>
> Great, thanks for your contribution!
>
> -Olek
>
>
>
>

Re: Taking over DPMT (Was: python-boto: autopkgtest failure with Python 3.8 as default)

[Emmanuel Arias]

Hi,

Thanks for let me know my error.

I will contact to maintainer to try to move python-boto into DPMT umbrella

Cheers,
Arias Emmanuel
@eamanu
http://eamanu.com

El sáb., 4 de abr. de 2020 a la(s) 06:28, Thomas Goirand
(z...@debian.org) escribió:
>
> On 3/30/20 11:44 AM, Andreas Tille wrote:
> > I wonder whether we should take over python-boto into DPMT maintenance
> > which would enable commits to Git way more easily.
>
> I'd very much be in the favor of this, especially considering the
> package history.
>
> Cheers,
>
> Thomas Goirand (zigo)
>

Re: sshuttle / python3.8

[Emmanuel Arias]

Hello I am available to help.

Let me take a look.

Cheers,
Emmanuel

El mié., 11 de dic. de 2019 18:02, Brian May  escribió:

> Hello,
>
> I have been informed that the sshuttle package, in Debian is most likely
> completely broken under Python 3.8
>
> https://github.com/sshuttle/sshuttle/issues/381
>
> To me this looks like a regression in Python 3.8. but at the same time
> sshuttle is possibly misusing(?) sockets in ways that were never
> intended(?).
>
> Unfortunately, even though I am upstream and Debian maintainer, I don't
> have any time to look at this.
>
> Help appreciated.
>
> Thanks
> --
> Brian May 
>
>

Re: RFS: python-pyjsparser (ITP bug #943785)

[Emmanuel Arias]

Hi Peter,

You can ask via IRC #debian-python

On 11/1/19 6:50 AM, Peter Wienemann wrote:
> Dear Python team,
>
> I prepared packaging for python-pyjsparser (ITP bug #943785) on
>
> https://salsa.debian.org/python-team/modules/python-pyjsparser
>
> It provides a fast JavaScript parser written in Python.
>
> It would be great if a DD could review the code, provide feedback and
> (if everything looks OK) upload it.
>
> Thanks, Peter
>

-- 
Cheers,
Emmanuel Arias
@eamanu
https://eamanu.com




signature.asc
Description: OpenPGP digital signature

Re: [Python-apps-team] pylint3 reverse dependencies.

[Emmanuel Arias]

oh, I understand



signature.asc
Description: OpenPGP digital signature