* Package name    : uv
  Version         : 0.1.37
  Upstream Contact: Charlie Marsh <charlie.r.marsh@gmail.com>
* URL             : https://github.com/astral-sh/uv
* License         : MIT, Apache-2.0
  Programming Lang: Rust
  Description     : an extremely fast Python package installer and resolver, written in Rust

uv is an extremely fast Python package installer and resolver, written in Rust.
Designed as a drop-in replacement for common pip and pip-tools workflows.

- Drop-in replacement for common pip, pip-tools, and virtualenv commands.
- 10-100x faster than pip and pip-tools (pip-compile and pip-sync).
- Disk-space efficient, with a global cache for dependency deduplication.
- Tested at-scale against the top 10,000 PyPI packages.
- Advanced features such as dependency version overrides and alternative
  resolution strategies.
- Best-in-class error messages with a conflict-tracking resolver.
- Support for a wide range of advanced pip features, including editable
  installs, Git dependencies, direct URL dependencies, local dependencies,
  constraints, source distributions, HTML and JSON indexes, and more.

Hi!

I'm interest in work on it.

Cheers,
Emmanuel

Hi Emmanuel,

Are you still planning to package uv? Is there anything I can do to help
move it forward?

Taavi

Hi,

Sorry I was on VAC.

Please take a look here: https://lists.debian.org/debian-rust/2024/12/msg00018.html

Hi Emmanuel

Thankst for taking on this ITP and already packaging some (or all?) of
its dependencies -- looking at librust-http-content-range-dev now
happily residing in Debian.  Do you think you would find more of spare
cycles to get uv itself over the finish line?

Cheers and thanks in advance!

Hi!
I've just stop working on it because freezing. I can continue working on uv,
but I will try to help fixing RC bugs during this period first.

Hi Emmanuel,

I've been working on packaging uv_build, but it looks like getting the
full UV cli packaged wouldn't be much more effort - and it would likely
make sense to do it from the same source package.

Would it be okay for me to take over this ITP, or are you still working
on this?

ITP for uv_build: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1115616

Best,

Antonin

Hi,

some of my packages migrated to use uv/uv_build and I'm now blocked from
uploading newer upstream releases.

What's the status of this bug? Are you still interested, will it be
uploaded anytime soon?

Regards,
Daniel

Hi,

Yes, I'm interested in continuing this work. My conclusion is that it's
not so much more work to package the full "uv" instead of just
"uv_build". I'm hoping to upload it to experimental in the coming month.
Upload to unstable will remain blocked by various dependencies still in
the NEW queue.

Unless Emmanuel shouts I would reassign myself the "uv" ITP in the
coming days.

Best,

Antonin

Hi,

Quoting Antonin Delpeuch (2026-01-05 13:55:29)

Please reassign. Also, it would be great if you can maintain update us
how the package is going. I'm busy but if you have some
issues/problems just ping me/us.

Thanks for that!

cheers,
        Emmanuel Arias

 ⢀⣴⠾⠻⢶⣦⠀
 ⣾⠁⢠⠒⠀⣿⡁  eamanu@debian.org
 ⢿⡄⠘⠷⠚⠋⠀  OpenPGP: 13796755BBC72BB8ABE2AEB5 FA9DEC5DE11C63F1
 ⠈⠳⣄

Here is an update on this front.

This is waiting on the following packages to get out of the NEW queue:

- rust-astral-version-ranges

- rust-next-version

- rust-retry-policies

- rust-spdx

- rust-ambient-id

- rust-markdown

If you are familiar with Rust packaging, you can help by:

- getting reqsign 0.18.0 packaged (preferably by packaging the entire
workspace into one source package)

- updating schemars to 1.0 (Colin Watson has expressed interest in this)

Those updates would be nice to have, but downgrading them in uv look
doable too.

Cheers,

Antonin

From the dependencies I've packaged there's only one still to be
processed by the DSFG team [1]:

# Pending review
- rust-astral-async-zip

The others were accepted and some have been uploaded.

# Uploaded:
- rust-tracing-test
- rust-tracing-test-macro

# Accepted (not uploaded yet)
- rust-astral-async-http-range-reader
- rust-astral-pubgrub
- rust-astral-reqwest-middleware
- rust-astral-reqwest-retry
- rust-astral-tl
- rust-cyclonedx-bom
- rust-cyclonedx-bom-macros
- rust-wasmtimer


1 - https://dfsg-new-queue.debian.org/reviews/history

Hi,

it seems all build-depends for uv are in the archive now, do you plan to
upload uv soon?

Regards,
Daniel

Hi Daniel,

