Re: Bug#1063957: python-pytest-lazy-fixture: autopkgtest regression with pytest 8
Le mar. 14 mai 2024 à 08:35, Julian Gilbey a écrit : > > On Mon, May 13, 2024 at 11:07:54PM +0200, Alexandre Detiste wrote: > > Le lun. 13 mai 2024 à 22:59, Scott Kitterman a écrit > > : > > > >I suggest that we soon ask ftpmaster to drop pytest-lazy-fixture from > > > >Debian unstable. > > > > > > Please transition all the rdepends first. Asking before that's done > > > just creates more work for everyone. > > > > > > Scott K > > > > It looks like for this one package it's already clear. > > > > @Julian: here it looks you forgot to check build-depends: > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067200 > > Oh, gosh, I thought I had done so (this is cython3-legacy), but I > clearly made a serious mistake in my attempt! I made a mistake in my attempt too..., here's the real list: Maintainer: Sandro Tosi Package: prettytable Maintainer: Debian GIS Project -> CC'ing Antonio Package: pycoast Package: pyresample Maintainer: Debian Python Team Package: python-django-timezone-field Package: python-limits Package: python-marshmallow-sqlalchemy
Re: Bug#1063957: python-pytest-lazy-fixture: autopkgtest regression with pytest 8
Le lun. 13 mai 2024 à 22:59, Scott Kitterman a écrit : > >I suggest that we soon ask ftpmaster to drop pytest-lazy-fixture from > >Debian unstable. > > Please transition all the rdepends first. Asking before that's done just > creates more work for everyone. > > Scott K It looks like for this one package it's already clear. @Julian: here it looks you forgot to check build-depends: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067200 I don't know what's the best way to check this, I use this template hereunder Greetings #!/bin/sh Sources=/var/lib/apt/lists/ftp.*.debian.org_debian_dists_unstable_*_source_Sources Packages=/var/lib/apt/lists/ftp.*.debian.org_debian_dists_unstable_*_binary-amd64_Packages ben query '.build-depends ~ "python3-lazy-fixture"' $Sources -s Package,Maintainer ben query '.build-depends-indep ~ "python3-lazy-fixture"' $Sources -s Package,Maintainer ben query '.depends ~ "python3-lazy-fixture"' $Packages -s Package,Maintaine
Re: Status of pymodbus (was: Status of sqlalchemy)
helper.py is not so helpful (and not even used in test/conftest.py ?) anyway it builds now but maybe upstream would accept a patch to help reduce the downstream patch (maybe read certificates location from env variable, this needs more eyes) It's almost done. Greetings Le mar. 23 avr. 2024 à 00:06, Martin a écrit : > > Hi Alexandre, > > I pushed my changes to debian/master. If you have time to work on > pymodbus (e.g. update disable-failing-unittests.patch), please go on. > I probably can't work on that this week. > > Cheers
Re: Bug#1065325: morph's abandoned packages (list)
Yes do please. Le sam. 11 mai 2024 à 20:51, Nilesh Patra a écrit : > > Quoting Alexandre Detiste : > > I would pick-up matplotlib I guess, I have some special connection to it, > > It was one the packages that enabled me to escape > > my horrible SAS-Insitute powered previous job/life. > > > > It's a big one. > > > > Help is appreciated, I already cherry picked some commits from Ciel's PR. > > Would you consider to add me in as an Uploader (co-maintainer) alongside you? > > I am a Debian Developer. > > Best, > Nilesh
Bug#1070772: ITP: python-mutf8 -- encoders and decoders for the MUTF-8 character encoding
Package: wnpp Severity: wishlist Owner: Alexandre Detiste X-Debbugs-Cc: debian-de...@lists.debian.org, debian-python@lists.debian.org * Package name: python-mutf8 Version : 1.0.0 Upstream Contact: Tyler Kennedy * URL : https://pypi.org/project/mutf8/ * License : MIT Programming Lang: Python Description : encoders and decoders for the MUTF-8 character encoding This package contains simple pure-python as well as C encoders and decoders for the MUTF-8 character encoding. In most cases, it can also parse the even-rarer CESU-8. These days, you'll most likely encounter MUTF-8 when working on files or protocols related to the JVM. Strings in a Java .class file are encoded using MUTF-8, strings passed by the JNI, as well as strings exported by the object serializer. This library was extracted from Lawu, a Python library for working with JVM class files. I will maintain this inside DPT. This is a new dependency of androguard
Re: please be more careful about your team uploads
It is now in the NEW queue. https://salsa.debian.org/python-team/packages/python-pytest-relaxed/-/pipelines/675307 Le mer. 8 mai 2024 à 16:19, Antoine Beaupré a écrit : > On 2024-05-08 16:11:46, Alexandre Detiste wrote: > > Ok I guess you want to do this one: > > > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008768 > > Not really! It's a RFP, if I was going to do it, I would have renamed > that package to "ITP" and reassigned it... > > a.
Re: please be more careful about your team uploads
Ok I guess you want to do this one: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008768
Re: please be more careful about your team uploads
Hi, That was the very first day I got to work on DPT packages; so well yes, I did some mistakes at first; and having been DM for far too long (~10 years) I needed to retrain; I had so many things stuck in my queue at first. https://lists.debian.org/debian-python/2023/12/msg00012.html I'm now going through the ITP's needed for stalled package updates. Greetings Le mer. 8 mai 2024 à 15:58, Antoine Beaupré a écrit : > > Hi, > > I'm working on updating the python-invoke package and see you've done > two uploads on the package: > > https://tracker.debian.org/news/1491303/accepted-python-invoke-200-11-source-into-unstable/ > https://tracker.debian.org/news/1491393/accepted-python-invoke-200-12-source-into-unstable/ > > So, first off: thanks for fixing those issues! :) > > But, second, could you be a little more careful about how you do those? > Normally, I would have expected those changes to be pushed to salsa so > that I can build on top of. > > Or, at the very least, you should have sent a debdiff... The uploads are > a little bizarre too, because they have a NMU-like versionn number > (e.g. 2.0.0-1.1) yet they say "Team upload" on the changelog. Clearly > that should have yielded lintian warnings, did you ignore those? > > In any case, i'm now in the rather unfortunate position of having to > retrofit that stuff back in the package, and it's making my life a > little harder than it should... > > So please be a little more careful next time around, thanks! > > a.
paramiko: FTBFS: dh_auto_test: error: pybuild
> E ModuleNotFoundError: No module named 'six' This happens because we unknot the python3-mock -> python3-pbr -> python3-six dependency chain. I did this _on purpose_ to discover missing python3-six (build-)dependencies and/or upstream that needs a cleanup. Here it's of course better to do this long overdue paramiko update than merely adding python3-six as build-dep for a quick fix. Greetings and thank you https://tracker.debian.org/news/1492697/accepted-python-mock-510-1-source-into-unstable/ python-mock (5.1.0-1) unstable; urgency=medium . * Team Upload * New upstream version 5.1.0 (Closes: #717192, #717193, #1030887) (LP: #1248066) * remove obsolete build-dep python3-pbr & python3-unittest2 * use new dh-sequence-python3 https://tracker.debian.org/news/1505240/accepted-python-pbr-600-1-source-into-unstable/ python-pbr (6.0.0-1) unstable; urgency=medium . * New upstream release (Closes: #1060153). * Do not use six anymore.
RM: pyannotate -- ROM; leaf package
control: tag -1 -moreinfo This one should still be removed ... It hasn't moved an inch still 2019 https://github.com/dropbox/pyannotate https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065045
Re: Status of pymodbus (was: Status of sqlalchemy)
Le lun. 22 avr. 2024, 09:57, Martin a écrit : > > 1. privacy-breach-fixes.patch (I updated this, can push > These ones are annoying to maintain. I wish dh_installdocs would be smart enough to strip these tiny widget that are present in so many Readme.md on GitHub. They re quite formulaic and it could be done with a regexp (but dh is in Perl ). Thanks
Re: Status of pymodbus (was: Status of sqlalchemy)
Hi, I ll check back home, but it's most likely I was waiting for SQLAlchemy 2.xx. I know for share that one package does wait for SA 2.xx but can t remember which one. > It looks like all but one of the debian/patches are obsolete now? Sure Le lun. 22 avr. 2024, 08:09, Martin a écrit : > On 2024-04-15 11:38, Alexandre Detiste wrote: > > Le lun. 15 avr. 2024 à 11:20, Thomas Goirand a écrit : > >> The rest of: > >> - pymodbus > >> > >> I don't even know what they do. > > > > Life is better when one does not have to deal with modbus :-) > > Yes! > > > This package is outdated and need a refresh. > > As I see, you already pushed a new upstream to git in January/February, > but did not yet upload the package. Are there any blockers? It looks > like all but one of the debian/patches are obsolete now? >
Re: Orphaning mu-editor, firmware-microbit-micropython, and their (build)-deps
Hi, I understand you. Maybe the best option is to co-maintain this outside of the D Python Team. Greetings Le sam. 20 avr. 2024, 01:56, Keith Packard a écrit : > > > Now Keith can rebase his changes unto that. > > My changes involve stripping the non-DFSG elements out of the package, > and that requires shipping a non-upstream .tar.gz file for the source > archive. Because of that, I'm using a pure git process and not bothering > to generate pristine tar bits -- there's no usable upstream tarball > anyways. > > I'm willing to continue to maintain this package using that process, but > I don't really have any interest in using the existing python packagers > process because I don't think it applies in this case. > > -- > -keith >
Re: Orphaning mu-editor, firmware-microbit-micropython, and their (build)-deps
Hi, I did this upstream bump because I think that MR on upstream & pristine-tar brach should not be allowed. (the Games Team did received several such MR from XZ-hack "Hans Jansen" puppet socket) Now Keith can rebase his changes unto that. Greetings Le sam. 20 avr. 2024, 00:34, Nick Morrott > Keith Packard (CC'd) is interested in contributing and co-maintaining > mu-editor, and there is a current MR in the repo. The mu-editor > repository has also just had a drive-by upstream bump to version 1.2.0 > but nothing else so far... > > Thanks, > Nick > >
Re: Status of sqlalchemy
Le lun. 15 avr. 2024 à 11:20, Thomas Goirand a écrit : > The rest of: > - pymodbus > > I don't even know what they do. Life is better when one does not have to deal with modbus :-) This package is outdated and need a refresh. > All that to say: I'm ok at this point if SQLA 2.x is uploaded to Sid and > we move on... Agreed, please move on
Fwd: [cdent/paste] Potentially ceasing development of Paste (Discussion #91)
Might interrest more here. -- Forwarded message - De : Chris Dent Date: ven. 5 avr. 2024, 19:18 Subject: [cdent/paste] Potentially ceasing development of Paste (Discussion #91) To: cdent/paste Cc: Alexandre Detiste , Mention < ment...@noreply.github.com> paste uses a lot of deprecated functionality, much of it related to old libraries like cgi and cgitb. When Python 3.13 becomes the main Python release this deprecated functionality will be removed and without a fair bit of work paste will stop working. I personally do not think we should continue to maintain paste. It is an old tool using old technology that is no longer aligned with modern techniques or tools. I would like us to consider winding it down but I'm not certain who should be involved in the discussion so pinging some of the people who have made contributions to the project over the last while: @a-detiste <https://github.com/a-detiste> , @amitmarkel <https://github.com/amitmarkel> , @benjaminp <https://github.com/benjaminp> , @Cito <https://github.com/Cito> , @cjwatson <https://github.com/cjwatson> , @CyrilRoelandteNovance <https://github.com/CyrilRoelandteNovance> , @blueyed <https://github.com/blueyed> , @brondsem <https://github.com/brondsem> , @hugovk <https://github.com/hugovk> , and of course @ianb <https://github.com/ianb> . Please register your opinion. If you feel like paste should carry on living, and want to volunteer to take over maintenance I'm very willing to transfer ownership. I also maintain pastescript and feel it should end too, so if someone wants to take them as a package deal that would be great. — Reply to this email directly, view it on GitHub <https://github.com/cdent/paste/discussions/91>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AB47WUDN2YPOYOCW6TVPC5TY33MGFAVCNFSM6ABFZQFRXSVHI2DSMVQWIX3LMV43ERDJONRXK43TNFXW4OZWGQ3DKMBVGQ> . You are receiving this because you were mentioned.Message ID:
Re: Requests to join DPT haven't been processed for months
Thank you both Le mer. 3 avr. 2024 à 17:48, Christian Kastner a écrit : > > On 2024-04-03 16:50, Stefano Rivera wrote: > > We've added a new owner to help out. Thanks peb! > > > > Stefano > > Excellent, thanks Stefano and of course Pierre-Elliott for taking care > of this! > > Best, > Christian >
Re: New upstream version for python-pint
I've packaged font-awesome5 at work, for sure it's not in Debian. The upgrade to v5 was rightfully reverted but it's in limbo since. https://packages.debian.org/sid/fonts-font-awesome fonts-font-awesome (5.0.10+really4.7.0~dfsg-4.1) <-- Please note that this package provides Font Awesome 4 (not Font Awesome 5 or Font Awesome 6 which are different fonts with different licensing). Le lun. 1 avr. 2024 à 21:26, Antonio Valentino a écrit : > > Dear Thomas, > > Il 01/04/24 17:52, Thomas Goirand ha scritto: > > On 3/31/24 21:05, Antonio Valentino wrote: > >> Dear Thomas, > >> > >> Il 30/03/24 22:25, Thomas Goirand ha scritto: > >>> On 3/29/24 15:13, Antonio Valentino wrote: > Dear Thomas and Ondřej, > a couple of packages that I maintain are impacted by an RC bug in > python-pint (#1067318). > I think that an update to the to the latest pint version 0.23 should > be sufficient to fix the issue. > > If you agree, I would like prepare the package for the new upstream > version in the salsa. > Of course I will let to you the review and upload. > > Please let me know, > > > kind regards > >>> > >>> Please go ahead and feel free to add yourself as uploader. > >>> > >>> Thomas > >> > >> Thanks Thomas > >> The packages is now updated in salsa. > >> Unfortunately the reprotest job fails in CI, but I'm not able to > >> reproduce on my laptop and it seems not to be a regression. > >> I will try to fix it in future uploads but for the moment I would > >> prefer to have an upload to fix a couple of RC bugs. > >> > >> Could you please review and upload? > >> > >> I have also put myself as uploader. > >> I'm a DM so I kindly ask you to grant me upload permissions as > >> described in [3]. > >> > >> > >> kind regards > > > > Hi! > > > > Thanks for the work Antonio. > > > > 1/ In the clean target, please also clean: > > - Pint.egg-info > > - docs/savefig > > > > 2/ There's a typo in d/changelog, you wrote: "d/copuright". > > > > 3/ I'm really not sure about the python-pint-doc.lintian-overrides > > overriding "font-in-non-font-package". Can't you use the fonts from > > system instead? > > > > Cheers, > > > > Thomas Goirand (zigo) > > 1/ and 2/ are now fixed > > For 3/ I indeed did a quick search but I was not able to find a font > package providing the needed fonts > > $ apt-file search fa-brands-400.ttf > gnunet: > /usr/share/doc/gnunet/html/_static/vendor/fontawesome/6.1.2/webfonts/fa-brands-400.ttf.gz > icinga-php-library: > /usr/share/icinga-php/ipl/asset/static/font/awesome/fa-brands-400.ttf > node-fortawesome-fontawesome-free: > /usr/share/nodejs/@fortawesome/fontawesome-free/webfonts/fa-brands-400.ttf > ntopng-data: > /usr/share/ntopng/httpdocs/fontawesome-free-5.11.2-web/webfonts/fa-brands-400.ttf > omnidb-common: > /usr/lib/python3/dist-packages/OmniDB_app/static/OmniDB_app/lib/fa/webfonts/fa-brands-400.ttf > petsc3.18-doc: > /usr/share/doc/petsc3.18-doc/docs/_static/vendor/fontawesome/6.1.2/webfonts/fa-brands-400.ttf.gz > petsc3.19-doc: > /usr/share/doc/petsc3.19-doc/docs/_static/vendor/fontawesome/6.1.2/webfonts/fa-brands-400.ttf.gz > python-astroplan-doc: > /usr/share/doc/python-astroplan-doc/html/_static/vendor/fontawesome/5.13.0/webfonts/fa-brands-400.ttf.gz > python-astropy-doc: > /usr/share/doc/python-astropy-doc/html/_static/vendor/fontawesome/5.13.0/webfonts/fa-brands-400.ttf.gz > python-blosc-doc: > /usr/share/doc/python-blosc-doc/html/_static/vendor/fontawesome/5.13.0/webfonts/fa-brands-400.ttf.gz > python-cogent-doc: > /usr/share/doc/python-cogent-doc/html/_static/vendor/fontawesome/5.13.0/webfonts/fa-brands-400.ttf.gz > python-dask-doc: > /usr/share/doc/python-dask-doc/html/_static/vendor/fontawesome/5.13.0/webfonts/fa-brands-400.ttf.gz > python-distributed-doc: > /usr/share/doc/python-distributed-doc/html/_static/vendor/fontawesome/5.13.0/webfonts/fa-brands-400.ttf.gz > python-django-doc: > /usr/share/doc/python-django-doc/html/_static/fontawesome/webfonts/fa-brands-400.ttf.gz > python-h5netcdf-doc: > /usr/share/doc/python-h5netcdf-doc/html/_static/vendor/fontawesome/5.13.0/webfonts/fa-brands-400.ttf.gz > python-imageio-doc: > /usr/share/doc/python-imageio-doc/html/_static/vendor/fontawesome/5.13.0/webfonts/fa-brands-400.ttf.gz > python-md-toc-doc: > /usr/share/doc/python-md-toc-doc/html/_static/vendor/fontawesome/5.13.0/webfonts/fa-brands-400.ttf.gz > python-mpl-sphinx-theme-doc: > /usr/share/doc/python-mpl-sphinx-theme-doc/html/_static/vendor/fontawesome/5.13.0/webfonts/fa-brands-400.ttf.gz > python-nbformat-doc: > /usr/share/doc/python-nbformat-doc/html/_static/vendor/fontawesome/5.13.0/webfonts/fa-brands-400.ttf.gz > python-pandas-doc: > /usr/share/doc/python-pandas-doc/html/_static/vendor/fontawesome/5.13.0/webfonts/fa-brands-400.ttf.gz > python-pyqtgraph-doc: > /usr/share/doc/python-pyqtgraph-doc/html/_static/vendor/fontawesome/5.13.0/webfonts/fa-brands-400.ttf.gz > python-pystac-doc: >
Re: Updated package list with packages open for adoption (Was: morph's abandoned packages (list))
Hi, I'd like to add paramiko to the list of semi-orphaned packages that needs more maintainers. high popcon, major upgrade, lots of rdeps: this would be a small transition by itself, like pytest 8 ... Le jeu. 28 mars 2024 à 10:24, Andreas Tille a écrit : > > ? #1065199 RM: pprintpp -- ROM; leaf package > Do we need this package? It looks dead upstream & was a trivial utility, let's drop it. > ? #1065246 O: contourpy -- Python library for calculating contours of 2D > quadrilateral grids > rdepends: python3-matplotlib > Taken by alexandre.deti...@gmail.com, deba...@debian.org https://salsa.debian.org/python-team/packages/contourpy/-/jobs/5508432 E ImportError: Python version mismatch: module was compiled for Python 3.11, but the interpreter version is incompatible: 3.12.2 dh-python or newer dh-sequence-python3 is missing from d/control (?) could it be the cause of the FTBFS ? I'l try again soon. > #1065325 O: matplotlib -- Python based plotting system >--> alexandre.deti...@gmail.com > + deba...@debian.org Not finished, was still debhelper 7 or 8 based from memory, had to kill xvfb-run several times to let the build complete successfully (?!) the resulting .deb does work. > General remark: I'd prefer if we would at least have [*] two maintainers per maintainer. > If you find my name in any Uploaders field and you are > interested in this package (no matter whether it is in this list or not) > please simply add your name and move on with doing on that package what > you feel necessary to do. If something might break we can fix it later. Please do the same. I'm bit of scatterbrain and can at some times only allocate small time slots to do small things so anything that hasn't been touched on the very same day is up for grab. ... but I do have some tooling to track my unfinished stuff. I'm moving python-socketio-client to DPT I can move "dosage" too if someone is interested (my only remaining non-team maintained package is "cruft-ng"; but that's not python ... anybody is welcome there too) Greetings
matplotlib
If you have the time/will, I would suggest to overhaul build to from 7 to new debhelper 13 with the automagic "%: dh $@" rule. Almost all other Python projects have already been converted. wc -l */debian/rules 29 lincity-ng/debian/rules 25 lmfit-py/debian/rules 21 logbook/debian/rules 28 logilab-constraint/debian/rules 35 love/debian/rules 21 ltris/debian/rules 15 lua-lpeg/debian/rules 13 magic-wormhole/debian/rules 206 matplotlib/debian/rules 14 mdp/debian/rules 18 microsoft-authentication-library-for-python/debian/rules 56 minetest/debian/rules 13 mir-eval/debian/rules 12 mrrescue/debian/rules 18 mu-cade/debian/rules
Re: python-debian | remove some Python2 dead code (!131)
Hi, Does anyone know some automated tool to convert Python2-style annotations into Python3-style ? python-debian $ grep '# type' -r | wc -l 1499 Greetings Le dim. 17 mars 2024 à 13:46, Jelmer Vernooij (@jelmer) a écrit : > > Jelmer Vernooij commented on a discussion: > > Yes, we should be able to migrate to modern type annotations - happy to > review PRs that make that change :) https://salsa.debian.org/python-debian-team/python-debian/-/merge_requests/131
Re: morph's abandoned packages (list)
Hi, The arguments to remove flask-basicauth looks sensible, can someone confirm ? CCing Daniele who uploads bespoken flask-login and Carsten who manage whole flaks ecosystem. Greetings Le jeu. 14 mars 2024 à 07:20, Julian Gilbey a écrit : > > Dear all (and Bcc-ing the RM bugs), > > For information, here is a list of packages that morph has either > requested removal of or orphaned. If you are interested in taking one > or more of them on, that would be great! > > Removal requested: > > #1066146 RM: flask-basicauth -- ROM; RC buggy, dead upstream, leaf package
Re: morph's abandoned packages (list)
Just add yourself. Le ven. 15 mars 2024 à 15:38, Martin a écrit : > > On 2024-03-15 14:21, Alexandre Detiste wrote: > > I would pick-up matplotlib I guess, I have some special connection to it, > > I *might* help on this, because we use matplotlib at $DAYJOB, but can't > promise much, as my workload is already pretty high.
Re: morph's abandoned packages (list)
Hi, I would pick-up matplotlib I guess, I have some special connection to it, It was one the packages that enabled me to escape my horrible SAS-Insitute powered previous job/life. It's a big one. Help is appreciated, I already cherry picked some commits from Ciel's PR. I already adopted python3-pygraphviz Greetings
Re: Would you agree with swapping Maintainer and Uploaders in eric?
Hi Jan, I see on the tracker that you have both set the LowNMU flag (like I did too) and also made use of the special rule of the DPT policy discussed from [1]; that seems a bit of a contradiction to me but I have read that it was the default behaviour of some source package templating tool which might explain where it came from. Would you agree to swap Maintainer & Uploader fields like proposed ? My offer to refresh the package still stands on. I would need this anyway for my work anyway in the coming months, that seems like a waste of time not to share this work. (we are currently using the bookworm .deb on buster and it justs works...) Greetings [0] https://tracker.debian.org/pkg/python-pika Le lun. 11 mars 2024 à 22:30, Andreas Tille a écrit : > > Hi Gudjon, > > in case you agree with the suggested change of policy discussed on the > debian-python mailing list[1] would you agree to set DPT as maintainer? > If yes, I'd volunteer to do this, fix bug #1065855 and #1060736. > > Kind regards and thanks for working on this package > Andreas. > > [1] https://lists.debian.org/debian-python/2024/02/msg00052.html
Re: Suggesting change in DPT policy
+1 for this policy change too, I went through the same hurdles & thinking progress, but it's much fresher in py head because I m only contributing to DPT since 1/1/2024, doing exactly what I said I would do on my membership application mail. Before this talk happened I would not have recommended anybody to join the team. I m glad it is being resolved. Greetings Le dim. 3 mars 2024, 00:30, Emmanuel Arias a écrit : > +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
RM: nb2plots -- ROM; leaf package
control: tag -1 +moreinfo Hi, I'm using this (nice, alive...) package and I'm willing to maintain it in the Python Team. Greetings, Alexandre
Re: Fix for pysmbc -Python 3.12 transition
Hi, Thanks again I may have an identical pytest -> python3-pytest commit stuck in my home computer, but whatever. Please someone pick this up Greetings Le lun. 22 janv. 2024 à 09:31, Yogeswaran Umasankar a écrit : > > Hi Alexandre, > Came across pysmbc, saw that there was an issue while building. Worked > on the issue in a different branch “py312 transition’ [0]. If it looks > ok, please feel free to merge the branch. I hope the revisions help > Python 3.12 transition. > > [0] > https://salsa.debian.org/python-team/packages/pysmbc/-/tree/py312-transition?ref_type=heads > > Best regards, > Yogeswaran.
Re: QA python3-unittest2
Le mer. 17 janv. 2024 à 17:14, Thomas Goirand a écrit :
> On 1/17/24 14:25, Alexandre Detiste wrote:
> > Le jeu. 11 janv. 2024 à 10:47, Thomas Goirand a écrit :
> >>> I'm busy with the (tentative-) removal of python3-unittest2.
> >>>
> >> https://docs.openstack.org/contributors/en_GB/common/accounts.html
> > I can send Salsa MR if that's easier for everyone too.
>
> If you just send me the list of packages affected, with no change to be
> sent upstream, I can take care of it in a few minutes myself.
Yes please
>Or have you already filled the bugs?
I've filled a handful of bugs then it felt wrong so I dropped the ball
10 cases with the 1 extraneous line in d/control
keystone/debian/control: python3-unittest2,
neutron/debian/control: python3-unittest2,
python-django-compressor/debian/control: python3-unittest2,
python-kafka/debian/control: python3-unittest2,
python-novaclient/debian/control: python3-unittest2,
python-oauth2client/debian/control: python3-unittest2,
python-pecan/debian/control: python3-unittest2,
sahara-dashboard/debian/control: python3-unittest2,
senlin-dashboard/debian/control: python3-unittest2,
trove-dashboard/debian/control: python3-unittest2,
3 cases with 1 extraneous line in test-requirements.txt &
1 extraneous line in d/control
... removing the Debian line may trigger a regression
when someone package the next update.
These would be my first 3 Gerrit-requests
murano-agent/test-requirements.txt:unittest2>=1.1.0 # BSD
murano-agent/debian/control: python3-unittest2,
designate-dashboard/test-requirements.txt:unittest2>=1.1.0 # BSD
designate-dashboard/debian/control: python3-unittest2,
mistral/test-requirements.txt:unittest2>=1.1.0 # BSD
mistral/debian/control: python3-unittest2,
and then more, but that is scripted.. and will be for a next iteration
#!/bin/bash
lists=/var/lib/apt/lists/ftp.be.debian.org_debian_dists
mkdir -p /tmp/unittest2
grep-dctrl python3-unittest2 -n -s Vcs-Git
${lists}_*{Sources,Packages} | grep openstack | sort -u | while read
url
do
dir=$(basename $url)
git clone --depth=1 $url /tmp/unittest2/$dir
done
(cd /tmp/unittest2; grep -r unittest2 .)
Re: QA python3-unittest2
Le jeu. 11 janv. 2024 à 10:47, Thomas Goirand a écrit : > > I'm busy with the (tentative-) removal of python3-unittest2. > > > > unitest2 is an old version of what has become "unittest" in the > > standard library > > > > 90% of dependencies are stale and only need a quick edit of debian/control > > for the other I submit patches upstream > > Will you also send patches to upstream OpenStack? If so, please note > that OpenStack uses Gerrit, and you need to follow the instructions > detailed here for a new account: > https://docs.openstack.org/contributors/en_GB/common/accounts.html I will learn Gerrit because I'm curious... ...but 90% of these remaining dep on unittest2 are really only about removing 1 line from debian/control ... only committing this change + setting the bug as pending would already help with triaging I can send Salsa MR if that's easier for everyone too. > I'd strongly recommend sending patches upstream rather than in > downstream Debian packages only. The next OpenStack release (codename: > Caracal) is due for April, so if you send patches upstream now, it's > going to be in Debian soonish. Great > Note that upstream OpenStack has been actively removing the Six > dependency, and they'll be very happy to have some kind of help > finishing the work. I'll do. have a nice day
Bug#1060421: python3-botocore: botocore as a (useless) undeclared dependency on python3-six
Package: python3-botocore Version: 1.31.49+repack-1 Severity: important X-Debbugs-Cc: debian-python@lists.debian.org python3-core is importing python3-six for absolutely no reason this package only work by luck for now because the library got pulled-in by something else (most likely python3-urllib2) $ grep ' six' /usr/lib/python3/dist-packages/botocore -r | grep import /usr/lib/python3/dist-packages/botocore/compat.py:import six Greetings, A possibility to catch this earlier would be to add a deprecation warning inside python3-six ? -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (501, 'testing'), (450, 'unstable'), (400, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.5.0-5-amd64 (SMP w/2 CPU threads; PREEMPT) Kernel taint flags: TAINT_USER Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE:fr Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages python3-botocore depends on: ii python3 3.11.4-5+b1 ii python3-dateutil 2.8.2-3 ii python3-jmespath 1.0.1-1 ii python3-requests 2.31.0+dfsg-1 ii python3-urllib3 2.0.7-1 python3-botocore recommends no packages. python3-botocore suggests no packages. -- no debconf information
QA python3-unittest2
Hi, I'm busy with the (tentative-) removal of python3-unittest2. unitest2 is an old version of what has become "unittest.mock" in the standard library 90% of dependencies are stale and only need a quick edit of debian/control for the other I submit patches upstream Can I get (minimal) Salsa team membership for this one task ? maybe also checking for python3-mock & python3-six at the same time. I do not plan to do any upload of these packages and more generally I do not even fully grasp what OpenStack is about. I can maybe handle just this urgent one #1059108 [i|P|♔] [src:gnocchi] gnocchi: please remove extraneous dependency on python3-future python3-unittest2: """ designate-dashboard keystone mistral murano-agent neutron python-django-compressor python-funcsigs python-jenkins python-kafka python-linecache2 python-novaclient python-oauth2client python-pecan python-pymysql sahara-dashboard senlin-dashboard testresources trove-dashboard python3-six: #1053966 [n| | ] [python3-ironic-ui] python3-ironic-ui: please remove extraneous, obsolete, dependency on python3-six #1054151 [n| | ] [python3-neutron-vpnaas] python3-neutron-vpnaas: please remove obsolete python3-six dependency #1060114 [n| |↝] [src:python-txaio] python-txaio: please remove extraneous dependency on python3-six (so not these ones, unless requested) #1052512 [n| | ] [src:python-pysaml2] python-pysaml2: please package v7.4.2 and remove python3-six dependency #1053378 [n| | ] [src:python-gabbi] python-gabbi: please package v2.10.0 and remove dependency on python3-six Greetings
Re: [Help] Re: python-future: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13
Le jeu. 4 janv. 2024 à 07:48, Andreas Tille a écrit : > > @Vincent: this one package "gtextfsm" is yours > > do you green light an upload ? > > If you ask me the package is team maintained and a "Team upload" > should be fine. Hi, I just try to follow the rules I agreed on last month. https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst#id2 | Team in Uploaders is a weak statement of collaboration. Help in maintaining the package is appreciated, | commits to the Git repository are freely welcomed, but before uploading, please contact the Maintainer for the green light. There are not so many packages where "Uploader = DPT" to begin with, so this might not well a well-known practice... So I'm formally asking Ana & PaN for approval to upload "lexicon" and "dioptas". (lexicon is a one line change, dioptas needs to package a new release) @Vincent: thanks. Greetings - Debian Python Team dioptas (U) gtextfsm (U) lexicon (U) Ana Custura lexicon Debian PaN Maintainers dioptas
Re: [Help] Re: python-future: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13
Le lun. 11 déc. 2023 à 16:43, Andreas Tille a écrit :
> Control: tags -1 help
>
> [Bug #1056419 in CC since the issue seems to be caused by python-future]
>
> Hi Vincent,
>
> I tried to upgrade python-future to the latest upstream version in the
> hope that this would solve the issue reported in bug #1042244.
> Unfortunately this is not the case and now with Python3.12 we also
> have to deal with the removal of imp (which affects bug #1056419).
>
> I'd like to ask for help on debian-python list since I'm pretty
> overworked with other stuff. Please also review my rude patch[1] to
> hack around a shinx issue. It would be great to have some better
> solution here.
The better solution is to remove python3-future altogether.
I've set up a tracker with remaining packages:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059934
(list is not complete)
There might be some nmu needed too if maintainers don't react.
@Vincent: this one package "gtextfsm" is yours
do you green light an upload ?
Greetings,
https://salsa.debian.org/python-team/packages/gtextfsm/-/pipelines/621238
gtextfsm $ cat debian/patches/no-future.patch
From: Alexandre Detiste
--- a/setup.py
+++ b/setup.py
@@ -53,5 +53,5 @@
},
include_package_data=True,
package_data={'textfsm': ['../testdata/*']},
- install_requires=['six', 'future'],
+ install_requires=['six'],
)
Re: Why is ${python3:Depends} injecting cython3-legacy (Was: obitools: runtime dependency on cython)
The worse thing is when upstreams ask you to sign a CLA to accept a PR that removes one extraneous line from requirements.txt. Is it even copyrightable ? Le dim. 17 déc. 2023 à 20:21, Graham Inggs a écrit : > > Hi Andreas > > On Sun, 17 Dec 2023 at 18:15, Andreas Tille wrote: > > Is there > > any better way than editing debian/obitools.substvars in d/rules by > > adding some override_dh_gencontrol? > > Remove the line: > > Cython>=0.24 > > from requirements.txt.
Re: Bug#1056419: [Help] Re: python-future: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13
Le lun. 11 déc. 2023 à 17:02, Jochen Sprickerhof a écrit : > I think the right thing here is to package the new uncertainties version > which drops the past import: > > https://github.com/lebigot/uncertainties/releases/tag/3.1.7 +1 > Also we should probably get rid of python-future at some point. I removed it from three games this week-end and filled 6 more bugs since to remove extraneous stale dependency. There are in fact more fake stale dependencies than remaining true ones It takes like 10 minutes to review one package. It's a peaceful life. https://salsa.debian.org/games-team/ardentryst/-/commit/fc6901b0e90b6bb3ec19b23c1c2d458d653b2d4a I will continue this review. The existing bugs can be tagged someway if that helps. Greetings python3-gnocchi 0 python3-mir-eval 1 dioptas 2 python3-bioxtasraw 2 openqa-client3 rocketcea3 graide 5 python3-emperor 5 python3-grapefruit 6 python3-stomper 6 python3-junitparser 7 python3-pyhamtools 8 python3-pyxnat 11 onionbalance 16 python3-graphite216 python3-picopore 16 turing 16 autoradio17 #1054207 python3-biomaj3 24 python3-flask-autoindex 25 python3-scikit-rf26 radon29 osdlyrics30 python3-pyswarms 30 python3-pyocd34 bugwarrior 40 python3-gnocchiclient47 buildbot-worker 63 python3-bibtexparser 71 weechat-matrix 71 gnome-keysign82---> upstream python3-proselint83 python3-cpuset 90 python3-mdp 143 old_div python3-yade 192 c++ python3-plaso212 RM python3-uncertainties262 package new version chirp321 non duplicity10757
Bug#1058057: impacket: please remove erroneous extraneous reference to 'future' from setup.py
Source: impacket Severity: important X-Debbugs-Cc: debian-python@lists.debian.org Dear Maitainer, Upstream mistakenly added 'future' to the requirements in setup.py Maybe they tought it was needed to get the "from __future__ import ..." statements working. That would had been "from future import ..." / "from past import ...". Nowadays it means that your package is pulling in python3-future. This library is obsolete and mostly unmaintained and should be removed from Debian. So please patch it out from the build. Greetings, Alexandre -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (501, 'testing'), (450, 'unstable'), (400, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.5.0-5-amd64 (SMP w/2 CPU threads; PREEMPT) Kernel taint flags: TAINT_USER Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE:fr Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system)
Bug#1058056: multiqc: please remove extraneous dependency on python3-future
Source: multiqc Severity: normal X-Debbugs-Cc: debian-python@lists.debian.org Dear Maintainers, Your package's setup.py declares an extraneous dependency on old compatibility layer python3-future. > setup.py:"future>0.14.0", But it doesn't need it at all: no import of "past" or "future" libraries. Please report it upstream and in the meantime build a package with this line patched-out. Greetings, Alexandre -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (501, 'testing'), (450, 'unstable'), (400, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.5.0-5-amd64 (SMP w/2 CPU threads; PREEMPT) Kernel taint flags: TAINT_USER Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE:fr Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system)
Bug#1058055: galpy: please remove extraneous dependency on python3-future
Source: galpy Version: 1.8.1-2 Severity: important X-Debbugs-Cc: debian-python@lists.debian.org Dear Maintainer, The removal of the python3-future library is being evaluated. It's obsolete & unmaitained upstream. Your package seems not to have required python3-future for a long time. Please remove the hardcoded dependency from debian/control. Greetings, /tmp/galpy $ grep future -r setup.py:# Note for the futureL could now get the actual compiler in the BuildExt class debian/control: python3-future, debian/control: python3-future, debian/changelog: * Add python3-future as build and package dependency /tmp/galpy $ grep past -r HISTORY.txt: examples to the user's clipboard for easy pasting into a Python /tmp/galpy $ -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (501, 'testing'), (450, 'unstable'), (400, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.5.0-5-amd64 (SMP w/2 CPU threads; PREEMPT) Kernel taint flags: TAINT_USER Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE:fr Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system)
Re: Request to join the team
Hi, I would like to join the Debian Python team too, my Salsa login is detiste-guest. https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst ACK I'm interested: - fixing the bug I submitted - checking if old python2 compatibility layers are actually still used: - unittest2 - future - six - dose1 - ( I also check upstreams & send PR if upstream is still active) - add typing annotations to native packages (alike python3-debian, python3-debconf, apt-listchanges ...) - helping with Py3.12 support & random RC bugs Greetings
Re: Bug#1057830: qgis: please remove extranous dependency on python3-future
Hi, Le sam. 9 déc. 2023 à 07:53, Sebastiaan Couwenberg a écrit : > > qgis has some dependencies for the sake of plugins which cannot pull in > dependencies on their own. > > Are there plans to remove python3-future from Debian or it being > deprecated upstream? There's no plan yet. The default plan would be to remove python3-future when nothing needs it anymore. That's what is happening right now with all these old GTK2 & SDL1 frameworks I've removed trivial usage of python3-future from 3 games yesterday, I will continue. I guess all packages are not that easy to patch and there will be some blocker with a dead upstream. A quite smarter plan would be to patch python3-future so it's start emitting a Debian-specific DeprecationWarning that will come up: - in CI of other packages using it (?) (after "duplicity" is updated not to annoy too many people at once) - in QGIS users scripts (Ubuntu 24.04 would be a nice "test bed") Greetings DONE: ardentryst_1.71-10_source.changes ACCEPTED into unstable -from past.builtins import cmp +def cmp(x, y): return (x > y) - (x < y) bouncy_0.6.20071104-9_source.changes ACCEPTED into unstable -from past.builtins import long +long = int unknown-horizons_2019.1-7_source.changes ACCEPTED into unstable d/control: - python3-fututre, was already clean TODO, with popcon: qgis of course duplicity10757 -> new upstream version pending python3-impacket 573 ycmd 448 vim-youcompleteme442 chirp321 python3-uncertainties262 python3-plaso212 python3-yade 192 python3-mdp 143 python3-django-q 138 python3-galpy125 multiqc 113 python3-nipype 106 python3-cpuset 90 python3-proselint83 gnome-keysign82 weechat-matrix 71 python3-bibtexparser 71 renpy66 buildbot-worker 63 python3-gnocchiclient47 bugwarrior 40 python3-pyocd34 python3-pyswarms 30 osdlyrics30 radon29 python3-scikit-rf26 python3-flask-autoindex 25 python3-biomaj3 24 insilicoseq 21 autoradio17 turing 16 python3-picopore 16 python3-graphite216 onionbalance 16 python3-pyxnat 11 python3-pyhamtools 8 python3-junitparser 7 python3-stomper 6 python3-grapefruit 6 python3-emperor 5 graide 5 rocketcea3 openqa-client3 python3-bioxtasraw 2 dioptas 2 python3-mir-eval 1 python3-gnocchi 0
