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

            A new commit has been pushed.

            Repo   : rpms/archlinux-keyring
            Branch : epel9
            Commit : bd81c16ae01fe315c5e44ce0ad6c465d1641a0a6
            Author : Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>
            Date   : 2025-07-17T15:29:39+02:00
            Stats  : +5/-3 in 3 file(s)
            URL    : https://src.fedoraproject.org/rpms/archlinux-keyring/c/bd81c16ae01fe315c5e44ce0ad6c465d1641a0a6?branch=epel9

            Log:
            Version 20250716

... (rhbz#2376804)

---
diff --git a/.gitignore b/.gitignore
index 208fb06..8b7aa6b 100644
--- a/.gitignore
+++ b/.gitignore
@@ -64,3 +64,5 @@
 /archlinux-keyring-20250123.tar.gz
 /archlinux-keyring-20250430.1.tar.gz
 /archlinux-keyring-20250430.1.tar.gz.sig
+/archlinux-keyring-20250716.tar.gz
+/archlinux-keyring-20250716.tar.gz.sig

diff --git a/archlinux-keyring.spec b/archlinux-keyring.spec
index acf2974..f32b292 100644
--- a/archlinux-keyring.spec
+++ b/archlinux-keyring.spec
@@ -1,5 +1,5 @@
 Name:           archlinux-keyring
-Version:        20250430.1
+Version:        20250716
 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 7ea2837..8519d8a 100644
--- a/sources
+++ b/sources
@@ -1,2 +1,2 @@
-SHA512 (archlinux-keyring-20250430.1.tar.gz) = 774f357e0b620f38780ffc1d9724e7206b0d5d3edef47af4b92e1850a0f1bb2859c57387d13a60cf016e4fa144d1e0b28c42a80295dc5f114d7dd01972c2753e
-SHA512 (archlinux-keyring-20250430.1.tar.gz.sig) = fab150fe178f948061893e306144ee4f4a276cd76af0078e75a92a79dd6471a1496106362d6a3e726a00b4becdf3e789f3e9b949b073002b166dbcfc63c934b9
+SHA512 (archlinux-keyring-20250716.tar.gz) = a2f14cc8bff1e3421d0cc46cbaf091d13a30be1eb4e4c6fc52bbf3c6dc2783cdd3e5e5faa90568b2f0669301970c2fc34e580384d6090793bfe63878287d6ab8
+SHA512 (archlinux-keyring-20250716.tar.gz.sig) = a422e01e5ea28723cfce0d781d29242dfda9fd541bdd652234ff4fc33cd63489f5d8dfc09b8e3937d92ee7c6323e87f1477e69f8ee12e353bdb124b18f36f9c0

                 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=178611081986.1.11250128631737315146.rpms-archlinux-keyring-bd81c16ae01f@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