Request to join DPMT and PAPT to package devpi
Hi Python Team Can I join both the DPMT and PAPT to help maintain devpi (and its associated subprojects)? I've read both the DPMT and PAPT policies and accept them. My salsa login is aragilar-guest. My plan for devpi is to update devpi-common to the latest release, then work down the list of devpi projects. I plan on putting the projects under PAPT (apart from devpi-common), unless there are other suggestions? James P.S. I've CC'd in the current ITP bugs for devpi, there will probably be more as I package further projects.
Re: cannot allocate memory in static TLS block
On Saturday, March 14 2020, Andreas Tille wrote: > On Fri, Mar 13, 2020 at 11:09:31PM +0100, Paul Gevers wrote: >> >> raise RuntimeError(('Could not find drmaa library. Please specify >> its ' + >> RuntimeError: Could not find drmaa library. Please specify its full >> path using the environment variable DRMAA_LIBRARY_PATH > > I've fixed this in Git. Unfortunately I get a new issue when importing > drmaa > > $ python3 > Python 3.7.6 (default, Jan 19 2020, 22:34:52) > [GCC 9.2.1 20200117] on linux > Type "help", "copyright", "credits" or "license" for more information. import drmaa > Traceback (most recent call last): > File "", line 1, in > File > "/home/andreas/debian-maintain/salsa/med-team/python-drmaa/drmaa/__init__.py", > line 65, in > from .session import JobInfo, JobTemplate, Session > File > "/home/andreas/debian-maintain/salsa/med-team/python-drmaa/drmaa/session.py", > line 39, in > from drmaa.helpers import (adapt_rusage, Attribute, > attribute_names_iterator, > File > "/home/andreas/debian-maintain/salsa/med-team/python-drmaa/drmaa/helpers.py", > line 36, in > from drmaa.wrappers import (drmaa_attr_names_t, drmaa_attr_values_t, > File > "/home/andreas/debian-maintain/salsa/med-team/python-drmaa/drmaa/wrappers.py", > line 58, in > _lib = CDLL(libpath, mode=RTLD_GLOBAL) > File "/usr/lib/python3.7/ctypes/__init__.py", line 364, in __init__ > self._handle = _dlopen(self._name, mode) > OSError: /usr/lib/x86_64-linux-gnu/libjemalloc.so.2: cannot allocate memory > in static TLS block > > > Any help would be welcome This is an issue with jemalloc's handling of the TLS model when being dlopened.. See: https://github.com/jemalloc/jemalloc/issues/1237 The recommended way to build a libjemalloc that is suitable for being dlopened is to use '--disable-initial-exec-tls' when building it. Take a look at the INSTALL.md file, and look for this option: https://github.com/jemalloc/jemalloc/blob/dev/INSTALL.md There is a way to workaround this bug by doing an LD_PRELOAD of libjemalloc when invoking python, but this will only mask the problem and we can't expect users to do/know this. The way I see it, you can try to convince jemalloc's maintainer to enable that flag. BTW, the reason 'find_library' can't find drmaa's library is because the .so is being installed in a non-standard directory. I don't know why the package was made like this, though. Thanks, -- Sergio GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36 Please send encrypted e-mail if possible http://sergiodj.net/ signature.asc Description: PGP signature
[RFS] pytds
Hi, Currently pytds FTBFS with python3.8. I have fixed it, and build + autopkgtests pass. It is also lintian-clean. There are however, a few build warnings which I am not sure how to fix: I see a lot of: Setting up python3-roman (2.0.0-3) ... /usr/lib/python3.8/subprocess.py:838: RuntimeWarning: line buffering (buffering=1) isn't supported in binary mode, the default buffer size will be used self.stdin = io.open(p2cwrite, 'wb', bufsize) similar warnings; I didn't find buffer=1 in any of the subprocess/file descriptor based functions, not really sure what is causing this. I also see dh_python related warnings as: W: dh_python3 fs:112: Paths differ: debian/python3-tds/usr/lib/python3.8/dist-packages/.test-cache/rootcert.pem and debian/python3-tds/usr/lib/python3/dist-packages/.test-cache/rootcert.pem ... similar warnings; not sure what is wrong here either. I have fixed rest of the warnings, that pytest reported. My changes have been pushed here[1]. Needs review and sponsorship. [1]: https://salsa.debian.org/gi-boi-guest/pytds Thanks and regards, Nilesh
Re: cannot allocate memory in static TLS block (Was: Bug#953832: drmaa: autopkgtest failure: RuntimeError: Could not find drmaa library)
Hi Andreas, On 14-03-2020 14:30, Andreas Tille wrote: > Hi Paul, [...] > Any help would be welcome I can't help you with this. Paul signature.asc Description: OpenPGP digital signature
cannot allocate memory in static TLS block (Was: Bug#953832: drmaa: autopkgtest failure: RuntimeError: Could not find drmaa library)
Control: tags -1 help Control: retitle -1 cannot allocate memory in static TLS block Hi Paul, On Fri, Mar 13, 2020 at 11:09:31PM +0100, Paul Gevers wrote: > > raise RuntimeError(('Could not find drmaa library. Please specify > its ' + > RuntimeError: Could not find drmaa library. Please specify its full > path using the environment variable DRMAA_LIBRARY_PATH I've fixed this in Git. Unfortunately I get a new issue when importing drmaa $ python3 Python 3.7.6 (default, Jan 19 2020, 22:34:52) [GCC 9.2.1 20200117] on linux Type "help", "copyright", "credits" or "license" for more information. >>> import drmaa Traceback (most recent call last): File "", line 1, in File "/home/andreas/debian-maintain/salsa/med-team/python-drmaa/drmaa/__init__.py", line 65, in from .session import JobInfo, JobTemplate, Session File "/home/andreas/debian-maintain/salsa/med-team/python-drmaa/drmaa/session.py", line 39, in from drmaa.helpers import (adapt_rusage, Attribute, attribute_names_iterator, File "/home/andreas/debian-maintain/salsa/med-team/python-drmaa/drmaa/helpers.py", line 36, in from drmaa.wrappers import (drmaa_attr_names_t, drmaa_attr_values_t, File "/home/andreas/debian-maintain/salsa/med-team/python-drmaa/drmaa/wrappers.py", line 58, in _lib = CDLL(libpath, mode=RTLD_GLOBAL) File "/usr/lib/python3.7/ctypes/__init__.py", line 364, in __init__ self._handle = _dlopen(self._name, mode) OSError: /usr/lib/x86_64-linux-gnu/libjemalloc.so.2: cannot allocate memory in static TLS block Any help would be welcome Andreas. -- http://fam-tille.de
Re: ITS: pssh
Hi Sandro, I've lost interest in pssh. At that time I was investigating a couple of parallel SSH solutions, and I eventually chose ansible. On Fri, Mar 13, 2020 at 08:29:04PM -0400, Sandro Tosi wrote: > On Thu, 20 Jun 2019 06:24:13 -0700 Mo Zhou wrote: > > Source: pssh > > Version: 2.3.1-1 > > > > I plan to salvage pssh and fix at least the following bug: > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891340 > > Not sure if Mo is still interested in salvaging this package, other > wise this could be a nice project for someone willing to improve their > packaging skills. this would translate to: > > * bring it under PAPT maintenance > * update to the latest upstream release (check #891340 or even > https://github.com/ParallelSSH/parallel-ssh ?) > * drop python2 support, add python3 support > * upload to debian. > > Regards, > Sandro
Re: ITS: pssh
Am 14.03.2020 um 01:29 teilte Sandro Tosi mit: > On Thu, 20 Jun 2019 06:24:13 -0700 Mo Zhou wrote: >> I plan to salvage pssh and fix at least the following bug: >> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891340 > > Not sure if Mo is still interested in salvaging this package, other > wise this could be a nice project for someone willing to improve their > packaging skills. this would translate to: > > * 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? > * update to the latest upstream release (check #891340 or even > https://github.com/ParallelSSH/parallel-ssh ?) > Yes one has to do that. > * drop python2 support, add python3 support > Has been done in upstream in one of the later commits. > * upload to debian. > Well, probably. I'd need a sponsor for initial upload as I'm just a DM. H. -- sigfault #206401 http://counter.li.org signature.asc Description: OpenPGP digital signature