public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
To: git-commits@fedoraproject.org
Subject: [rpms/archlinux-keyring] epel10: Version 20260409
Date: Fri, 07 Aug 2026 13:54:12 GMT	[thread overview]
Message-ID: <178611085259.1.17583957331364568690.rpms-archlinux-keyring-e9626ac37024@fedoraproject.org> (raw)

            A new commit has been pushed.

            Repo   : rpms/archlinux-keyring
            Branch : epel10
            Commit : e9626ac370240391cee9d49378d9e9d32c72b9f5
            Author : Zbigniew Jędrzejewski-Szmek <zbyszek@amutable.com>
            Date   : 2026-04-10T16:10:25+02:00
            Stats  : +5/-3 in 3 file(s)
            URL    : https://src.fedoraproject.org/rpms/archlinux-keyring/c/e9626ac370240391cee9d49378d9e9d32c72b9f5?branch=epel10

            Log:
            Version 20260409

... (rhbz#2457162)

---
diff --git a/.gitignore b/.gitignore
index 3b3cd18..f4c1d3d 100644
--- a/.gitignore
+++ b/.gitignore
@@ -82,3 +82,5 @@
 /archlinux-keyring-20260206.tar.gz.sig
 /archlinux-keyring-20260323.tar.gz
 /archlinux-keyring-20260323.tar.gz.sig
+/archlinux-keyring-20260409.tar.gz
+/archlinux-keyring-20260409.tar.gz.sig

diff --git a/archlinux-keyring.spec b/archlinux-keyring.spec
index c2615b7..44586cd 100644
--- a/archlinux-keyring.spec
+++ b/archlinux-keyring.spec
@@ -1,5 +1,5 @@
 Name:           archlinux-keyring
-Version:        20260323
+Version:        20260409
 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 cce378a..9620ea8 100644
--- a/sources
+++ b/sources
@@ -1,2 +1,2 @@
-SHA512 (archlinux-keyring-20260323.tar.gz) = c10f5bf65a826c8f9f8627bcfa251a482874138e5e82ce3fceac5fc53795b013b164e2f900955342c293ad6b8963b6faae55c65863678cbd98e4ba288ea2266c
-SHA512 (archlinux-keyring-20260323.tar.gz.sig) = 80bdd224e448fb7922380aae386a9ff3de21d0713d2aad2a9cc8871aabf97be0330f0ae2600eb0c25855368875d550c4d27c41f8cd048da7e7913ebf8bbae95d
+SHA512 (archlinux-keyring-20260409.tar.gz) = 9eeb176e485db322d818b90a63ae471657e51d86ca5e5bc7ccc85b1094b86935e1a49861d0d4199d4e5d9b4a827e70eb5f6cecff53fbfc852a406cda5cc0c13b
+SHA512 (archlinux-keyring-20260409.tar.gz.sig) = bbb63f283c1572b1f2faffd3d0a5bf8b216c1716eda037d6f3555edd7fde55f927002f7f39f177fc5a687b95875fa6768fa149ba4a46f141c2a33d6dc9ad7c98

                 reply	other threads:[~2026-08-07 13:54 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=178611085259.1.17583957331364568690.rpms-archlinux-keyring-e9626ac37024@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