Request to join Python Modules Team

2020-04-04 Thread fancycade
Hi there!

I would like to join the Python Modules Team. For the time being I am 
interested in maintaining packages related to the upcoming covid biohackathon. 
Specifically I am trying to get my feet wet by packaging this module 
https://github.com/kvesteri/validators which is needed by the streamlit package.

I am familiar with Debian packaging, and already have a package that builds.

My salsa login is: @fancycade-guest

I have read the Python Modules policy.

Thanks!

Re: [RFC] python-cobra, python3-sbml5

2020-04-04 Thread Andrey Rahmatullin
On Sat, Apr 04, 2020 at 06:53:55PM +0530, Nilesh Patra wrote:
> >From the logs, in the last message[2] it looks like an import-error for
> '_libsbml' file which corresponds to libsbml (with python3-sbml5 as a
> provide) package. When I dug into looking at libsbml, I noticed that the
> relevant file (libsbml.py) which throws error
> is generated with swig-3.0 by the upstream [3]
> 
> While the same file in the apt archive (observed after $apt source
> python3-sbml5) seems to be generated with swig-4.0, and that's the current
> swig version in Debian now.
Sorry, I couldn't understand which two files are you comparing. One is
from the python3-sbml5 binary package and is generated with swig 4, where
is the second one, generated by swig 3?

-- 
WBR, wRAR


signature.asc
Description: PGP signature


[RFC] python-cobra, python3-sbml5

2020-04-04 Thread Nilesh Patra
Hi,
Currently python-cobra FTBFS reported here [1].

>From the logs, in the last message[2] it looks like an import-error for
'_libsbml' file which corresponds to libsbml (with python3-sbml5 as a
provide) package. When I dug into looking at libsbml, I noticed that the
relevant file (libsbml.py) which throws error
is generated with swig-3.0 by the upstream [3]

While the same file in the apt archive (observed after $apt source
python3-sbml5) seems to be generated with swig-4.0, and that's the current
swig version in Debian now.

When I compared, the one generated with swig 4.0 looks pretty different
from the one generated by swig 3.0.
I "suspect" that the error is due to the swig version change to 4.0, and
corresponding API changes.

I would really appreciate if I could have more folks "confirm" that this is
the case, and I'm not missing out on anything else.
I'll then file a report upstream then, asking for corresponding code
changes needed for swig 4.0.

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

[2]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955656#10

[3]:
https://salsa.debian.org/med-team/libsbml/-/blob/master/src/bindings/python/libsbml.py?expanded=true=simple

Thanks and regards
Nilesh


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

2020-04-04 Thread Thomas Goirand
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: ITS: pssh

2020-04-04 Thread Jochen Sprickerhof

Hi Hilmar,

* Hilmar Preuße  [2020-03-14 08:26]:

Am 14.03.2020 um 01:29 teilte Sandro Tosi mit:

On Thu, 20 Jun 2019 06:24:13 -0700 Mo Zhou  wrote:
* bring it under PAPT maintenance


Is there more to do than creating a source package, adding a new package
below the PAPT group and import the source package into it?


I did a:

$ gbp import-dscs --pristine-tar --debsnap pssh

and pushed it here:

https://salsa.debian.org/python-team/applications/pssh


* update to the latest upstream release (check #891340 or even
https://github.com/ParallelSSH/parallel-ssh ?)


Yes one has to do that.


parallel-ssh seems to be a Python library and different code base, so I 
would rather go with the Github fork mentioned in #891340. But there are 
no new releases, so it's probably easiest to pull in the patches via 
debian/patches. There is a discussion to make it upstream, so I would 
propose to ask for a release after that is cleared:


https://github.com/lilydjwg/pssh/issues/110#issuecomment-580609871


* upload to debian.


Well, probably. I'd need a sponsor for initial upload as I'm just a DM.


I'm happy to sponsor and help maintain as well.

Do you have time later today or tomorrow to work on it together? 
Otherwise I will go ahead and do some cleanup. My hope would be to get a 
fixed version into unstable by the end of the weekend.


Cheers Jochen


signature.asc
Description: PGP signature