public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Jakub Jelen <jjelen@redhat.com>
To: git-commits@fedoraproject.org
Subject: [rpms/libgcrypt] rawhide: New upstream release (#2531881)
Date: Mon, 14 Sep 2026 07:51:48 GMT [thread overview]
Message-ID: <178937230873.1.2291459705273245932.rpms-libgcrypt-72aac0e9992e@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/libgcrypt
Branch : rawhide
Commit : 72aac0e9992e16b594f2516e09aa515be163a8fd
Author : Jakub Jelen <jjelen@redhat.com>
Date : 2026-09-14T09:51:35+02:00
Stats : +5/-3 in 3 file(s)
URL : https://src.fedoraproject.org/rpms/libgcrypt/c/72aac0e9992e16b594f2516e09aa515be163a8fd?branch=rawhide
Log:
New upstream release (#2531881)
---
diff --git a/.gitignore b/.gitignore
index e46f7a2..6680ce4 100644
--- a/.gitignore
+++ b/.gitignore
@@ -50,3 +50,5 @@ libgcrypt-1.4.5-hobbled.tar.bz2
/libgcrypt-1.12.2.tar.bz2.sig
/libgcrypt-1.12.3.tar.bz2
/libgcrypt-1.12.3.tar.bz2.sig
+/libgcrypt-1.12.4.tar.bz2
+/libgcrypt-1.12.4.tar.bz2.sig
diff --git a/libgcrypt.spec b/libgcrypt.spec
index dd78797..1d8ba10 100644
--- a/libgcrypt.spec
+++ b/libgcrypt.spec
@@ -1,5 +1,5 @@
Name: libgcrypt
-Version: 1.12.3
+Version: 1.12.4
Release: %autorelease
URL: https://www.gnupg.org/
Source0: https://www.gnupg.org/ftp/gcrypt/libgcrypt/libgcrypt-%{version}.tar.bz2
diff --git a/sources b/sources
index 2c2a78a..03f601e 100644
--- a/sources
+++ b/sources
@@ -1,2 +1,2 @@
-SHA512 (libgcrypt-1.12.3.tar.bz2) = 84c150730af55669e35d3d9109250ae28175da1b506de84117701464ac5c7e542163977a1eb2e5df4cdaa8c723ea759aa8c004cccc98251902482aff7f847cad
-SHA512 (libgcrypt-1.12.3.tar.bz2.sig) = 1a621c62ebe15a706d65b69709d1f415d7c73b68c48f4cf0fed1730e458f49e5e88ef4583514218a76f8c5fb6bb1fd98f2348e12978772af14f8fff7fee04fff
+SHA512 (libgcrypt-1.12.4.tar.bz2) = 632bac4146ba6b3d5e4672e28b1a8b276fcc8bf17961021240b080c6ea4470e46016968a39ee943d3dcd496bda5c9617bf7704bdec75be55847b738809053d8d
+SHA512 (libgcrypt-1.12.4.tar.bz2.sig) = ea1b0648bb88784049de0b0b323e0be8ad6c2d0f33541bb861ff02939847a7c23ced0815b5887b7ec0d1cde8d714d99e745be5adaa3040179c5ae4c6021cceb1
reply other threads:[~2026-09-14 7:51 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=178937230873.1.2291459705273245932.rpms-libgcrypt-72aac0e9992e@fedoraproject.org \
--to=jjelen@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