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

            A new commit has been pushed.

            Repo   : rpms/archlinux-keyring
            Branch : epel9
            Commit : 22698963b2c02d7c094b8b13226cb84fda588379
            Author : Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>
            Date   : 2026-01-10T11:28:02+01:00
            Stats  : +5/-3 in 3 file(s)
            URL    : https://src.fedoraproject.org/rpms/archlinux-keyring/c/22698963b2c02d7c094b8b13226cb84fda588379?branch=epel9

            Log:
            Version 20260107

... (rhbz#2415251)

---
diff --git a/.gitignore b/.gitignore
index fee1ca5..7660c0b 100644
--- a/.gitignore
+++ b/.gitignore
@@ -72,3 +72,5 @@
 /archlinux-keyring-20251012.tar.gz.sig
 /archlinux-keyring-20251027.tar.gz
 /archlinux-keyring-20251027.tar.gz.sig
+/archlinux-keyring-20260107.tar.gz
+/archlinux-keyring-20260107.tar.gz.sig

diff --git a/archlinux-keyring.spec b/archlinux-keyring.spec
index 97c7d79..f225a93 100644
--- a/archlinux-keyring.spec
+++ b/archlinux-keyring.spec
@@ -1,5 +1,5 @@
 Name:           archlinux-keyring
-Version:        20251027
+Version:        20260107
 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 bd1fd44..d7e5609 100644
--- a/sources
+++ b/sources
@@ -1,2 +1,2 @@
-SHA512 (archlinux-keyring-20251027.tar.gz) = 8ca7577d9031f4d0ff1df65993a441c908e4ce83bf030da2a08923b9cedb845181bc139f869b68eeeac66260178ace7b654774bfb74f31b8ef37567f558ca920
-SHA512 (archlinux-keyring-20251027.tar.gz.sig) = 99d4370f73a118e51968e25894a2b1bef8b2e76573ad6f5bf82d9c077fba8d438e818de20ac289ec35f40490ee18b98159fc364e0c50948aa76413c80f850d4b
+SHA512 (archlinux-keyring-20260107.tar.gz) = 7886fa4e87b00f5a5b70a107572bb1a35733bd540c1ade1a8609c2ea605e9d1c12d3e31c77cd21e68febcb13ffa271ed7028472778b71120b20327172f7e3a36
+SHA512 (archlinux-keyring-20260107.tar.gz.sig) = e568abd1a2568cc7a4f9d3e07daadff866668038a315fcfbe30a641a0cff56a2ee30d4c61f904da4c02a5d5a0938ad2bd8aa490110c5154442dbf5433d73461b

                 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=178611082219.1.14518550530921866179.rpms-archlinux-keyring-22698963b2c0@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