[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: uv in debian



Hi Aeliton,

On 11/29/25 09:44, Aeliton G. Silva wrote:
I was looking at this thread [1] from UV's upstream and got curious to
know how is the progress on the Debian side and maybe offer a hand if
needed.
1 - https://github.com/astral-sh/uv/issues/13640

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

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

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.

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

Thanks,
Antonin


Reply to: