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

            A new commit has been pushed.

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

            Log:
            Version 20260131

... (rhbz#2435635)

---
diff --git a/.gitignore b/.gitignore
index 7660c0b..16cfa6f 100644
--- a/.gitignore
+++ b/.gitignore
@@ -74,3 +74,5 @@
 /archlinux-keyring-20251027.tar.gz.sig
 /archlinux-keyring-20260107.tar.gz
 /archlinux-keyring-20260107.tar.gz.sig
+/archlinux-keyring-20260131.tar.gz
+/archlinux-keyring-20260131.tar.gz.sig

diff --git a/archlinux-keyring.spec b/archlinux-keyring.spec
index f225a93..9bb155b 100644
--- a/archlinux-keyring.spec
+++ b/archlinux-keyring.spec
@@ -1,5 +1,5 @@
 Name:           archlinux-keyring
-Version:        20260107
+Version:        20260131
 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 d7e5609..73113f1 100644
--- a/sources
+++ b/sources
@@ -1,2 +1,2 @@
-SHA512 (archlinux-keyring-20260107.tar.gz) = 7886fa4e87b00f5a5b70a107572bb1a35733bd540c1ade1a8609c2ea605e9d1c12d3e31c77cd21e68febcb13ffa271ed7028472778b71120b20327172f7e3a36
-SHA512 (archlinux-keyring-20260107.tar.gz.sig) = e568abd1a2568cc7a4f9d3e07daadff866668038a315fcfbe30a641a0cff56a2ee30d4c61f904da4c02a5d5a0938ad2bd8aa490110c5154442dbf5433d73461b
+SHA512 (archlinux-keyring-20260131.tar.gz) = a2fca1363133551f452e13c08df01066418a8be7a3d7c841db4b5648f1d7e91d83aae457ce6d08c515ab95fe30f425dfde496585a27e6528f8d2a637f87b3487
+SHA512 (archlinux-keyring-20260131.tar.gz.sig) = 56469f0820d1f611d6cfeea1bc9a8a986742b41ad49cb0f71b58044b3014e34c65e350c25423f14caa9397bd298650777725d048f568a348c8b1f55cc410e6ab

                 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=178611082363.1.14488775916855823714.rpms-archlinux-keyring-37b7519e9a0a@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