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

            A new commit has been pushed.

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

            Log:
            Version 20260206

... (rhbz#2437287)

---
diff --git a/.gitignore b/.gitignore
index 5636e31..5bb36e8 100644
--- a/.gitignore
+++ b/.gitignore
@@ -78,3 +78,5 @@
 /archlinux-keyring-20260131.tar.gz.sig
 /archlinux-keyring-20260202.tar.gz
 /archlinux-keyring-20260202.tar.gz.sig
+/archlinux-keyring-20260206.tar.gz
+/archlinux-keyring-20260206.tar.gz.sig

diff --git a/archlinux-keyring.spec b/archlinux-keyring.spec
index a3e55ef..e1c9a0d 100644
--- a/archlinux-keyring.spec
+++ b/archlinux-keyring.spec
@@ -1,5 +1,5 @@
 Name:           archlinux-keyring
-Version:        20260202
+Version:        20260206
 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 be22564..7988a6f 100644
--- a/sources
+++ b/sources
@@ -1,2 +1,2 @@
-SHA512 (archlinux-keyring-20260202.tar.gz) = 1456f168cf1e1852ba87e8bf5f6e21af8aeb5bd96fe923c52d3d630729ff3a4e3520f3ae4a2b05f625d9273423cf69ebd274babc8a1cca757f50f4b09c2f3f25
-SHA512 (archlinux-keyring-20260202.tar.gz.sig) = 033f74dbde808ac9bf6ad68f0088f368f97f09ccf160b4191b8a1d707d5a08a75dd16c102004e875cba099129fab1b6402333a3494463cd5b180c60e4b0ce80e
+SHA512 (archlinux-keyring-20260206.tar.gz) = f62351fa924380e760f3202fb320c066ae2ff1d5c140d342fa24aa10eae62236aec46e85033c0ed50713a864f7d24d8309924076328e78662726efdf386886b6
+SHA512 (archlinux-keyring-20260206.tar.gz.sig) = b222801631077a0afbff3405ee489753579fc330064d34c81576067f55ee1755e36c0d42a98bd839323e8c75ef07ccd9898d1c14e6fef9cee1a3a418f3e4bf2b

                 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=178611086835.1.1498421556306352592.rpms-archlinux-keyring-f885a2980046@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