public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Benjamin A. Beasley <code@musicinmybrain.net>
To: git-commits@fedoraproject.org
Subject: [rpms/uv] epel10: More spec-file comment improvements
Date: Sun, 16 Aug 2026 07:50:55 GMT [thread overview]
Message-ID: <178686665596.1.14042978166280377249.rpms-uv-ee01661ac5a1@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/uv
Branch : epel10
Commit : ee01661ac5a1422fa98a72ffad2575607c135608
Author : Benjamin A. Beasley <code@musicinmybrain.net>
Date : 2026-08-05T10:44:04+01:00
Stats : +6/-3 in 1 file(s)
URL : https://src.fedoraproject.org/rpms/uv/c/ee01661ac5a1422fa98a72ffad2575607c135608?branch=epel10
Log:
More spec-file comment improvements
---
diff --git a/uv.spec b/uv.spec
index fd0107f..449df87 100644
--- a/uv.spec
+++ b/uv.spec
@@ -45,7 +45,7 @@ Summary: An extremely fast Python package installer and resolver, written
# MIT
# - crates/uv-virtualenv/src/activator/ is vendored and forked from
# python3dist(virtualenv)
-# - crates/uv-netrc/ is vencored from crate(rust-netrc)
+# - crates/uv-netrc/ is vendored from crate(rust-netrc)
#
# Additionally, the following are bundled/forked but happen to be under the
# same (Apache-2.0 OR MIT) terms as uv itself:
@@ -278,8 +278,11 @@ Provides: bundled(crate(keyring)) = 4.0.0~rc2
# rust-netrc 0.1.2[…]”
#
# Upstream justifies the bundling in
-# https://github.com/astral-sh/uv/pull/19409, and the mandatory
-# path-to-unbundling query appears in a comment on that PR.
+# https://github.com/astral-sh/uv/pull/19409: they want unreleased bug fixes,
+# including those pertaining to https://github.com/astral-sh/uv/issues/16083,
+# and to avoid a dependency on thiserror v1. In response to the mandatory
+# query, they report they are open to de-vendoring if a new rust-netrc release
+# with the desired changes appears.
Provides: bundled(crate(rust-netrc)) = 0.1.2
# The contents of crates/uv-virtualenv/src/activator/ are a bundled and
reply other threads:[~2026-08-16 7:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=178686665596.1.14042978166280377249.rpms-uv-ee01661ac5a1@fedoraproject.org \
--to=code@musicinmybrain.net \
--cc=git-commits@fedoraproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox