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

            A new commit has been pushed.

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

            Log:
            Version 20260202

... (rhbz#2436009)

---
diff --git a/.gitignore b/.gitignore
index 16cfa6f..5636e31 100644
--- a/.gitignore
+++ b/.gitignore
@@ -76,3 +76,5 @@
 /archlinux-keyring-20260107.tar.gz.sig
 /archlinux-keyring-20260131.tar.gz
 /archlinux-keyring-20260131.tar.gz.sig
+/archlinux-keyring-20260202.tar.gz
+/archlinux-keyring-20260202.tar.gz.sig

diff --git a/archlinux-keyring.spec b/archlinux-keyring.spec
index 9bb155b..a3e55ef 100644
--- a/archlinux-keyring.spec
+++ b/archlinux-keyring.spec
@@ -1,5 +1,5 @@
 Name:           archlinux-keyring
-Version:        20260131
+Version:        20260202
 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 73113f1..be22564 100644
--- a/sources
+++ b/sources
@@ -1,2 +1,2 @@
-SHA512 (archlinux-keyring-20260131.tar.gz) = a2fca1363133551f452e13c08df01066418a8be7a3d7c841db4b5648f1d7e91d83aae457ce6d08c515ab95fe30f425dfde496585a27e6528f8d2a637f87b3487
-SHA512 (archlinux-keyring-20260131.tar.gz.sig) = 56469f0820d1f611d6cfeea1bc9a8a986742b41ad49cb0f71b58044b3014e34c65e350c25423f14caa9397bd298650777725d048f568a348c8b1f55cc410e6ab
+SHA512 (archlinux-keyring-20260202.tar.gz) = 1456f168cf1e1852ba87e8bf5f6e21af8aeb5bd96fe923c52d3d630729ff3a4e3520f3ae4a2b05f625d9273423cf69ebd274babc8a1cca757f50f4b09c2f3f25
+SHA512 (archlinux-keyring-20260202.tar.gz.sig) = 033f74dbde808ac9bf6ad68f0088f368f97f09ccf160b4191b8a1d707d5a08a75dd16c102004e875cba099129fab1b6402333a3494463cd5b180c60e4b0ce80e

                 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=178611086787.1.3980154750573082555.rpms-archlinux-keyring-ab57f8f7c2bb@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