Re: uv in debian
On Sat, 2025-11-29 at 10:47 +0100, Antonin Delpeuch (lists) wrote:
>
> I have been working on packaging uv_build, so that it can be used as
> build backend for Python projects. This relies on significantly less
> dependencies than the full "uv" CLI. Which one are you interested in?
> The (very early stage) draft package is here:
>
> https://salsa.debian.org/rust-team/uv/-/tree/debian/latest
>
That's good to know! I keep an eye on that.
> There are many ways you can help :)
>
> The dependencies for uv_build are still making their way through the
> NEW
> queue: "rust-spdx", "rust-astral-version-ranges", "rust-toml-parser".
> If
> there is a way to nudge them to find their way out of the queue, it
> will
> help.
>
> If you are familiar with Rust packaging, you could look into
> upgrading
> schemars to 1.1:
> https://salsa.debian.org/rust-team/debcargo-conf/-/issues/154
I'm not familiar with rust packaging yet, but I'm keen to learn. I'll
be happy to read the current docs and try things locally.
I started to have a look at the schemars porting yesterday when I was
looking for information about ruff that has been just remove from
testing [1].
>
> Otherwise, for packaging the full uv CLI, there are plenty of other
> Rust
> crates that need to be packaged: "ambient-id",
> "astral_async_http_range_reader", "astral_async_zip", "astral-
> pubgrub",
> "astral-reqwest-middleware", "astral-reqwest-retry", "astral-tl",
> "cyclonedx-bom-macros", "cyclonedx-bom", "purl" and more.
>
I'd love to package some stuff, but it seems that the schemars issues
are blocking at the moment multiple packages at the moment, so if
that's the case, I'd like to learn more about it and try to help with
that if that's ok.
> If you are familiar with Python packaging, you could look into adding
> whatever is needed to this draft source package for it to expose the
> appropriate binary package for a Python lib (if that's the
> appropriate
> way of doing things). For now I have only been working on the
> generation
> of the uv_build binary from the Rust side.
>
> But I imagine it's difficult to work on the Python packaging as long
> as
> the Rust binary doesn't build (because the dependencies aren't
> available
> or up to date yet).
>
> See the ITP:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1115616
Just subscribed to it, thanks for sharing.
I'll do some reading now :)
1 - https://tracker.debian.org/news/1645108/ruff-removed-from-testing/
Cheers,
Aeliton
Reply to: