public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Matthew Harmsen <mharmsen@redhat.com>
To: git-commits@fedoraproject.org
Subject: [rpms/jss] pqc: Resolves: rhbz #1434535
Date: Tue, 28 Jul 2026 16:48:32 GMT [thread overview]
Message-ID: <178525731291.1.226729645599902528.rpms-jss-8ea4b348367c@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/jss
Branch : pqc
Commit : 8ea4b348367c5bce84d6aec7293ef6c7f0faf939
Author : Matthew Harmsen <mharmsen@redhat.com>
Date : 2017-04-30T23:20:50-06:00
Stats : +13/-4 in 3 file(s)
URL : https://src.fedoraproject.org/rpms/jss/c/8ea4b348367c5bce84d6aec7293ef6c7f0faf939?branch=pqc
Log:
Resolves: rhbz #1434535
- Mozilla Bugzilla #1352476 - RFE: Document on the README how to create a
release tag (mharmsen)
- Mozilla Bugzilla #1355358 - CryptoStore: add methods for importing and
exporting EncryptedPrivateKeyInfo (ftweedal)
- Mozilla Bugzilla #1359731 - CryptoStore.importPrivateKey enhancements
(ftweedal)
---
diff --git a/.gitignore b/.gitignore
index 2af452b..dead9a9 100644
--- a/.gitignore
+++ b/.gitignore
@@ -2,3 +2,4 @@ jss-4.2.6.tar.gz
/jss-4.2.6.tar.gz
/jss-4.4.0.tar.gz
/jss-4.4.1.tar.gz
+/jss-4.4.2.tar.gz
diff --git a/jss.spec b/jss.spec
index 9dfca84..4c50e5b 100644
--- a/jss.spec
+++ b/jss.spec
@@ -1,6 +1,6 @@
Name: jss
-Version: 4.4.1
-Release: 2%{?dist}
+Version: 4.4.2
+Release: 1%{?dist}
Summary: Java Security Services (JSS)
Group: System Environment/Libraries
@@ -11,7 +11,7 @@ URL: http://www.mozilla.org/projects/security/pki/jss/
#
# hg clone https://hg.mozilla.org/projects/jss
# cd jss
-# hg archive --prefix jss-4.4.1/jss/ ../jss-4.4.1.tar.gz
+# hg archive --prefix jss-4.4.2/jss/ ../jss-4.4.2.tar.gz
#
Source0: http://pki.fedoraproject.org/pki/sources/%{name}/%{version}/%{name}-%{version}.tar.gz
Source1: http://pki.fedoraproject.org/pki/sources/%{name}/%{version}/MPL-1.1.txt
@@ -138,6 +138,14 @@ rm -rf $RPM_BUILD_ROOT
%{_javadocdir}/%{name}-%{version}/*
%changelog
+* Mon May 1 2017 Matthew Harmsen <mharmsen@redhat.com> - 4.4.2-1
+- Mozilla Bugzilla #1352476 - RFE: Document on the README how to create a
+ release tag (mharmsen)
+- Mozilla Bugzilla #1355358 - CryptoStore: add methods for importing and
+ exporting EncryptedPrivateKeyInfo (ftweedal)
+- Mozilla Bugzilla #1359731 - CryptoStore.importPrivateKey enhancements
+ (ftweedal)
+
* Mon Apr 17 2017 Matthew Harmsen <mharmsen@redhat.com> - 4.4.1-2
- Mozilla Bugzilla #1355268 - JSS 4.4 is incompatible with versions of
idm-console-framework < 1.1.17-4
diff --git a/sources b/sources
index f479c82..88399b9 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-SHA512 (jss-4.4.1.tar.gz) = 06162955d83adf95552408f087a687e9f30e5a4baa2621ce0be041ab0d3ea0aa7aec7e4db8d53bbe995499ad269a9cabffd756aa239190cdc24048b1cbe3bb22
+SHA512 (jss-4.4.2.tar.gz) = 71f76aef2905c374a0d87b25a73db2498562fe16cef1489c5859271d2ae264695dd2b00880539c35b21f4e0b19856abc5028b813fe05b33352304b538182b251
next reply other threads:[~2026-07-28 16:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-28 16:48 Matthew Harmsen [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-07-28 16:48 [rpms/jss] pqc: Resolves: rhbz #1434535 Matthew Harmsen
2026-07-28 16:48 Matthew Harmsen
2026-07-28 16:48 Matthew Harmsen
2026-07-28 16:48 Matthew Harmsen
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=178525731291.1.226729645599902528.rpms-jss-8ea4b348367c@fedoraproject.org \
--to=mharmsen@redhat.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