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

            A new commit has been pushed.

            Repo   : rpms/archlinux-keyring
            Branch : epel9
            Commit : 3f7af72b4f0b7d04edc98a423f8e4896d9939910
            Author : Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>
            Date   : 2025-10-31T14:32:20+01:00
            Stats  : +5/-3 in 3 file(s)
            URL    : https://src.fedoraproject.org/rpms/archlinux-keyring/c/3f7af72b4f0b7d04edc98a423f8e4896d9939910?branch=epel9

            Log:
            Version 20251027

... (rhbz#2406666)

---
diff --git a/.gitignore b/.gitignore
index 5435c5f..fee1ca5 100644
--- a/.gitignore
+++ b/.gitignore
@@ -70,3 +70,5 @@
 /archlinux-keyring-20250807.1.tar.gz.sig
 /archlinux-keyring-20251012.tar.gz
 /archlinux-keyring-20251012.tar.gz.sig
+/archlinux-keyring-20251027.tar.gz
+/archlinux-keyring-20251027.tar.gz.sig

diff --git a/archlinux-keyring.spec b/archlinux-keyring.spec
index d96bd40..97c7d79 100644
--- a/archlinux-keyring.spec
+++ b/archlinux-keyring.spec
@@ -1,5 +1,5 @@
 Name:           archlinux-keyring
-Version:        20251012
+Version:        20251027
 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 936a097..bd1fd44 100644
--- a/sources
+++ b/sources
@@ -1,2 +1,2 @@
-SHA512 (archlinux-keyring-20251012.tar.gz) = 7cd838b27f2444933d8f4cd812942c761e8d31daddfde046199b98fe66ffc86e50cdcb9337f63bffb7d8d52f76c546d83f7b6c2409d831c1a771a7562c51910a
-SHA512 (archlinux-keyring-20251012.tar.gz.sig) = ba239f957f55ed9fee0c0a16fb48aa3a2e855eceb571b9fdf73dc9e3a7d317e3649fe288b83f1dcfc7de97915922decc09b4e6c622531ee6e15008e9cc632f11
+SHA512 (archlinux-keyring-20251027.tar.gz) = 8ca7577d9031f4d0ff1df65993a441c908e4ce83bf030da2a08923b9cedb845181bc139f869b68eeeac66260178ace7b654774bfb74f31b8ef37567f558ca920
+SHA512 (archlinux-keyring-20251027.tar.gz.sig) = 99d4370f73a118e51968e25894a2b1bef8b2e76573ad6f5bf82d9c077fba8d438e818de20ac289ec35f40490ee18b98159fc364e0c50948aa76413c80f850d4b

                 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=178611082176.1.16179049541459631017.rpms-archlinux-keyring-3f7af72b4f0b@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