Re: Use debhelper-compat instead of debian/compat
Hello Ondřej, On 18/07/2019 21:15, Ondrej Novy wrote: > > I would like to mass-commit this change to DPMT/PAPT, example: > > https://salsa.debian.org/python-team/modules/python-geoip2/commit/bc5ce34dd9bbfe3ecb7951aead267dbdaba3376a > > Any thoughts? Thanks, please go ahead! Regards, -- Daniele Tricoli 'eriol' https://mornie.org
Use debhelper-compat instead of debian/compat
Hi, according to debhelper man package it's recommended to use debhelper-compat instead of debian/compat file. I would like to mass-commit this change to DPMT/PAPT, example: https://salsa.debian.org/python-team/modules/python-geoip2/commit/bc5ce34dd9bbfe3ecb7951aead267dbdaba3376a Any thoughts? -- Best regards Ondřej Nový
Re: Python package maintainer request for joining Salsa team
Hi, st 17. 7. 2019 v 17:34 odesílatel Geert Stappers napsal: > Think "improve bus factor" > that is always good idea :) > The process that should be told is weather it is OK (or not) that > any DD member is allowed to (or may) add new members to the Salsa team. > only Salsa python-team "owners" should/could add members. List is: Ondřej Nový @onovy Piotr Ożarowski @piotr Scott Kitterman @kitterman Stefano Rivera @stefanor Bernd Zeimetz @bzed Which privileges the new member gets initially. > all members have same privileges. Push to Git repos and do team uploads (explained in policy). > What checks are needed. > tha's up to admins :) > If the salsa web interface is right tool, > or that script "foo" is the preferred. > it's manual work now. Where to communicate that it is (being) processed. > it's not. Because when is processed, it's finished in same day. -- Best regards Ondřej Nový
Re: python-socketio x gevent-socketio
On Thu, 2019-07-18 at 10:47 +0200, Benjamin Drung wrote: > Hi, > > I orphaned gevent-websocket and William Grzybowski took over this > package. Therefore taking him into the loop. Not clear how websocket package is related but I will try to help! > > Am Montag, den 03.12.2018, 22:20 -0200 schrieb Paulo Henrique > Santana: > > So. what is a good a solution to this? > > Keep my python-socketio on Python3 tree and gevent-socketio on > > Python2.7? > > Use Conflicts field to force the user to remove gevent-socketio > > before install python-socketio? > > Or other solution? > > > > [1] https://tracker.debian.org/pkg/flask-socketio > > [2] https://github.com/miguelgrinberg/Flask-SocketIO > > [3] https://tracker.debian.org/pkg/gevent-socketio > > [4] https://pypi.org/project/gevent-socketio/#files > > [5] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879631 > > [6] http://github.com/miguelgrinberg/python-socketio > > IMO the best solution is to work together with upstream to resolve > the > Python namespace conflict. Then both packages use different paths in > /usr/lib/python3/dist-packages and can be installed and used in > parallel. IMO gevent-socketio is pretty much a dead or extremely low maintenance upstream, we could try talking to them but its likely we wont reach out to a consensus, renaming python modules is terrible from both point of views. That said, python-socketio has no reverse dependencies so it would be somewhat easy to rename python-socketio to python-gevent-socketio, create the new package as python3-socketio to not have any confusion with the naming and set up conflicts for them. Who knows? Maybe gevent-socketio will get active again and add py3 support, which then we would need python3-gevent-socketio. If it doesn't it will get removed as python 2.x support will eventually get dropped. Cheers, signature.asc Description: This is a digitally signed message part
Proposed removal of python net-snmp modules
Hi, For the next net-snmp release, I am proposing removing the python modules that link to libsnmp. There are many reasons for doing so including: * net-snmp is python 2 only bindings * net-snmp python is synchronous calls only, not asynchronous * net-snmp is horribly clunky in the way it works * The pysnmp module, as found in python3-pysnmp4 is vastly better pretty much any way you look at it. There are no reverse dependencies on the python-netsnmp package. While it's hard to tell, I don't think it is used terribly much and if it is, that use would be better served with pysnmp. If someone knows about a Debian package needing this module, let me know and I'll endeavour to work with the maintainer to port it across to pysnmp. - Craig -- Craig Small (@smallsees) https://dropbear.xyz/ csmall at : dropbear.xyz Debian GNU/Linux http://www.debian.org/ csmall at : debian.org GPG fingerprint:5D2F B320 B825 D939 04D2 0519 3938 F96B DF50 FEA5
Documentation path and Python 2->3
(Sorry if this has been discussed before: it's not obvious how to search for it) Policy 12.3 [0] states that documentation for $package should preferably be packaged as $package-doc but still install to /usr/share/doc/$package not /usr/share/doc/$package-doc. By default, debhelper implements this as "if $package (or $package-dev) exists in the same source, install $package-doc to /usr/share/doc/$package(-dev), otherwise install it to /usr/share/doc/$package-doc" [1]. For Python packages, this means that python-$module-doc moves from /usr/share/doc/python-$module to /usr/share/doc/python-$module-doc when the Python 2 $module ceases to exist [2]. This may break links (doc-base [3], users' local bookmarks, etc). Should it instead move to /usr/share/doc/python3-$module? (And if so, should the -doc package be renamed to python3-$module-doc? though that implies a large[4] amount of binary-NEW processing...) Or stay in /usr/share/doc/python-$module to not break links? Should there be symlinks to the documentation in whichever of /usr/share/doc/python3-$module, /usr/share/doc/python-$module-doc and (if it exists) /usr/share/doc/python-$module don't contain the actual documentation? This was suggested for the general /usr/share/doc/$package-doc to /usr/share/doc/$package case in the original Policy discussion [5], but didn't make into actual Policy. [0] https://www.debian.org/doc/debian-policy/ch-docs.html#additional-documentation [1] https://sources.debian.org/src/debhelper/12.2.2/lib/Debian/Debhelper/Dh_Lib.pm/#L2664 [2] e.g. https://packages.debian.org/buster/all/python-django-doc/filelist -> https://packages.debian.org/sid/all/python-django-doc/filelist [3] https://bugs.debian.org/931652 [4] there are currently 661 python-$module-doc (and 19 python3-$module-doc, which appear to be new packages rather than renames) [5] https://bugs.debian.org/106073
