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-bcrypt] epel10: Make Rust dependency licenses easier to edit and audit
Date: Tue, 07 Jul 2026 05:49:54 GMT	[thread overview]
Message-ID: <178340339400.1.12185732551407858613.rpms-python-bcrypt-0bbbe125e921@fedoraproject.org> (raw)

            A new commit has been pushed.

            Repo   : rpms/python-bcrypt
            Branch : epel10
            Commit : 0bbbe125e9210b21991627a9c1e16380fff8cc66
            Author : Benjamin A. Beasley <code@musicinmybrain.net>
            Date   : 2026-07-07T05:28:08+01:00
            Stats  : +14/-1 in 1 file(s)
            URL    : https://src.fedoraproject.org/rpms/python-bcrypt/c/0bbbe125e9210b21991627a9c1e16380fff8cc66?branch=epel10

            Log:
            Make Rust dependency licenses easier to edit and audit

[skip changelog]

---
diff --git a/python-bcrypt.spec b/python-bcrypt.spec
index 2db759d..dcb4e66 100644
--- a/python-bcrypt.spec
+++ b/python-bcrypt.spec
@@ -31,8 +31,21 @@ Patch:          python-bcrypt-4.3.0-pyo3.patch
 
 %package -n python3-%{modname}
 Summary:            %{sum}
+# Includes statically linked Rust dependencies from %%{cargo_license_summary}:
+#
+# Apache-2.0 OR MIT
+# BSD-3-Clause
+# MIT
+# MIT OR Apache-2.0
+# Unlicense OR MIT
+License:            %{shrink:
+    Apache-2.0 AND LicenseRef-Fedora-Public-Domain AND
+    BSD-3-Clause AND
+    MIT AND
+    (Apache-2.0 OR MIT) AND
+    (Unlicense OR MIT)
+    }
 # LICENSE.dependencies contains a full license breakdown
-License:            Apache-2.0 AND LicenseRef-Fedora-Public-Domain AND BSD-3-Clause AND MIT AND (Apache-2.0 OR MIT) AND (Unlicense OR MIT)
 BuildRequires:      python3-devel
 BuildRequires:      rust-packaging
 

                 reply	other threads:[~2026-07-07  5:49 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=178340339400.1.12185732551407858613.rpms-python-bcrypt-0bbbe125e921@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