public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Jeremy Cline <jeremycline@microsoft.com>
To: git-commits@fedoraproject.org
Subject: [rpms/rust-sigul-pesign-bridge] f44: Update to v0.10.1
Date: Thu, 09 Jul 2026 20:34:48 GMT	[thread overview]
Message-ID: <178362928844.1.6568613537411011154.rpms-rust-sigul-pesign-bridge-c44921c1bbd3@fedoraproject.org> (raw)

            A new commit has been pushed.

            Repo   : rpms/rust-sigul-pesign-bridge
            Branch : f44
            Commit : c44921c1bbd392551f6f4bb23d2eed29e34ff1dd
            Author : Jeremy Cline <jeremycline@microsoft.com>
            Date   : 2026-07-09T16:31:07-04:00
            Stats  : +9/-3 in 3 file(s)
            URL    : https://src.fedoraproject.org/rpms/rust-sigul-pesign-bridge/c/c44921c1bbd392551f6f4bb23d2eed29e34ff1dd?branch=f44

            Log:
            Update to v0.10.1

- Updates license to reflect current dependencies

---
diff --git a/.gitignore b/.gitignore
index fae74b0..1e11e74 100644
--- a/.gitignore
+++ b/.gitignore
@@ -6,3 +6,4 @@
 /sigul-pesign-bridge-0.8.0.crate
 /sigul-pesign-bridge-0.9.0.crate
 /sigul-pesign-bridge-0.10.0.crate
+/sigul-pesign-bridge-0.10.1.crate

diff --git a/rust-sigul-pesign-bridge.spec b/rust-sigul-pesign-bridge.spec
index 0e5a3a4..f544b2a 100644
--- a/rust-sigul-pesign-bridge.spec
+++ b/rust-sigul-pesign-bridge.spec
@@ -7,7 +7,7 @@
 %global crate sigul-pesign-bridge
 
 Name:           rust-sigul-pesign-bridge
-Version:        0.10.0
+Version:        0.10.1
 Release:        %autorelease
 Summary:        Bridge pesign-client requests to a Sigul signing server
 
@@ -32,13 +32,18 @@ requests to a Sigul server.}
 %package     -n sigul-pesign-bridge
 Summary:        %{summary}
 # (MIT OR Apache-2.0) AND Unicode-DFS-2016
+# Apache-2.0
 # Apache-2.0 OR MIT
 # Apache-2.0 WITH LLVM-exception OR Apache-2.0 OR MIT
 # BSD-2-Clause OR Apache-2.0 OR MIT
+# BSD-3-Clause
+# BSL-1.0
+# LGPL-2.0-or-later
 # MIT
 # MIT OR Apache-2.0
+# Unicode-3.0
 # Unlicense OR MIT
-License:        Unicode-DFS-2016 AND (MIT OR Apache-2.0) AND (Apache-2.0 WITH LLVM-exception OR Apache-2.0 OR MIT) AND (BSD-2-Clause OR Apache-2.0 OR MIT) AND MIT AND (Unlicense OR MIT)
+License:        ((MIT OR Apache-2.0) AND Unicode-DFS-2016) AND (Apache-2.0) AND (Apache-2.0 OR MIT) AND (Apache-2.0 WITH LLVM-exception OR Apache-2.0 OR MIT) AND (BSD-2-Clause OR Apache-2.0 OR MIT) AND (BSD-3-Clause) AND (BSL-1.0) AND (LGPL-2.0-or-later) AND (MIT) AND (MIT OR Apache-2.0) AND (Unicode-3.0) AND (Unlicense OR MIT)
 # LICENSE.dependencies contains a full license breakdown
 
 # Enables support for the "socket_acl" setting

diff --git a/sources b/sources
index ccb0c55..a4bcf1d 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-SHA512 (sigul-pesign-bridge-0.10.0.crate) = 05fcceb4c37146baf23d4c6e00e3256c554696f9b683cb304bb2143998bc8a24911aa71451a919f2d5d0a44606ddf321a9fa9ba9172813dc7bd55a976796d39a
+SHA512 (sigul-pesign-bridge-0.10.1.crate) = e5f237e71a12ebdbc925075144f9ae1dc70b980eb2b6e22cd77d37a4572b1b3db20c6ac96afd4fc43ec7f94a92c40caf009b6497d5d28035a6cdacc227b72861

                 reply	other threads:[~2026-07-09 20:34 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=178362928844.1.6568613537411011154.rpms-rust-sigul-pesign-bridge-c44921c1bbd3@fedoraproject.org \
    --to=jeremycline@microsoft.com \
    --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