Re: Please enable me transfering python-bioblend to Debian Med team
Am Sat, Jan 15, 2022 at 07:23:14PM + schrieb Stefano Rivera: > > Could you process this transfer please? Moving python-bioblend from > > python->med team. > > You have maintainer access in -med and owner in -python, hence please > > consider transferring this. > > Transferred: https://salsa.debian.org/med-team/python-bioblend Thanks a lot for moving - package is uploaded on behalf of the Debian Med team now. Kind regards Andreas. -- http://fam-tille.de
Re: Please enable me transfering python-bioblend to Debian Med team
Hi Nilesh (2022.01.15_14:57:40_+) > > I think we sorted out that the request to move python-bioblend to Debian > > Med is valid. I'm CCing Debian Python team maintainers to get this > > finally done. > Could you process this transfer please? Moving python-bioblend from > python->med team. > You have maintainer access in -med and owner in -python, hence please > consider transferring this. Transferred: https://salsa.debian.org/med-team/python-bioblend SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272
Re: Please enable me transfering python-bioblend to Debian Med team
Hi Stefano/Ondřej, On 1/11/22 8:03 PM, Andreas Tille wrote: Hi, I think we sorted out that the request to move python-bioblend to Debian Med is valid. I'm CCing Debian Python team maintainers to get this finally done. Could you process this transfer please? Moving python-bioblend from python->med team. You have maintainer access in -med and owner in -python, hence please consider transferring this. Regards, Nilesh OpenPGP_signature Description: OpenPGP digital signature
Re: Please enable me transfering python-bioblend to Debian Med team
Hi, I think we sorted out that the request to move python-bioblend to Debian Med is valid. I'm CCing Debian Python team maintainers to get this finally done. I'm not sure whether making me the owner of that actual repository is sufficient to enable me transfering the archive. Alternatively I could make one of the DPT owners maintainer on Debian Med project and let this person do the transfer. If this is all to complicated I'll create a new repository in Debian Med and will ask for removal here once the package was uploaded. Kind regards Andreas. Am Wed, Dec 22, 2021 at 09:33:17PM +0100 schrieb Pierre-Elliott Bécue: > > Nilesh Patra wrote on 22/12/2021 at 20:45:53+0100: > > > [[PGP Signed Part:No public key for 00BAE74B343369F1 created at > > 2021-12-22T20:45:49+0100 using RSA]] > > Hi Pierre-Elliot, > > > > On Wed, Dec 22, 2021 at 08:06:01PM +0100, Pierre-Elliott Bécue wrote: > >> >> I'm sorry but pressuring to take over a package is not really fine. If > >> >> you're not happy with the time it takes for an answer, you can try to > >> >> fill an ITS and if the procedure goes to its end then you may take over. > >> > > >> > Please note: The people involved are the same. We are members of > >> > both teams but consider the Debian Med team more appropriate. We > >> > are simply missing the permissions to do the move properly. > >> > >> I am aware of that. > >> > >> Yet, the fact that you are members of both teams doesn't entitle you to > >> decide such a transfer, even if you had the technical rights to do so. > > > > Hmm, I am not sure what the problem in such a case would be (permission in > > both teams) > > Steffen is the maintainer (uploader if you might prefer it that way) and he > > has > > agreed already[1] -- so what's the problem? > > > > [1]: https://lists.debian.org/debian-med/2021/12/msg00119.html > > I guess the problem is that the python-team doesn't seem to have been > Cc-ed in your exchange, which was not quoted in the initial mail of this > thread. > > As I'm not subscribed to the list, it really looked like you were > intending to take over a package without any maintainer of it having > been asked for it before. > > As it seems not to be the case, it's not the same at all. > > >> I therefore stand my point: the way Debian is made has not changed > >> recently, and taking over still requires a formal approval from the > >> maintainer, which you are not. > >> > >> The only alternatives are either an ITS or MIA team orphaning their > >> packages, but as the maintainer is an active team, the latter will not > >> happen. > > > > I do not think it is sensible to take consensus from an entire team to > > move a single package. > > I did not suggest to wait for a consensus, but rather that an admin asks > if someone is against and waits for a reasonable delay (72 hours?) and > then makes the transfer if they're happy with it. > > > Honestly speaking, we really do not need to make team transfer debian > > processes such a high friction ones -- it just stalls the work for no > > good reason. The package has not seen uploads since more than two > > years, I really doubt anyone in the team feels strong ly about not > > moving it. > > There is no real difference between teams and individual developers on > that part: a take over has to be approved or to follow due procedures, > whether we like it or not. > > Here, as Steffen gave his approval, the topic is a bit moot. > > > If you are talking about Ondřej doing the uploads apart from the > > initial uploads, then you probably are also aware that Ondřej does a > > number of team-maintained package uploads to fix bugs, does updates > > and so on (a lot of us do so, for that matter albeit in other teams) I > > really don't think that he has a personal interest in every single one > > of those packages (including this one) but we should hear from him. > > I was under the (false) impression that Steffen was not currently > available to reply to your query. Ondřej being an admin of the team and > having done all the uploads apart from those done by Steffen, he clearly > seemed the best second contact point to ask this transfer. > > >> >> and they could be willing to check that no one in the team objects. > > > > Sure but how are you making a "check" here? I do have admin access in > > a few teams, and speaking for myself: I would send out an email to the > > list, wait for a time frame (maximum 1 week) and check if someone has > > any comments If not, I would make a move. So we already have a mail > > in the debian-python mailing list, and no objections so far, so > > > > I would have probably done more to ask for consensus better (asking on > > IRC channels etc) but admittedly, we only have 24 hours in the day, > > and several dozens of packages to do. > > Asking globally on the list and waiting a reasonable amount of time for > a potential grunt is fine with me. > > >> I think you missed the second part of my
Re: Transfering packages from Debian Med to DPT (Was: Please enable me transfering python-bioblend to Debian Med team)
Am Sun, Jan 02, 2022 at 09:00:27PM +0100 schrieb Andreas Tille: ... Continuing with moving packages from Debian Med to Debian Python Team > python-sinfo 0.3.1-2 > python3-sinfo : print different version information for loaded modules Moved to Debian Python Team. > python-spectra 0.0.11-3 > python3-spectra : Easy color scales and color conversion for > Python (Python 3 version) Moved to Debian Python Team. > python-stdlib-list 0.8.0-4 > python3-stdlib-list : List of Python Standard Libraries (2.6-7, 3.2-9) Moved to Debian Python Team. > python-streamz 0.6.3-1 > python3-streamz : build pipelines to manage continuous streams of data Moved to Debian Python Team. Unfortunately there is a build time test issue in my local pbuilder environment: ___ test_from_iterable_backpressure def test_from_iterable_backpressure(): it = iter(range(5)) source = Source.from_iterable(it) wait_for(lambda: L == [0], 1, period=0.01) > assert next(it) == 2 # 1 is in blocked _emit E assert 1 == 2 E+ where 1 = next() streamz/tests/test_sources.py:151: AssertionError However, salsa-ci is fine: https://salsa.debian.org/python-team/packages/python-streamz/-/pipelines/333644 (besides i386 build which also failed before) Could somebody please check and upload? > python-stubserver 1.1-2 > python3-stubserver : mock tester of external web dependencies for Python Moved to Debian Python Team. > python-tinyalign 0.2-5 > python3-tinyalign : numerical representation of differences between > strings This is mentioned in med-* tasks and directly used by Biologists. I think we should keep it inside Debian Med team. > python-typechecks 0.1.0+ds-2 > python3-typechecks : express constraints on types Moved to Debian Python Team. > python-upsetplot 0.6.0-2 > python3-upsetplot : Draw Lex et al.'s UpSet plots with Pandas and > Matplotlib Moved to Debian Python Team. > python-wdlparse 0.1.0-2 > python3-wdlparse : Workflow Description Language (WDL) parser for Python This is mentioned in med-* tasks and directly used by Biologists. I think we should keep it inside Debian Med team. > python-wordcloud 1.8.1+dfsg-2 > python3-wordcloud : little word cloud generator in Python Moved to Debian Python Team. > python-xopen 1.2.1-3 > python3-xopen : Python3 module to open compressed files transparently Moved to Debian Python Team. > smart-open 5.2.1-3 > python3-smart-open : utils for streaming large files Moved to Debian Python Team. > sorted-nearest 0.0.31+dfsg-1 > python3-sorted-nearest : Cython helper library for pyranges This is just a helper for pyranges which is clearly a Debian Med package. I see no real value in moving this to Debian Python Team. > sphinxcontrib-autoprogram 0.1.7-1 > python3-sphinxcontrib.autoprogram : automated documentation of CLI > programs for Sphinx (Python 3) Moved to Debian Python Team. > Thanks, You are welcome. I'd love to see an additional Uploader for all these moved packages. Please let me know if you see some additional room for enhancement of the cooperation between Debian Python Team and Debian Med Team. Kind regards Andreas. -- http://fam-tille.de
Re: Transfering packages from Debian Med to DPT (Was: Please enable me transfering python-bioblend to Debian Med team)
Am Sun, Jan 02, 2022 at 11:25:40AM +0100 schrieb Andreas Tille: > Am Sun, Jan 02, 2022 at 10:00:09AM +0100 schrieb Andreas Tille: > > ... > Continuing with moving packages from Debian Med to Debian Python Team > python-duckpy 3.2.0-2 > python3-duckpy : simple Python library for searching on DuckDuckGo Moved to Debian Python Team > python-easydev 0.12.0+dfsg-1 > python3-easydev : common utilities to ease the development of > Python packages (Python 3) Moved to Debian Python Team > python-etelemetry 0.2.0-4 > python3-etelemetry : lightweight Python3 client to communicate > with the etelemetry server That's pretty clearly a Debian Med topic > python-hdmedians 0.14.2-3 > python3-hdmedians : high-dimensional medians in Python3 Moved to Debian Python Team > python-leidenalg 0.8.8-1 > python3-leidenalg : Python3 implementation of the Leiden algorithm in C++ Seems pretty related to Debian Med topic even if not that obvious. > python-lzstring 1.0.4-1.1 > python3-lzstring : LZ-based compression algorithm for Python > (Python 3 version) Moved to Debian Python Team > python-matplotlib-venn 0.11.6-2 > python3-matplotlib-venn : Python 3 plotting area-proportional two- > and three-way Venn diagrams Moved to Debian Python Team > python-multipletau 0.3.3+ds-3 > python-multipletau-doc : documentation for multipletau Python module > python3-multipletau : multiple-tau algorithm for Python3/NumPy Moved to Debian Python Team > python-multisplitby 0.0.1-4 > python3-multisplitby : Python3 module to create iterables split on > arbitrary separators Moved to Debian Python Team > python-ncls 0.0.63+ds-1 > python3-ncls : datastructure for interval overlap queries Moved to Debian Python Team > python-pipdeptree 2.2.0-2 > python3-pipdeptree : display dependency tree of the installed > Python 3 packages Moved to Debian Python Team > python-pyflow 1.1.20-3 > python3-pyflow : lightweight parallel task engine for Python Workflows are a very hot topic in Debian Med team. If there is no strong reason to move this package to Debian Python team I'd prefer to leave it where it is. > python-pynndescent 0.5.2+dfsg-1 > python3-pynndescent : nearest neighbor descent for approximate > nearest neighbors Moved to Debian Python Team Git but source does not build - most possibly due problems with Python3.10 and numba. The latest upstream version fails as well (with even more errors). I'd be happy if someone from Debian Python Team could serve as Uploader and care for this. > python-pypubsub 4.0.3-5 > python3-pubsub : Python 3 publish-subcribe library Moved to Debian Python Team I'll continue with the next batch soon. Kind regards Andreas. > python-sinfo 0.3.1-2 > python3-sinfo : print different version information for loaded modules > python-spectra 0.0.11-3 > python3-spectra : Easy color scales and color conversion for > Python (Python 3 version) > python-stdlib-list 0.8.0-4 > python3-stdlib-list : List of Python Standard Libraries (2.6-7, 3.2-9) > python-streamz 0.6.3-1 > python3-streamz : build pipelines to manage continuous streams of data > python-stubserver 1.1-2 > python3-stubserver : mock tester of external web dependencies for Python > python-tinyalign 0.2-5 > python3-tinyalign : numerical representation of differences between > strings > python-typechecks 0.1.0+ds-2 > python3-typechecks : express constraints on types > python-upsetplot 0.6.0-2 > python3-upsetplot : Draw Lex et al.'s UpSet plots with Pandas and > Matplotlib > python-wdlparse 0.1.0-2 > python3-wdlparse : Workflow Description Language (WDL) parser for Python > python-wordcloud 1.8.1+dfsg-2 > python3-wordcloud : little word cloud generator in Python > python-xopen 1.2.1-3 > python3-xopen : Python3 module to open compressed files transparently > smart-open 5.2.1-3 > python3-smart-open : utils for streaming large files > sorted-nearest 0.0.31+dfsg-1 > python3-sorted-nearest : Cython helper library for pyranges > sphinxcontrib-autoprogram 0.1.7-1 > python3-sphinxcontrib.autoprogram : automated documentation of CLI > programs for Sphinx (Python 3) > > Thanks, > -- > Sandro "morph" Tosi > My website: http://sandrotosi.me/ > Me at Debian: http://wiki.debian.org/SandroTosi > Twitter: https://twitter.com/sandrotosi > -- http://fam-tille.de
Re: Transfering packages from Debian Med to DPT (Was: Please enable me transfering python-bioblend to Debian Med team)
Am Sun, Jan 02, 2022 at 10:00:09AM +0100 schrieb Andreas Tille: > ... Continuing with moving packages from Debian Med to Debian Python Team > > python-ciso8601 2.2.0-1 > > python3-ciso8601 : fast ISO8601 date time parser for Python written in C Moved to Debian Python Team > > python-colormap 1.0.4-2 > > python3-colormap : ease manipulation of matplotlib colormaps and > > color codecs (Python 3) Moved to Debian Python Team > > python-colormath 3.0.0-1.1 > > python3-colormath : Abstracts common color math operations (Python > > 3 version) Moved to Debian Python Team > > python-cooler 0.8.11-1 > > python3-cooler : library for a sparse, compressed, binary persistent > > storage > > python3-cooler-examples : library for a sparse, compressed, binary > > persistent storage (examples) Should remain in Debian Med team (see https://lists.debian.org/debian-python/2022/01/msg2.html ) > > python-depinfo 1.7.0-1 > > python3-depinfo : retrieve and print Python 3 package dependencies Moved to Debian Python Team > > python-fitbit 0.3.1-2 > > python-fitbit-doc : FitBit REST API Client Implementation - > > Documentation > > python3-fitbit : FitBit REST API Client Implementation - Python 3 Should remain in Debian Med team (see https://lists.debian.org/debian-python/2022/01/msg2.html ) Will be continued later. Kind regards Andreas. > > python-duckpy 3.2.0-2 > > python3-duckpy : simple Python library for searching on DuckDuckGo > > python-easydev 0.12.0+dfsg-1 > > python3-easydev : common utilities to ease the development of > > Python packages (Python 3) > > python-etelemetry 0.2.0-4 > > python3-etelemetry : lightweight Python3 client to communicate > > with the etelemetry server > > python-hdmedians 0.14.2-3 > > python3-hdmedians : high-dimensional medians in Python3 > > python-leidenalg 0.8.8-1 > > python3-leidenalg : Python3 implementation of the Leiden algorithm in > > C++ > > python-lzstring 1.0.4-1.1 > > python3-lzstring : LZ-based compression algorithm for Python > > (Python 3 version) > > python-matplotlib-venn 0.11.6-2 > > python3-matplotlib-venn : Python 3 plotting area-proportional two- > > and three-way Venn diagrams > > python-multipletau 0.3.3+ds-3 > > python-multipletau-doc : documentation for multipletau Python module > > python3-multipletau : multiple-tau algorithm for Python3/NumPy > > python-multisplitby 0.0.1-4 > > python3-multisplitby : Python3 module to create iterables split on > > arbitrary separators > > python-ncls 0.0.63+ds-1 > > python3-ncls : datastructure for interval overlap queries > > python-pipdeptree 2.2.0-2 > > python3-pipdeptree : display dependency tree of the installed > > Python 3 packages > > python-pyflow 1.1.20-3 > > python3-pyflow : lightweight parallel task engine for Python > > python-pynndescent 0.5.2+dfsg-1 > > python3-pynndescent : nearest neighbor descent for approximate > > nearest neighbors > > python-pypubsub 4.0.3-5 > > python3-pubsub : Python 3 publish-subcribe library > > python-sinfo 0.3.1-2 > > python3-sinfo : print different version information for loaded modules > > python-spectra 0.0.11-3 > > python3-spectra : Easy color scales and color conversion for > > Python (Python 3 version) > > python-stdlib-list 0.8.0-4 > > python3-stdlib-list : List of Python Standard Libraries (2.6-7, 3.2-9) > > python-streamz 0.6.3-1 > > python3-streamz : build pipelines to manage continuous streams of data > > python-stubserver 1.1-2 > > python3-stubserver : mock tester of external web dependencies for Python > > python-tinyalign 0.2-5 > > python3-tinyalign : numerical representation of differences between > > strings > > python-typechecks 0.1.0+ds-2 > > python3-typechecks : express constraints on types > > python-upsetplot 0.6.0-2 > > python3-upsetplot : Draw Lex et al.'s UpSet plots with Pandas and > > Matplotlib > > python-wdlparse 0.1.0-2 > > python3-wdlparse : Workflow Description Language (WDL) parser for Python > > python-wordcloud 1.8.1+dfsg-2 > > python3-wordcloud : little word cloud generator in Python > > python-xopen 1.2.1-3 > > python3-xopen : Python3 module to open compressed files transparently > > smart-open 5.2.1-3 > > python3-smart-open : utils for streaming large files > > sorted-nearest 0.0.31+dfsg-1 > > python3-sorted-nearest : Cython helper library for pyranges > > sphinxcontrib-autoprogram 0.1.7-1 > > python3-sphinxcontrib.autoprogram : automated documentation of CLI > > programs for Sphinx (Python 3) > > > > Thanks, > > -- > > Sandro "morph" Tosi > > My website: http://sandrotosi.me/ > > Me at
Re: Transfering packages from Debian Med to DPT (Was: Please enable me transfering python-bioblend to Debian Med team)
Am Sun, Jan 02, 2022 at 01:04:46PM +0530 schrieb Nilesh Patra: > Before you/someone else makes a move, some of these packages are > bioinformatics > and are better suited for med team: > > * indexed-gzip - This one is mainly for NIFTI image files I fully agree here but I'd be happy to habd this over (and just did so) since I feel the competence for NIFTI quite sparsely settled in our team and thus I consider it well hosted in Debian Python Team. > * python-anndata - For gene annotation ACK (and wrote this also in my mail. > * python-fitbit - For FITBIT API (more in med domain) > * python-cooler - For genomic interaction data > > There are probably more, but please do not move these ^^ I will not move these. Kind regards Andreas. -- http://fam-tille.de
Re: Transfering packages from Debian Med to DPT (Was: Please enable me transfering python-bioblend to Debian Med team)
Am Sat, Jan 01, 2022 at 09:28:10PM -0500 schrieb Sandro Tosi:
> > In general we are open to hand over general packages that are not
> > directly touching the medical / biological field to competent hands. So
> > just ping me and I'll try to respond as quick as possible.
>
> with UDD-mirror U now, i was able to generate the below list. This
> is in no way a request to move them, just a potential source of data
> for your consideration
>
> arcp 0.2.1-3
> python3-arcp : (Archive and Package) URI parser and generator
Moved to Debian Python Team
> enlighten 1.7.2-1
> python3-enlighten : console progress bar module for Python3
> python3-enlighten-doc : console progress bar module for Python3
> (documentation)
> python3-enlighten-examples : console progress bar module for
> Python3 (examples)
Moved to Debian Python Team - I packaged version 1.8.0 which is the
last one that does not need the module prefixed (which is a new
dependency since version 1.9.0). Unfortunately the build time test
fails with:
...
WARNING: Retrying (Retry(total=1, connect=None, read=None, redirect=None,
status=None)) after connection broken by 'ProxyError('Cannot connect to
proxy.', NewConnectionError(': Failed to establish a new connection: [Errno 111] Connection
refused'))': /simple/blessed/
WARNING: Retrying (Retry(total=0, connect=None, read=None, redirect=None,
status=None)) after connection broken by 'ProxyError('Cannot connect to
proxy.', NewConnectionError(': Failed to establish a new connection: [Errno 111] Connection
refused'))': /simple/blessed/
ERROR: Could not find a version that satisfies the requirement
backports.functools-lru-cache>=1.2.1 (from blessed)
ERROR: No matching distribution found for backports.functools-lru-cache>=1.2.1
=== log end
ERROR: could not install deps [blessed]; v =
InvocationError('/build/enlighten-1.8.0/.tox/py310/bin/python -m pip install
blessed', 1)
___ summary
ERROR: py310: could not install deps [blessed]; v =
InvocationError('/build/enlighten-1.8.0/.tox/py310/bin/python -m pip install
blessed', 1)
E: pybuild pybuild:367: test: plugin distutils failed with: exit code=1: cd
/build/enlighten-1.8.0/.pybuild/cpython3_3.10/build; tox -c
/build/enlighten-1.8.0/tox.ini --sitepackages -e py310
I: pybuild base:237: cd /build/enlighten-1.8.0/.pybuild/cpython3_3.9/build; tox
-c /build/enlighten-1.8.0/tox.ini --sitepackages -e py39
May be you want to have a look to finalise the move to Debian Python Tem.
> h5sparse 0.1.0-4
> python3-h5sparse : Scipy sparse matrix in HDF5
Moved to Debian Python Team
> indexed-gzip 1.6.4-1
> python3-indexed-gzip : fast random access of gzip files in Python
Moved to Debian Python Team
> pyrle 0.0.33-2
> python3-pyrle : run length arithmetic in Python
Moved to Debian Python Team
> python-anndata 0.7.8-2
> python3-anndata : annotated gene by sample numpy matrix
^^
I think this package is nicely maintained by Debian Med team since it is
in the field of bioinformatics.
> python-avro 1.10.2+dfsg-1
> python3-avro : Apache Avro serialization system (Python 3 library)
Moved to Debian Python Team. After upgrading to latest upstream version
the build ends with
...
==
ERROR: test_server_with_path (avro.test.test_ipc.TestIPC)
--
Traceback (most recent call last):
File
"/build/python-avro-1.11.0+dfsg/.pybuild/cpython3_3.9_avro/build/avro/test/test_ipc.py",
line 35, in test_server_with_path
client_with_custom_path = avro.ipc.HTTPTransceiver("apache.org", 80,
"/service/article")
File
"/build/python-avro-1.11.0+dfsg/.pybuild/cpython3_3.9_avro/build/avro/ipc.py",
line 442, in __init__
self.conn.connect()
File "/usr/lib/python3.9/http/client.py", line 946, in connect
self.sock = self._create_connection(
File "/usr/lib/python3.9/socket.py", line 823, in create_connection
for res in getaddrinfo(host, port, 0, SOCK_STREAM):
File "/usr/lib/python3.9/socket.py", line 954, in getaddrinfo
for res in _socket.getaddrinfo(host, port, family, type, proto, flags):
socket.gaierror: [Errno -3] Temporary failure in name resolution
--
Ran 396 tests in 10.738s
FAILED (errors=1, skipped=2)
Unfortunately my time to investigate into this ends now.
I will continue with your list ... and wished moves in the other
direction could be as simple and unbureaucratic as it can be.
Kind regards
Andreas.
> python-ciso8601 2.2.0-1
> python3-ciso8601 : fast ISO8601 date time parser for Python written in C
> python-colormap 1.0.4-2
> python3-colormap : ease manipulation of matplotlib colormaps and
> color codecs (Python 3)
>
Re: Transfering packages from Debian Med to DPT (Was: Please enable me transfering python-bioblend to Debian Med team)
Before you/someone else makes a move, some of these packages are bioinformatics and are better suited for med team: * indexed-gzip - This one is mainly for NIFTI image files * python-anndata - For gene annotation * python-fitbit - For FITBIT API (more in med domain) * python-cooler - For genomic interaction data There are probably more, but please do not move these ^^ Nilesh OpenPGP_signature Description: OpenPGP digital signature
Re: Transfering packages from Debian Med to DPT (Was: Please enable me transfering python-bioblend to Debian Med team)
> > > Sandro, do you have any other packages in mind? > > > > too many to scan by-eyes only, so i planned on running some queries on > > UDD to figure some other package out, but the udd-mirror is down, so > > i'm going to provide a list (if any) later on. > > In general we are open to hand over general packages that are not > directly touching the medical / biological field to competent hands. So > just ping me and I'll try to respond as quick as possible. with UDD-mirror U now, i was able to generate the below list. This is in no way a request to move them, just a potential source of data for your consideration arcp 0.2.1-3 python3-arcp : (Archive and Package) URI parser and generator enlighten 1.7.2-1 python3-enlighten : console progress bar module for Python3 python3-enlighten-doc : console progress bar module for Python3 (documentation) python3-enlighten-examples : console progress bar module for Python3 (examples) h5sparse 0.1.0-4 python3-h5sparse : Scipy sparse matrix in HDF5 indexed-gzip 1.6.4-1 python3-indexed-gzip : fast random access of gzip files in Python pyrle 0.0.33-2 python3-pyrle : run length arithmetic in Python python-anndata 0.7.8-2 python3-anndata : annotated gene by sample numpy matrix python-avro 1.10.2+dfsg-1 python3-avro : Apache Avro serialization system (Python 3 library) python-ciso8601 2.2.0-1 python3-ciso8601 : fast ISO8601 date time parser for Python written in C python-colormap 1.0.4-2 python3-colormap : ease manipulation of matplotlib colormaps and color codecs (Python 3) python-colormath 3.0.0-1.1 python3-colormath : Abstracts common color math operations (Python 3 version) python-cooler 0.8.11-1 python3-cooler : library for a sparse, compressed, binary persistent storage python3-cooler-examples : library for a sparse, compressed, binary persistent storage (examples) python-depinfo 1.7.0-1 python3-depinfo : retrieve and print Python 3 package dependencies python-duckpy 3.2.0-2 python3-duckpy : simple Python library for searching on DuckDuckGo python-easydev 0.12.0+dfsg-1 python3-easydev : common utilities to ease the development of Python packages (Python 3) python-etelemetry 0.2.0-4 python3-etelemetry : lightweight Python3 client to communicate with the etelemetry server python-fitbit 0.3.1-2 python-fitbit-doc : FitBit REST API Client Implementation - Documentation python3-fitbit : FitBit REST API Client Implementation - Python 3 python-hdmedians 0.14.2-3 python3-hdmedians : high-dimensional medians in Python3 python-leidenalg 0.8.8-1 python3-leidenalg : Python3 implementation of the Leiden algorithm in C++ python-lzstring 1.0.4-1.1 python3-lzstring : LZ-based compression algorithm for Python (Python 3 version) python-matplotlib-venn 0.11.6-2 python3-matplotlib-venn : Python 3 plotting area-proportional two- and three-way Venn diagrams python-multipletau 0.3.3+ds-3 python-multipletau-doc : documentation for multipletau Python module python3-multipletau : multiple-tau algorithm for Python3/NumPy python-multisplitby 0.0.1-4 python3-multisplitby : Python3 module to create iterables split on arbitrary separators python-ncls 0.0.63+ds-1 python3-ncls : datastructure for interval overlap queries python-pipdeptree 2.2.0-2 python3-pipdeptree : display dependency tree of the installed Python 3 packages python-pyflow 1.1.20-3 python3-pyflow : lightweight parallel task engine for Python python-pynndescent 0.5.2+dfsg-1 python3-pynndescent : nearest neighbor descent for approximate nearest neighbors python-pypubsub 4.0.3-5 python3-pubsub : Python 3 publish-subcribe library python-sinfo 0.3.1-2 python3-sinfo : print different version information for loaded modules python-spectra 0.0.11-3 python3-spectra : Easy color scales and color conversion for Python (Python 3 version) python-stdlib-list 0.8.0-4 python3-stdlib-list : List of Python Standard Libraries (2.6-7, 3.2-9) python-streamz 0.6.3-1 python3-streamz : build pipelines to manage continuous streams of data python-stubserver 1.1-2 python3-stubserver : mock tester of external web dependencies for Python python-tinyalign 0.2-5 python3-tinyalign : numerical representation of differences between strings python-typechecks 0.1.0+ds-2 python3-typechecks : express constraints on types python-upsetplot 0.6.0-2 python3-upsetplot : Draw Lex et al.'s UpSet plots with Pandas and Matplotlib python-wdlparse 0.1.0-2 python3-wdlparse : Workflow Description Language (WDL) parser for Python python-wordcloud 1.8.1+dfsg-2 python3-wordcloud : little word cloud generator in Python python-xopen 1.2.1-3 python3-xopen : Python3 module to open compressed files transparently smart-open 5.2.1-3 python3-smart-open : utils for streaming large files sorted-nearest 0.0.31+dfsg-1 python3-sorted-nearest : Cython helper library for pyranges sphinxcontrib-autoprogram 0.1.7-1
Re: Transfering packages from Debian Med to DPT (Was: Please enable me transfering python-bioblend to Debian Med team)
Hi Sandro, Am Thu, Dec 23, 2021 at 09:52:49AM -0500 schrieb Sandro Tosi: > > Thus I moved mypy now and moved it to DPT[2]. Feel free to add yourself > > to Uploaders and upload with the new location. > > thanks! You are welcome. > > Sandro, do you have any other packages in mind? > > too many to scan by-eyes only, so i planned on running some queries on > UDD to figure some other package out, but the udd-mirror is down, so > i'm going to provide a list (if any) later on. In general we are open to hand over general packages that are not directly touching the medical / biological field to competent hands. So just ping me and I'll try to respond as quick as possible. Please also note: I'd be really happy if for any of the DPT packages featuring my ID as Uploader if somebody wants to add another ID and become an Uploader of that package. I have way more packages on my table than I really want to have. Kind regards Andreas. -- http://fam-tille.de
Re: Transfering packages from Debian Med to DPT (Was: Please enable me transfering python-bioblend to Debian Med team)
> Thus I moved mypy now and moved it to DPT[2]. Feel free to add yourself > to Uploaders and upload with the new location. thanks! > Sandro, do you have any other packages in mind? too many to scan by-eyes only, so i planned on running some queries on UDD to figure some other package out, but the udd-mirror is down, so i'm going to provide a list (if any) later on. Thanks, -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi Twitter: https://twitter.com/sandrotosi
Re: Transfering packages from Debian Med to DPT (Was: Please enable me transfering python-bioblend to Debian Med team)
Hi, Am Thu, Dec 23, 2021 at 02:07:45PM +0530 schrieb Nilesh Patra: > On 12/23/21 1:54 PM, Andreas Tille wrote: > > Hi again, > > > > by chance I learned that I do not have permissions to create > > repositories in salsa:python-team/packages thus moving packages would be > > not as simple as transfering the projects. Please grant me maintainer > > permissions to enable moving packages smoothly. > > AFAICS here[1] you do have maintainer permissions. Hmmm, that's correct and I confirm I can create repositories manually (just my script failed and I did not checked on salsa.) Thus I moved mypy now and moved it to DPT[2]. Feel free to add yourself to Uploaders and upload with the new location. Sandro, do you have any other packages in mind? Hope this helps Andreas. [2] https://salsa.debian.org/python-team/packages/mypy/-/commit/8bca8da1ca92302b921755318d3325d53b6e0a47 -- http://fam-tille.de
Re: Transfering packages from Debian Med to DPT (Was: Please enable me transfering python-bioblend to Debian Med team)
On 12/23/21 1:54 PM, Andreas Tille wrote: Hi again, by chance I learned that I do not have permissions to create repositories in salsa:python-team/packages thus moving packages would be not as simple as transfering the projects. Please grant me maintainer permissions to enable moving packages smoothly. AFAICS here[1] you do have maintainer permissions. [1]: https://salsa.debian.org/groups/python-team/packages/-/group_members?search=tille Regards, Nilesh
Transfering packages from Debian Med to DPT (Was: Please enable me transfering python-bioblend to Debian Med team)
Hi again, by chance I learned that I do not have permissions to create repositories in salsa:python-team/packages thus moving packages would be not as simple as transfering the projects. Please grant me maintainer permissions to enable moving packages smoothly. Kind regards Andreas. Am Wed, Dec 22, 2021 at 10:06:10PM +0100 schrieb Andreas Tille: > Hi Sandro, > > Am Wed, Dec 22, 2021 at 03:13:28PM -0500 schrieb Sandro Tosi: > > > Please note: The people involved are the same. We are members of > > > both teams but consider the Debian Med team more appropriate. We > > > are simply missing the permissions to do the move properly. > > > > since you're talking about the appropriate team to maintain a given > > package (and it seems debian-med may be more suited for bioblend), are > > you also going to move all non-bio/med python packages from debian-med > > to dpt? because that's the more appropriate place for things like > > mypy. > > Yes, for sure. Some packages somehow appeared for historical reasons in > Debian Med but I'm fine to move those packages you consider more > sensible in Python team (without any bureaucracy - I think for the move > into this direction I own the proper permissions). > > Feel free to make a list if there are more packages than mypy. > > Kind regards > >Andreas. > > -- > http://fam-tille.de > > -- http://fam-tille.de
Re: Please enable me transfering python-bioblend to Debian Med team
Hi Sandro, Am Wed, Dec 22, 2021 at 03:13:28PM -0500 schrieb Sandro Tosi: > > Please note: The people involved are the same. We are members of > > both teams but consider the Debian Med team more appropriate. We > > are simply missing the permissions to do the move properly. > > since you're talking about the appropriate team to maintain a given > package (and it seems debian-med may be more suited for bioblend), are > you also going to move all non-bio/med python packages from debian-med > to dpt? because that's the more appropriate place for things like > mypy. Yes, for sure. Some packages somehow appeared for historical reasons in Debian Med but I'm fine to move those packages you consider more sensible in Python team (without any bureaucracy - I think for the move into this direction I own the proper permissions). Feel free to make a list if there are more packages than mypy. Kind regards Andreas. -- http://fam-tille.de
Re: Please enable me transfering python-bioblend to Debian Med team
Nilesh Patra wrote on 22/12/2021 at 20:45:53+0100: > [[PGP Signed Part:No public key for 00BAE74B343369F1 created at > 2021-12-22T20:45:49+0100 using RSA]] > Hi Pierre-Elliot, > > On Wed, Dec 22, 2021 at 08:06:01PM +0100, Pierre-Elliott Bécue wrote: >> >> I'm sorry but pressuring to take over a package is not really fine. If >> >> you're not happy with the time it takes for an answer, you can try to >> >> fill an ITS and if the procedure goes to its end then you may take over. >> > >> > Please note: The people involved are the same. We are members of >> > both teams but consider the Debian Med team more appropriate. We >> > are simply missing the permissions to do the move properly. >> >> I am aware of that. >> >> Yet, the fact that you are members of both teams doesn't entitle you to >> decide such a transfer, even if you had the technical rights to do so. > > Hmm, I am not sure what the problem in such a case would be (permission in > both teams) > Steffen is the maintainer (uploader if you might prefer it that way) and he > has > agreed already[1] -- so what's the problem? > > [1]: https://lists.debian.org/debian-med/2021/12/msg00119.html I guess the problem is that the python-team doesn't seem to have been Cc-ed in your exchange, which was not quoted in the initial mail of this thread. As I'm not subscribed to the list, it really looked like you were intending to take over a package without any maintainer of it having been asked for it before. As it seems not to be the case, it's not the same at all. >> I therefore stand my point: the way Debian is made has not changed >> recently, and taking over still requires a formal approval from the >> maintainer, which you are not. >> >> The only alternatives are either an ITS or MIA team orphaning their >> packages, but as the maintainer is an active team, the latter will not >> happen. > > I do not think it is sensible to take consensus from an entire team to > move a single package. I did not suggest to wait for a consensus, but rather that an admin asks if someone is against and waits for a reasonable delay (72 hours?) and then makes the transfer if they're happy with it. > Honestly speaking, we really do not need to make team transfer debian > processes such a high friction ones -- it just stalls the work for no > good reason. The package has not seen uploads since more than two > years, I really doubt anyone in the team feels strong ly about not > moving it. There is no real difference between teams and individual developers on that part: a take over has to be approved or to follow due procedures, whether we like it or not. Here, as Steffen gave his approval, the topic is a bit moot. > If you are talking about Ondřej doing the uploads apart from the > initial uploads, then you probably are also aware that Ondřej does a > number of team-maintained package uploads to fix bugs, does updates > and so on (a lot of us do so, for that matter albeit in other teams) I > really don't think that he has a personal interest in every single one > of those packages (including this one) but we should hear from him. I was under the (false) impression that Steffen was not currently available to reply to your query. Ondřej being an admin of the team and having done all the uploads apart from those done by Steffen, he clearly seemed the best second contact point to ask this transfer. >> >> and they could be willing to check that no one in the team objects. > > Sure but how are you making a "check" here? I do have admin access in > a few teams, and speaking for myself: I would send out an email to the > list, wait for a time frame (maximum 1 week) and check if someone has > any comments If not, I would make a move. So we already have a mail > in the debian-python mailing list, and no objections so far, so > > I would have probably done more to ask for consensus better (asking on > IRC channels etc) but admittedly, we only have 24 hours in the day, > and several dozens of packages to do. Asking globally on the list and waiting a reasonable amount of time for a potential grunt is fine with me. >> I think you missed the second part of my sentence you're quoting. > > I recetified this above. > >> >> Steffen only did the first upload. I'd suggest to contact Ondrej (Cc-ed). >> >> >> >> In the meantime, Nilesh is member of the Python team and therefore can >> >> do an update of the package (but not change the maintainer). >> > >> > I'm a member myself - but the upload should happen in the Debian >> > Med team. This is the point of my mail. >> >> I disagree. >> >> Either the python team accepts the package to be transferred and it >> indeed should happen there. > > Please don't repeat your points. You wrote the same stuff above (wrt > MIA, ITS etc) If many part of the same mail are raising the same point I prefer repeating these. >> This probably means we should have a stanza in the DPT policy about >> transfer of maintainership. > > This would
Re: Please enable me transfering python-bioblend to Debian Med team
Andreas, On Wed, Dec 22, 2021 at 1:42 PM Andreas Tille wrote: > > Am Wed, Dec 22, 2021 at 06:13:32PM +0100 schrieb Pierre-Elliott Bécue: > > > > Andreas Tille wrote on 21/12/2021 at 15:43:11+0100: > > > > > Ping? Could any admin of Debian Python Team help out? We can simply > > > recreate the repository in Debian Med and move on ... but that might > > > be confusing for users who will find two clones in differen teams. > > > Thank you, Andreas. > > > > I'm sorry but pressuring to take over a package is not really fine. If > > you're not happy with the time it takes for an answer, you can try to > > fill an ITS and if the procedure goes to its end then you may take over. > > Please note: The people involved are the same. We are members of > both teams but consider the Debian Med team more appropriate. We > are simply missing the permissions to do the move properly. since you're talking about the appropriate team to maintain a given package (and it seems debian-med may be more suited for bioblend), are you also going to move all non-bio/med python packages from debian-med to dpt? because that's the more appropriate place for things like mypy. Thanks, -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi Twitter: https://twitter.com/sandrotosi
Re: Please enable me transfering python-bioblend to Debian Med team
Hi Pierre-Elliot, On Wed, Dec 22, 2021 at 08:06:01PM +0100, Pierre-Elliott Bécue wrote: > >> I'm sorry but pressuring to take over a package is not really fine. If > >> you're not happy with the time it takes for an answer, you can try to > >> fill an ITS and if the procedure goes to its end then you may take over. > > > > Please note: The people involved are the same. We are members of > > both teams but consider the Debian Med team more appropriate. We > > are simply missing the permissions to do the move properly. > > I am aware of that. > > Yet, the fact that you are members of both teams doesn't entitle you to > decide such a transfer, even if you had the technical rights to do so. Hmm, I am not sure what the problem in such a case would be (permission in both teams) Steffen is the maintainer (uploader if you might prefer it that way) and he has agreed already[1] -- so what's the problem? [1]: https://lists.debian.org/debian-med/2021/12/msg00119.html > I therefore stand my point: the way Debian is made has not changed > recently, and taking over still requires a formal approval from the > maintainer, which you are not. > > The only alternatives are either an ITS or MIA team orphaning their > packages, but as the maintainer is an active team, the latter will not > happen. I do not think it is sensible to take consensus from an entire team to move a single package. Honestly speaking, we really do not need to make team transfer debian processes such a high friction ones -- it just stalls the work for no good reason. The package has not seen uploads since more than two years, I really doubt anyone in the team feels strong ly about not moving it. If you are talking about Ondřej doing the uploads apart from the initial uploads, then you probably are also aware that Ondřej does a number of team-maintained package uploads to fix bugs, does updates and so on (a lot of us do so, for that matter albeit in other teams) I really don't think that he has a personal interest in every single one of those packages (including this one) but we should hear from him. > >> and they could be willing to check that no one in the team objects. Sure but how are you making a "check" here? I do have admin access in a few teams, and speaking for myself: I would send out an email to the list, wait for a time frame (maximum 1 week) and check if someone has any comments If not, I would make a move. So we already have a mail in the debian-python mailing list, and no objections so far, so I would have probably done more to ask for consensus better (asking on IRC channels etc) but admittedly, we only have 24 hours in the day, and several dozens of packages to do. > I think you missed the second part of my sentence you're quoting. I recetified this above. > >> Steffen only did the first upload. I'd suggest to contact Ondrej (Cc-ed). > >> > >> In the meantime, Nilesh is member of the Python team and therefore can > >> do an update of the package (but not change the maintainer). > > > > I'm a member myself - but the upload should happen in the Debian > > Med team. This is the point of my mail. > > I disagree. > > Either the python team accepts the package to be transferred and it > indeed should happen there. Please don't repeat your points. You wrote the same stuff above (wrt MIA, ITS etc) > This probably means we should have a stanza in the DPT policy about > transfer of maintainership. This would be definitely helpful. PS: I do not mean to be disrespectful, please do not interpret my reply that way, I am only trying to reason it out. Regards, Nilesh signature.asc Description: PGP signature
Re: Please enable me transfering python-bioblend to Debian Med team
Andreas Tille wrote on 22/12/2021 at 19:42:26+0100: > Am Wed, Dec 22, 2021 at 06:13:32PM +0100 schrieb Pierre-Elliott Bécue: >> >> Andreas Tille wrote on 21/12/2021 at 15:43:11+0100: >> >> > Ping? Could any admin of Debian Python Team help out? We can simply >> > recreate the repository in Debian Med and move on ... but that might >> > be confusing for users who will find two clones in differen teams. >> > Thank you, Andreas. >> >> I'm sorry but pressuring to take over a package is not really fine. If >> you're not happy with the time it takes for an answer, you can try to >> fill an ITS and if the procedure goes to its end then you may take over. > > Please note: The people involved are the same. We are members of > both teams but consider the Debian Med team more appropriate. We > are simply missing the permissions to do the move properly. I am aware of that. Yet, the fact that you are members of both teams doesn't entitle you to decide such a transfer, even if you had the technical rights to do so. I therefore stand my point: the way Debian is made has not changed recently, and taking over still requires a formal approval from the maintainer, which you are not. The only alternatives are either an ITS or MIA team orphaning their packages, but as the maintainer is an active team, the latter will not happen. >> Apart from that, you'll need for an admin of the team to do the transfer, >> and they could be willing to check that no one in the team objects. > > Yes, we need an admin and that was I'm asking for. I think you missed the second part of my sentence you're quoting. >> Steffen only did the first upload. I'd suggest to contact Ondrej (Cc-ed). >> >> In the meantime, Nilesh is member of the Python team and therefore can >> do an update of the package (but not change the maintainer). > > I'm a member myself - but the upload should happen in the Debian > Med team. This is the point of my mail. I disagree. Either the python team accepts the package to be transferred and it indeed should happen there. Or you're in a hurry and you should not change the maintainer field and still do your upload. This probably means we should have a stanza in the DPT policy about transfer of maintainership. -- Pierre-Elliott Bécue signature.asc Description: PGP signature
Re: Please enable me transfering python-bioblend to Debian Med team
Am Wed, Dec 22, 2021 at 06:13:32PM +0100 schrieb Pierre-Elliott Bécue: > > Andreas Tille wrote on 21/12/2021 at 15:43:11+0100: > > > Ping? Could any admin of Debian Python Team help out? We can simply > > recreate the repository in Debian Med and move on ... but that might > > be confusing for users who will find two clones in differen teams. > > Thank you, Andreas. > > I'm sorry but pressuring to take over a package is not really fine. If > you're not happy with the time it takes for an answer, you can try to > fill an ITS and if the procedure goes to its end then you may take over. Please note: The people involved are the same. We are members of both teams but consider the Debian Med team more appropriate. We are simply missing the permissions to do the move properly. > Apart from that, you'll need for an admin of the team to do the transfer, > and they could be willing to check that no one in the team objects. Yes, we need an admin and that was I'm asking for. > Steffen only did the first upload. I'd suggest to contact Ondrej (Cc-ed). > > In the meantime, Nilesh is member of the Python team and therefore can > do an update of the package (but not change the maintainer). I'm a member myself - but the upload should happen in the Debian Med team. This is the point of my mail. Kind regards Andreas. -- http://fam-tille.de
Re: Please enable me transfering python-bioblend to Debian Med team
Andreas Tille wrote on 21/12/2021 at 15:43:11+0100: > Ping? Could any admin of Debian Python Team help out? We can simply > recreate the repository in Debian Med and move on ... but that might > be confusing for users who will find two clones in differen teams. > Thank you, Andreas. I'm sorry but pressuring to take over a package is not really fine. If you're not happy with the time it takes for an answer, you can try to fill an ITS and if the procedure goes to its end then you may take over. Apart from that, you'll need for an admin of the team to do the transfer, and they could be willing to check that no one in the team objects. Steffen only did the first upload. I'd suggest to contact Ondrej (Cc-ed). In the meantime, Nilesh is member of the Python team and therefore can do an update of the package (but not change the maintainer). With best regards, -- PEB signature.asc Description: PGP signature
Re: Please enable me transfering python-bioblend to Debian Med team
Ping? Could any admin of Debian Python Team help out? We can simply recreate the repository in Debian Med and move on ... but that might be confusing for users who will find two clones in differen teams. Thank you, Andreas. Am Sun, Dec 19, 2021 at 05:06:43PM +0100 schrieb Andreas Tille: > Hi, > > we want to take over python-bioblend to Debian Med team. Unfortunately > the transfer procedure requires owner permissions to remove the package > from the old place. Could someone grant Nilesh Patra or me owner > permissions on this package? Alternatively I can grant maintainer > permissions to some python-team owner to move the package over. > > Kind regards > >Andreas. > > -- > http://fam-tille.de > > -- http://fam-tille.de
Please enable me transfering python-bioblend to Debian Med team
Hi, we want to take over python-bioblend to Debian Med team. Unfortunately the transfer procedure requires owner permissions to remove the package from the old place. Could someone grant Nilesh Patra or me owner permissions on this package? Alternatively I can grant maintainer permissions to some python-team owner to move the package over. Kind regards Andreas. -- http://fam-tille.de
