Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.maint.python > #17313 > unrolled thread

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

Back to article view | Back to linux.debian.maint.python

Contents

  RFC: Packaging pyartnet - Patch build system from uv to setuptools? Arian Ott <arian.ott@ieee.org> - 2026-01-01 18:20 +0100
    Re: RFC: Packaging pyartnet - Patch build system from uv to  setuptools? Andrey Rakhmatullin <wrar@debian.org> - 2026-01-01 18:30 +0100
      Re: RFC: Packaging pyartnet - Patch build system from uv to setuptools? Arian Ott <arian.ott@ieee.org> - 2026-01-01 18:40 +0100

#17313 — RFC: Packaging pyartnet - Patch build system from uv to setuptools?

[Multipart message — attachments visible in raw view] — view raw

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

Happy new year!

Best,
-- 
*Arian Ott*

*Student in Business Informatics – Data Science* Member | IEEE
Mail: arian.ott@ieee.org
Linkedin: in/arian-ott <https://linkedin.com/in/arian-ott>
GitHub: github.com/Arian-Ott
Germany

[toc] | [next] | [standalone]

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

[Multipart message — attachments visible in raw view] — view raw

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

[toc] | [prev] | [next] | [standalone]

#17315

[Multipart message — attachments visible in raw view] — view raw

On Thu, 1 Jan 2026 at 18:25, Andrey Rakhmatullin <wrar@debian.org> wrote:

> 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).
>
>
Thanks for the confirmation! I will proceed with the patch to setuptools
then.
---
Arian
arian.ott@ieee.org

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.maint.python

csiph-web