Thanks for the ping on this. Some of the dependencies are still only in
experimental and not in unstable, so I've requested their sponsorship to
unstable. I have also held back by the difficulty to get DM permissions
on the packages I uploaded. I have requested both of those in the Rust
team, it should hopefully happen in the coming days.

(One suggestion in passing: would it not make sense if as a DM, when a
DD sponsors the upload of a new package I created, I automatically get
DM rights on it once it has been accepted in the archive? This would
remove some friction for projects like this one.)

Best,

Antonin

Hi,

not a blocker for uv, you can upload to experimental too, and people
using uv can upload to experimental.. if you don't, nobody can do
anything and everyone is waiting :)

thanks.

you can ask me to sponsor any packages, I'm glad to help.

DM upload rights are to be given to by your regular sponsor to you, if
they feel comfortable you doing the uploads for that package
unsupervised - that is not and should not be an automatic thing.

again, happy to sponsor any packages for you, just give me the URLs to
the dsc.

Regards,
Daniel

Hi,

Thanks for the offer to help!

I've been working on the packaging ahead of the dependencies being
available in unstable indeed. But there are several pieces of tooling
involved in the packaging (cargo-debstatus, Salsa CI) which don't work
so well with experimental, so it adds friction to my work, and to the
work of my sponsors. Given that those dependencies will need to be in
unstable sooner or later, I think it makes sense to do that at this point :)

The packages are rust-astral-reqwest-retry,
rust-astral-async-http-range-reader, rust-astral-pubgrub,
rust-cyclonedx-bom. Yifei from the Rust team indicated they would be
happy to upload them later today if no-one did before, so that should be
all good.

Best,

Antonin

Hi,

btw, note that when you CC only the bug, people will most of the time
only see your messages when they manually look up the bug tracker (i.e.
mailing the bug only means, only the bug gets the mail, thus it's
encuraged to CC people).

fortunately this has happened, all of them are in unstable.

Regards,
Daniel

Hi Daniel,

A first version of the package, exposing only `python3-uv-build`, is
available here:

https://salsa.debian.org/rust-team/uv

I plan to make follow up improvements (exposing all of `uv`, not just
`uv_build`, upgrading to a more version, autopkgtest that actually runs
tests), but we're at a state where the package should hopefully already
be usable by Python packages (although I didn't try myself, not being so
familiar with Python packaging).

If someone wants to sponsor its upload to experimental or unstable, that
would be helpful for it to clear the NEW queue.

Cheers,

Antonin

Thanks for your work on this Antonin.

I have a python package where the upstream uses uv and I had to patched
to use setuptools [1]. Once uv_build is in I can give it a go to check
how it would work.

I have a question about the versions of the uv deps I've packaged, all
of them have new upstream vesions. I wonder if it would help or hurt if
I update them whilst you are still working on packaging the rest of uv.
The list is this:

rust-astral-async-http-range-reader
rust-astral-async-zip
rust-astral-reqwest-middleware
rust-astral-reqwest-retry
rust-astral-tl
rust-cyclonedx-bom
rust-tracing-test
rust-tracing-test-macro

What are your thoughts?

Cheers,
Aeliton

1 -
https://salsa.debian.org/python-team/packages/audio-visualizer-python/-/blob/debian/main/debian/patches/0001-Change-backend-to-setuptools.patch?ref_type=heads
2 -

Hi Aeliton,

It would be great to update them - I was actually looking into updating
astral-reqwest-middleware and astral-reqwest-retry today.

The update will break the build of the uv package but I can work on
fixing that soon after.

Thanks for your work!

Antonin

Hi Antonin,

what's the status? can you upload the debian source package so I can
review and sponsor it?

Regards,
Daniel

Hi Daniel,

The package is ready for upload indeed, thanks for volunteering to
sponsor it :)

The debian source package built by Salsa CI can be found here:

https://salsa.debian.org/rust-team/uv/-/jobs/9568206/artifacts/download?file_type=archive

Otherwise you should be able to get it by running `gbp buildpackage` in
the repo.

All the best,

Antonin

We have a first version of the source package in unstable, exposing a
`python3-uv-build` binary package. Many thanks to Andrius Merkys for
sponsoring the package again. This ITP remains open because we should
also have an `uv` binary package for the full CLI.

I wouldn't be surprised if most of the bugs marked as being blocked by
this ITP were on fact only waiting on `python3-uv-build`.

I intend to work on catching up with upstream before turning to
packaging the full CLI.

Antonin

Closing as uv package is now in unstable.

Hello,

Should this bug be closed? Only python3-uv-build has been uploaded, not the full uv CLI tool.

Thanks!