public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
To: git-commits@fedoraproject.org
Subject: [rpms/archlinux-keyring] epel9: Version 20250123
Date: Fri, 07 Aug 2026 13:53:38 GMT	[thread overview]
Message-ID: <178611081839.1.7223254710085088933.rpms-archlinux-keyring-775e223cc034@fedoraproject.org> (raw)

            A new commit has been pushed.

            Repo   : rpms/archlinux-keyring
            Branch : epel9
            Commit : 775e223cc0347679f2e55c85c80e4c4ff964b084
            Author : Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>
            Date   : 2025-01-23T09:45:53+01:00
            Stats  : +5/-3 in 3 file(s)
            URL    : https://src.fedoraproject.org/rpms/archlinux-keyring/c/775e223cc0347679f2e55c85c80e4c4ff964b084?branch=epel9

            Log:
            Version 20250123

... (rhbz#2341704)

---
diff --git a/.gitignore b/.gitignore
index 67dbfe7..fa423d7 100644
--- a/.gitignore
+++ b/.gitignore
@@ -60,3 +60,5 @@
 /archlinux-keyring-20241015.tar.gz
 /archlinux-keyring-20241203.tar.gz
 /archlinux-keyring-20241203.tar.gz.sig
+/archlinux-keyring-20250123.tar.gz.sig
+/archlinux-keyring-20250123.tar.gz

diff --git a/archlinux-keyring.spec b/archlinux-keyring.spec
index c2c88dc..6bb1b56 100644
--- a/archlinux-keyring.spec
+++ b/archlinux-keyring.spec
@@ -1,5 +1,5 @@
 Name:           archlinux-keyring
-Version:        20241203
+Version:        20250123
 Release:        %autorelease
 Url:            https://archlinux.org/packages/core/any/archlinux-keyring/
 Source0:        https://gitlab.archlinux.org/archlinux/archlinux-keyring/-/archive/%{version}/archlinux-keyring-%{version}.tar.gz

diff --git a/sources b/sources
index d59ae67..47ba2ce 100644
--- a/sources
+++ b/sources
@@ -1,2 +1,2 @@
-SHA512 (archlinux-keyring-20241203.tar.gz) = ef680d29f80b874f4175856e7e77ac28e19a8fa53e555f217d5eaf4ac42af3ee770a77f96eb353804b29dc7fecf1426a4a274f074387021263e76ba076126c40
-SHA512 (archlinux-keyring-20241203.tar.gz.sig) = ac2f7455f0f6a82477035b3deb85bb441b3fba1fc7d26487ac95b1da14df325509d85a602303d13528f44add5a843a134e195f25354d5cfef8f9df882bf88401
+SHA512 (archlinux-keyring-20250123.tar.gz) = a5531df88f860e08d697231fed8bb5b5623211778854b57bd73a3ebf9a26102a17f3e2b55e5371aee6f73011a111731a12b5072bc745fc2040b7ed84858ffc73
+SHA512 (archlinux-keyring-20250123.tar.gz.sig) = 4a33121b4389c1488a9f5dbe8bb5c45750cd48fad8b119265a9e8a8bd37291c245fb400394b834c27e058bcf06066414fe335184b06fafab4e9f2e98d25b5058

                 reply	other threads:[~2026-08-07 13:53 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=178611081839.1.7223254710085088933.rpms-archlinux-keyring-775e223cc034@fedoraproject.org \
    --to=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