Hi Boyuan (2022.06.28_13:24:49_+0000)

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.

SR

--
Stefano Rivera
http://tumbleweed.org.za/
+1 415 683 3272

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Hi all,

I have encountered more and more packages that uses pdm-pep517 as build backend. Looking at [1], existing packages in Debian added patches to
manually switch to other backends, such as Poetry.

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. Besides that, what about packaging of pdm? Please correct me if needed: my mind and my
packaging work is still stuck in the old times of setup.py, and I just
started to look into the new ecosystem of pep517. Thanks!

Regards,
Boyuan Yang


[1] https://codesearch.debian.net/search?q=pdm.pep517
[2] https://github.com/pdm-project/pdm-pep517

-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAmK7ASEACgkQwpPntGGC Ws7bAQ//Su1ipjvDb1fX7fDnvIzuyIOg2RzmGjb206N4GfQIv3gQuxhWzdRVjjGF ATcj0TDp6rPc8OuKxnUENexh3mun4D9S5RdL9mnuWARHsMWVf6jLniSN1WkHaK8t v6D3H7ddZL2aIixhQhJEibE9Chd4iKANMsV+758iQ03ERrYNPb5FxbbMspKiMFhf N9TL583VVyuaqbQOTWoLu55PONWDR9bqDQtwU7spoJbOsj0cZqaMsJGSFfOnHwjA U/maBaHnTXOZ6YoWkv+Ehv+zkiV0suLdKaXDawMsmKGvMusCuqN2HxRVxYqH8UIQ uFERNlT/2AXcjTUWIemk4rSB3Mx+hAKlm+b/48jKDdlQ/QaDLgb4AdMDymRdoZDt ZQIYdCXyeeKp+9PUzguLXbYM3ye2O/ZFCAaTIwneLD3DDcJuV1zeDVWsKucUK2s4 ZblyA07eaIbF4MMxTjC6M37kXwPrxf2BVcIf8DS5HrwHmXpW+MIF9XpVwI83lEQP NOfFBid6GO+q1j0ZmwowMqwaLF3y1UbuMVekbTbMYeWwFqC4UDnfEPEjCcCRIXR1 svw7rwfcUcfnmVKIH4pYqe+FCu0VLVyWzRboeo6PhEnFivzdUuG4F/01HLIhoir/ EJip8x2zqsCEbiFp6VsGY5DwcZwihOR3Ymzyh81DCU1kdISV+/U=
=OaCD
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 2022-06-28 09 h 24, Boyuan Yang wrote:

Hi all,

I have encountered more and more packages that uses pdm-pep517 as build backend. Looking at [1], existing packages in Debian added patches to manually switch to other backends, such as Poetry.

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. Besides that, what about packaging of pdm? Please correct me if needed: my mind and my
packaging work is still stuck in the old times of setup.py, and I just started to look into the new ecosystem of pep517. Thanks!

Regards,
Boyuan Yang

[1] https://codesearch.debian.net/search?q=pdm.pep517
[2] https://github.com/pdm-project/pdm-pep517

Once packaged, please ping me so I can update the "missing-prerequisite-for-pyproject-backend" Lintian tag accordingly and
let people know they can migrate to it.

--
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau
⢿⡄⠘⠷⠚⠋ pollo@debian.org / veronneau.org
⠈⠳⣄

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Hi,

在 2022-06-28星期二的 13:32 +0000，Stefano Rivera写道：

Hi Boyuan (2022.06.28_13:24:49_+0000)

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

-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAmK8aKgACgkQwpPntGGC Ws6Wag//QjIhVK1G9Pt03MOdiOXdUtnJxpIxa8praXrGcV9veh+qKODc5AGFEmD3 K3g37IwvOiT1lGx+K6qinIF7NmSYfadHzpstUD5goqCdlAKrfSEHEBzvY5XbppJN H8n/ZtolJRPJHkKekLO0owy08N6OUkZc0ZE+aOtq0ZFC0XvtnGMhkexNihZLljwZ 6+j9X5Tz1TMQcau4JTXP1uLw8VH3CU96+UA9Y4SiNQ/MYHREOaedM0PX0DZn2gdP p7RaaMawZ4v7U75lhdE02GLVt4UgZzHgQHUSJ+BBYxQ2+TLi6Igyxs8+RUw04/mx 8Cyls+GqvDsYop2Max3kpbjgZ66zGYn1o8Xm3C3r2meMxKKO67C11qZ9J5Zvs9qz gh7zJ443olDJUgT34Un6vK9O9ULbbuRwz6yrmRbRajoeViCrpc29lQgCEvfjXnxw SYdJ7aXQv/fPcGM06EEAiqkjcg0i+1k6j2o6KPr8nwOOVBZhqsUNTr+uJUC9hSBd C3dWTMbhmAA6eGTwdR0SMfggpMAUXH9+3CznDO2XisFs56s+FjWFlA1us3W1plQD VRppWUg3ckbfuHcZrlD8TZv0NoK9lKhVyiPNDzu6PWQhFpgUAtOqNtfpIdnPg47n 1+eoRZ9Lewy2sMFWDyWNgdVXGs8IFMfqNnyrZqN/4NO/YUvily0=
=7/l2
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

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

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Hi,

