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/python-uv-build] f44: Adjust license expression handling again
Date: Thu, 19 Nov 2026 20:31:35 GMT [thread overview]
Message-ID: <179512029501.1.12575200012546218012.rpms-python-uv-build-a0b9678f3773@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/python-uv-build
Branch : f44
Commit : a0b9678f3773512cb5b7582f0f95e9b8be835c19
Author : Benjamin A. Beasley <code@musicinmybrain.net>
Date : 2026-11-10T23:01:23+00:00
Stats : +3/-3 in 1 file(s)
URL : https://src.fedoraproject.org/rpms/python-uv-build/c/a0b9678f3773512cb5b7582f0f95e9b8be835c19?branch=f44
Log:
Adjust license expression handling again
[skip changelog]
---
diff --git a/python-uv-build.spec b/python-uv-build.spec
index a05d38e..9fb2664 100644
--- a/python-uv-build.spec
+++ b/python-uv-build.spec
@@ -11,11 +11,11 @@ Summary: The uv build backend
# - crates/uv-pep440/ is vendored and forked from crate(pep440_rs)
# - crates/uv-pep508/ is vendored and forked from crate(pep508_rs)
%global upstream_license Apache-2.0 OR MIT
-SourceLicense: (%{upstream_license}) %{shrink:
+%global full_license (%{upstream_license}) %{shrink:
AND (Apache-2.0 OR BSD-2-Clause)
AND MPL-2.0
}
-License: %{sourcelicense}
+License: %{full_license}
# Rust crates compiled into the executable contribute additional license terms.
# To obtain the following list of licenses, build the package and note the
# output of %%{cargo_license_summary}.
@@ -39,7 +39,7 @@ License: %{sourcelicense}
# Unicode-3.0
# Unlicense OR MIT
# Zlib
-%global full_license %{sourcelicense} %{shrink:
+%global built_license %{full_license} %{shrink:
AND (0BSD OR Apache-2.0 OR MIT)
AND (Apache-2.0 OR Apache-2.0 WITH LLVM-exception OR MIT)
AND (Apache-2.0 OR BSD-2-Clause OR MIT)
reply other threads:[~2026-11-19 20:31 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=179512029501.1.12575200012546218012.rpms-python-uv-build-a0b9678f3773@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