Re: O: python-cryptography -- Python library exposing cryptographic recipes and primitives (documentation)
Le jeu. 29 févr. 2024 à 12:06, Andreas Tille a écrit : > Hi, > > as per bug #1064979 python-cryptography was orphaned. Actually the > process of orphaninig is defined differently[1] by setting QA team as > maintainer. In this case DPT remains maintainer but there is no > Uploader specified any more. I personally will not add my ID as > Uploader. I have added those team members who did uploads in the last > year in CC. > Good idea since I'm all right with helping to maintain it. I did the 41 upgrade so I'm already familiar with it. I'll AMAU unless someone is more motivated. Source package python-cryptography-vectors needs the same treatment. I tried to do some bug squashing anyway. Since the latest version was > requested in bug #1063771 and this new version also closes #1064778 > (CVE-2024-26130) (the other CVE-bug should have been closed in previous > upload) I decided to inject latest upstream, adapted the patches and > pushed to Git. Unfortunately the package does not build as you can > verify in Salsa CI[1]. I admit I have no clue how to fix this but I hope someone can take over > from here. I guess uploading to experimental first and see how it > plays nicely with its lots of rdepends makes sense here. Version 42 needs some rust deps to be updated as well, last time I checked, and I was in wait-and-see mode about those. Jérémy
Re: sphinx-build module not found in sbuild
Le lun. 8 janv. 2024 à 13:46, Julian Gilbey a écrit : > On Mon, Jan 08, 2024 at 01:22:54PM +0100, Jérémy Lal wrote: > > Hi, > > I'm stuck at this odd behavior: > > when I build a package in my current environment (debian/testing), > > sphinx-build ... works correctly. > > when building in sbuild, sphinx-build doesn't find current module: > > ModuleNotFoundError: No module named 'xxx' > > in docs/conf.py at > > from xxx import __version__ > > I don't understand which other debian package is modifying that outcome. > > Any idea ? > > Perhaps your local build is importing from a globally-installed > version of the package? (For example, you're building version 1.3 of > python3-foo, but you already have version 1.2 of python3-foo > installed.) > Damn, that new package I'm working on already exists ｡•́︿•̀｡
sphinx-build module not found in sbuild
Hi, I'm stuck at this odd behavior: when I build a package in my current environment (debian/testing), sphinx-build ... works correctly. when building in sbuild, sphinx-build doesn't find current module: ModuleNotFoundError: No module named 'xxx' in docs/conf.py at from xxx import __version__ I don't understand which other debian package is modifying that outcome. Any idea ?
Re: Request to join debian-python team on salsa
Le jeu. 11 août 2022 à 17:55, Stefano Rivera a écrit : > Hi Jérémy (2022.07.07_13:19:01_+) > > I'd like to continue to maintain "gyp", > > and possibly some other python packages in a near future. > > > > I am aware of python policy and documentation. > > Please state that you *agree* with the policy :) > Hi, Yes, of course, I agree with the python policy. Also mind that I don't plan to upload anything new without requesting review.
Re: Request to join debian-python team on salsa
salsa login is "kapouer" Le jeu. 7 juil. 2022 à 15:19, Jérémy Lal a écrit : > Hi, > > I'd like to continue to maintain "gyp", > and possibly some other python packages in a near future. > > I am aware of python policy and documentation. > > Thanks, > > Jérémy > >
Request to join debian-python team on salsa
Hi, I'd like to continue to maintain "gyp", and possibly some other python packages in a near future. I am aware of python policy and documentation. Thanks, Jérémy
Re: Bug#969081: gyp should not stay under pkg-js umbrella
Le jeu. 27 août 2020 à 11:48, Xavier Guimard a écrit : > Package: gyp > Version: 0.1+20200513gitcaa6002-1 > Severity: normal > > Hi, > > gyp is currently maintain under pkg-js umbrella. This package is a cross > platform tool written in Python and stored in salsa.d.o/debian/ area. > Then I don't understand the link with pkg-js team. > Good point ! Let's ask debian-python if gyp could be team-maintained there. Jérémy
Re: [Pkg-javascript-devel] npm2deb in debian
Le samedi 03 mai 2014 à 15:55 +0200, Leo Iannacone a écrit : Hello there, I'm looking for a sponsor for npm2deb: http://anonscm.debian.org/gitweb/?p=pkg-javascript/npm2deb.git some python developer around? Note that i'm all right with reviewing and uploading it, but it'd be very nice if a debian-python developer had a look at the python packaging part. Jérémy. (Please keep discussion into pkg-javascript-devel or cc to it) -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1399128935.5807.4.camel@imac.chaumes
Re: cdbs : doing two packages from one source
found the solution for my question: i added two files : python-mymodule.install containing usr/lib/python* and libjs-mymodule.install containing source/path/to/js us/share/javascript/mymodule/ -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: from python egg to debian package : a good example ?
On 20/08/2009 11:24, Piotr Ożarowski wrote: [Ben Finney, 2009-08-20] Piotr Ożarowskipi...@debian.org writes: [Jérémy Lal, 2009-08-18] i'm willing to package a python module (orbited, see http://orbited.org). I suppose there's a clever way when the said module is a python egg. There's tar.gz on PyPi, no need to use Egg. This is true for the ‘orbited’ distribution, but only because the distribution owner has uploaded a tarball. Can you point me to a project that is providing eggs only? anyway, here's what I'd do in such case: * check if upstream is using VCS (tarball can be created from files in the repo), or * ask upstream to point me to the sources, or * unzip .egg, add setup.py, create tarball, send setup.py upstream I was confused and made an omelet with the egg :) Indeed the tarball contains setup.py, and dh_pycentral did the job. Regards, Jérémy. -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: from python egg to debian package : a good example ?
On 20/08/2009 12:57, Ben Finney wrote: Jérémy Lalje...@edagames.com writes: Indeed the tarball contains setup.py, and dh_pycentral did the job. Note again, though, that new packaging work shouldn't rely on ‘python-central’; it has many problems that are tedious to recover from. Instead, use ‘python-support’. Thanks, i just discovered my questions were already answered at http://wiki.debian.org/DebianPythonFAQ -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
from python egg to debian package : a good example ?
Hi, i'm willing to package a python module (orbited, see http://orbited.org). I suppose there's a clever way when the said module is a python egg. However i don't find any coherent documentation on this, and how python-distutils, dh_pycentral, dh_pysupport provides coherent python module packaging. I'd appreciate any documentation, or better the name of a source package that shows clearly how to do. I tried reading python-fuse/debian/rules... not learned much from it :) Regards, Jérémy Lal -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