在 2022-06-28星期二的 11:19 -0400，Louis-Philippe Véronneau写道：

On 2022-06-28 09 h 24, Boyuan Yang wrote:

Hi all,

I have encountered more and more packages that uses pdm-pep517 as build backend. Looking at [1], existing packages in Debian added patches to manually switch to other backends, such as Poetry.

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. Besides that, what
about packaging of pdm? Please correct me if needed: my mind and my packaging work is still stuck in the old times of setup.py, and I just started to look into the new ecosystem of pep517. Thanks!

Regards,
Boyuan Yang

[1] https://codesearch.debian.net/search?q=pdm.pep517
[2] https://github.com/pdm-project/pdm-pep517

Once packaged, please ping me so I can update the "missing-prerequisite-for-pyproject-backend" Lintian tag accordingly and
let people know they can migrate to it.

This is now accepted at https://tracker.debian.org/pkg/pdm-pep517 .

Cheers,
Boyuan Yang

-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAmLHNb4ACgkQwpPntGGC Ws7DRQ/+InT6mfW++JeYFWb+DFBPXJktWwVxG7uxo5ogIWJBkmsGSM1Fh+G3Sw11 /OhI6GP+PahbGM7xMJP5zH+qZIRviq+saJUvV3kKvhmga9Tl63B9Da3SblEZdX91 fEULWuKZysVPYjZTS+qQZUYzKRVd+wC+kVDOebmYz8ojJsbTApvKXVVLrFd6WIMx /4t/xQAlJPLPQAp//kmeMXLwOQlYs685CIJUPBQVH14h/K9pfa6mIbbHHBXVnr/o KKfP3PxhS8FoFPRMPzvis6gyR3odNF8y4N8WwfIpuwxm3VAfUvhfmzQEC1VFQk9K WvY87y4IzV7DwQvQ4BC1K7ZtDMri7qMV7jcsxPB2PExxysM35OrBMdAU1wUE5tjK PBTRVEbQeWe+M8VcKn1AsD0cg6bNvHJmzYQbno9myRvQCXOeWah4gSgz9UzZGTzM P7QdD7sN7L4qVseofWO/RQzyZRthl3aIJh2gyXIRhR58I6nbj+lz2zrQw1Pp5ZDw AlEy9+UHMuJhltZ9q085vF6TTAWROAh/hcfLHCuEYzCSjRhhut0dBaV/4e50Wiz/ O7nmZp7Rb7j94MjBfb/e4nN8NVwMd3NQ8a6FFmDf54NO1a/wAagGWLKJ2gXe9dpQ wj1GBvbQw9qZwU0FWpBm1awgOk4QoALGzLTcv8nygeS3ToeT72U=
=n6cT
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 2022-07-07 15 h 36, Boyuan Yang wrote:

Hi,

在 2022-06-28星期二的 11:19 -0400，Louis-Philippe Véronneau写道：

On 2022-06-28 09 h 24, Boyuan Yang wrote:

Hi all,

I have encountered more and more packages that uses pdm-pep517 as build
backend. Looking at [1], existing packages in Debian added patches to
manually switch to other backends, such as Poetry.

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. Besides that,
what
about packaging of pdm? Please correct me if needed: my mind and my
packaging work is still stuck in the old times of setup.py, and I just
started to look into the new ecosystem of pep517. Thanks!

Regards,
Boyuan Yang


[1] https://codesearch.debian.net/search?q=pdm.pep517
[2] https://github.com/pdm-project/pdm-pep517

Once packaged, please ping me so I can update the
"missing-prerequisite-for-pyproject-backend" Lintian tag accordingly and
let people know they can migrate to it.

This is now accepted at https://tracker.debian.org/pkg/pdm-pep517 .

Thanks for the work on this.

Here's the lintian MR for reference:

https://salsa.debian.org/lintian/lintian/-/merge_requests/400

--
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau
⢿⡄⠘⠷⠚⠋ pollo@debian.org / veronneau.org
⠈⠳⣄

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Thu, Jul 07, 2022 at 03:36:30PM -0400, Boyuan Yang wrote:

Hi,

在 2022-06-28星期二的 11:19 -0400，Louis-Philippe Véronneau写道：

On 2022-06-28 09 h 24, Boyuan Yang wrote:

Hi all,

I have encountered more and more packages that uses pdm-pep517 as build backend. Looking at [1], existing packages in Debian added patches to manually switch to other backends, such as Poetry.

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. Besides that, what
about packaging of pdm? Please correct me if needed: my mind and my packaging work is still stuck in the old times of setup.py, and I just started to look into the new ecosystem of pep517. Thanks!

Regards,
Boyuan Yang

[1] https://codesearch.debian.net/search?q=pdm.pep517
[2] https://github.com/pdm-project/pdm-pep517

Once packaged, please ping me so I can update the "missing-prerequisite-for-pyproject-backend" Lintian tag accordingly and let people know they can migrate to it.

This is now accepted at https://tracker.debian.org/pkg/pdm-pep517 .

Cheers,
Boyuan Yang

Brilliant! Thanks for this! (I think you'll need to do a source-only
upload now to allow migration to testing, unless the procedures have
changed recently.)

Best wishes,

Julian

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)