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-cramjam] rawhide: Rename LICENSES.dependencies to LICENSE.dependencies
Date: Mon, 14 Sep 2026 05:54:40 GMT [thread overview]
Message-ID: <178936528041.1.15255692903309347516.rpms-python-cramjam-a0fa4a116255@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/python-cramjam
Branch : rawhide
Commit : a0fa4a116255f65cf7ba4a1c7171aaacb63da68b
Author : Benjamin A. Beasley <code@musicinmybrain.net>
Date : 2026-09-14T06:49:42+01:00
Stats : +3/-3 in 1 file(s)
URL : https://src.fedoraproject.org/rpms/python-cramjam/c/a0fa4a116255f65cf7ba4a1c7171aaacb63da68b?branch=rawhide
Log:
Rename LICENSES.dependencies to LICENSE.dependencies
https://docs.fedoraproject.org/en-US/packaging-guidelines/Rust/#_non_crate_rust_project
---
diff --git a/python-cramjam.spec b/python-cramjam.spec
index a438a3a..5ecb011 100644
--- a/python-cramjam.spec
+++ b/python-cramjam.spec
@@ -122,14 +122,14 @@ done
%build -p
%cargo_license_summary
-%{cargo_license} > LICENSES.dependencies
+%{cargo_license} > LICENSE.dependencies
%check -a
# If upstream adopts PEP 639 metadata in pyproject.toml and starts listing
-# license files explicitly, LICENSES.dependencies may be dropped from the
+# license files explicitly, LICENSE.dependencies may be dropped from the
# .dist-info directory. Guard against this.
-[ -n "$(find '%{buildroot}%{python3_sitearch}' -name LICENSES.dependencies)" ]
+[ -n "$(find '%{buildroot}%{python3_sitearch}' -name LICENSE.dependencies)" ]
%if %{with tests}
# Test failures in test_variants_decompress_into with recent hypothesis
reply other threads:[~2026-09-14 5:54 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=178936528041.1.15255692903309347516.rpms-python-cramjam-a0fa4a116255@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