public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Fedora Release Engineering <releng@fedoraproject.org>
To: git-commits@fedoraproject.org
Subject: [rpms/jss] pqc: Rebuilt for https://fedoraproject.org/wiki/Fedora_37_Mass_Rebuild
Date: Tue, 28 Jul 2026 16:49:05 GMT [thread overview]
Message-ID: <178525734591.1.2927153158505363402.rpms-jss-3d194c83fd40@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/jss
Branch : pqc
Commit : 3d194c83fd40661cc2741601e1e2f3faa413057d
Author : Fedora Release Engineering <releng@fedoraproject.org>
Date : 2022-07-21T15:28:13+00:00
Stats : +4/-1 in 1 file(s)
URL : https://src.fedoraproject.org/rpms/jss/c/3d194c83fd40661cc2741601e1e2f3faa413057d?branch=pqc
Log:
Rebuilt for https://fedoraproject.org/wiki/Fedora_37_Mass_Rebuild
Signed-off-by: Fedora Release Engineering <releng@fedoraproject.org>
---
diff --git a/jss.spec b/jss.spec
index 823d0ae..e299628 100644
--- a/jss.spec
+++ b/jss.spec
@@ -27,7 +27,7 @@ Summary: Java Security Services (JSS)
URL: https://github.com/dogtagpki/jss
License: MPLv1.1 or GPLv2+ or LGPLv2+
Version: %{major_version}.%{minor_version}.%{update_version}
-Release: %{release_number}%{?phase:.}%{?phase}%{?timestamp:.}%{?timestamp}%{?commit_id:.}%{?commit_id}%{?dist}
+Release: %{release_number}%{?phase:.}%{?phase}%{?timestamp:.}%{?timestamp}%{?commit_id:.}%{?commit_id}%{?dist}.1
# To generate the source tarball:
# $ git clone https://github.com/dogtagpki/jss.git
@@ -208,6 +208,9 @@ modutil -dbdir /etc/pki/nssdb -chkfips true | grep -q enabled && export FIPS_ENA
################################################################################
%changelog
+* Thu Jul 21 2022 Fedora Release Engineering <releng@fedoraproject.org> - 5.2.0-1.1
+- Rebuilt for https://fedoraproject.org/wiki/Fedora_37_Mass_Rebuild
+
* Wed Jun 29 2022 Dogtag PKI Team <devel@lists.dogtagpki.org> - 5.2.0-1
- Rebase to JSS 5.2.0
reply other threads:[~2026-07-28 16: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=178525734591.1.2927153158505363402.rpms-jss-3d194c83fd40@fedoraproject.org \
--to=releng@fedoraproject.org \
--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