Re: RFC: Packaging pyartnet - Patch build system from uv to setuptools?

Andrey Rakhmatullin <[email protected]> Thu, 1 Jan 2026 22:25:19 +0500

Newsgroups	gmane.linux.debian.devel.python
Message-ID	<[email protected]>

On Thu, Jan 01, 2026 at 06:17:04PM +0100, Arian Ott wrote:
>Hello everyone,
>
>I am currently packaging pyartnet for Debian (Bug: 1124471). The upstream
>project uses uv as build backend. When building the package, gbp fails
>since uv_build is unavailable and can't be imported.
>
>Pyartnet requires no significant external libraries.
>Can I switch the build backend to setuptools using a patch or is this
>considered bad practice?
>
>https://salsa.debian.org/Arian-Ott/pyartnet/-/blob/debian/latest/pyproject.toml?ref_type=heads#L62-64

I would do that (and did for python-cryptography-vectors, though that 
package is trivial and doesn't contain Python code, and I was just
reverting an upstream change, not even writing my own patch).

-- 
WBR, wRAR

signature.asc (application/pgp-signature, 894 B)