ITP: pdm-pep517 -- Yet another PEP 517 backend for PDM projects
Package: wnpp Severity: wishlist Owner: Boyuan Yang X-Debbugs-Cc: debian-de...@lists.debian.org * Package name: pdm-pep517 Version : 1.0.0 Upstream Author : Frost Ming * URL : https://github.com/pdm-project/pdm-pep517 * License : Expat Programming Lang: Python Description : Yet another PEP 517 backend for PDM projects This is the backend for PDM projects, while you can also use it alone. It reads the metadata of PEP 621 format and coverts it to Core metadata. This package is the build-dependency for several packages in Debian. I intend to maintain this package as part of the Debian Python Team. Packaging work will be stored at https://salsa.debian.org/python-team/packages/pdm-pep517 . Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part
Re: pdm-pep517: Shall we package it now?
Hi, 在 2022-06-28星期二的 13:32 +，Stefano Rivera写道： > Hi Boyuan (2022.06.28_13:24:49_+) > > I am wondering if it's time to package pdm-pep517 itself [2], or is there > > any blocking for it. I am aware that some sort of bootstrapping might be > > needed since pdm-pep517 seems to build-depends on itself. > > Yes, probably time to package it. > > Bootstrapping shouldn't be problematic, PEP517 includes support for > bootstrapping (backend-path = ["."]), so backends can build themselves > from their own source trees. Thanks. I have uploaded an initial version to the NEW queue. The packaging work is at https://salsa.debian.org/python-team/packages/pdm-pep517/ . It is worth noting that I took the very aggressive way in stripping every vendored libraries, see https://salsa.debian.org/python-team/packages/pdm-pep517/-/tree/master/debian/patches . This may not be ideal since the patch will need human intervention for every new upstream release, but anyway let's have a working version in Sid first. Meanwhile, any review or other types of help would be appreciated. Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part
Reintroduction of gtg and liblarch
Hello Python Team, I would like to reintroduce the gtg (Getting Things Gnome) package [1] and its dependency liblarch [2]. I have contacted Antonio Ospite, claiming that he's working on the package in the associated bug [3], but got no response. In the meantime I pushed an updated working package of liblarch at salsa [4], and I would like to know if the python team is OK to update the official repos [5] and go forward with the reintroduction of gtg and liblarch. Thanks! François [1] https://tracker.debian.org/pkg/gtg [2] https://tracker.debian.org/pkg/liblarch [3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970426 [4] https://salsa.debian.org/mzf/liblarch [5] https://salsa.debian.org/python-team/packages/liblarch signature.asc Description: This is a digitally signed message part
Re: Bug#1013425: ITP: wnpp -- Python Airspeed is a powerful templating engine compatible with Velocity for Java
Dear maintainers, the initial packaging for python3-airspeed is now ready at [1] and has a green salsa CI. It should be ready for a review. @Stephan: Would you like to sponsor this package as well? [1] https://salsa.debian.org/python-team/packages/airspeed Best regards, Felix Moessbauer Siemens AG
Re: pdm-pep517: Shall we package it now?
On Wed, Jun 29, 2022 at 10:58:48AM -0400, Boyuan Yang wrote: > Hi, > [...] > Thanks. I have uploaded an initial version to the NEW queue. The packaging > work is at https://salsa.debian.org/python-team/packages/pdm-pep517/ . > > It is worth noting that I took the very aggressive way in stripping every > vendored libraries, see > https://salsa.debian.org/python-team/packages/pdm-pep517/-/tree/master/debian/patches > . This may not be ideal since the patch will need human intervention for every > new upstream release, but anyway let's have a working version in Sid first. > Meanwhile, any review or other types of help would be appreciated. Hi Boyuan, I've just taken a look; the exclusions and patching look fine to me. Yes, there will need to be some human intervention, but there always should be for new upstream versions. It may well be that all that is needed is to refresh the patch and run: quilt push -a rgrep _vendor pdm (or the equivalent gbp pq push or something like that) to check that nothing has changed. One small change to the patch: * In pdm/pep517/utils.py and pdm/pep517/wheel.py, there is no need to insert an "import packaging" Best wishes, Julian
