public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Steve Cossette <farchord@gmail.com>
To: git-commits@fedoraproject.org
Subject: [rpms/kgpg] f43: 26.04.0
Date: Tue, 23 Jun 2026 17:57:36 GMT [thread overview]
Message-ID: <178223745627.1.885008608273069265.rpms-kgpg-839bdf9fe410@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/kgpg
Branch : f43
Commit : 839bdf9fe410791f22ffa9d18cdf6757c165b68c
Author : Steve Cossette <farchord@gmail.com>
Date : 2026-04-13T20:49:24-04:00
Stats : +6/-2 in 3 file(s)
URL : https://src.fedoraproject.org/rpms/kgpg/c/839bdf9fe410791f22ffa9d18cdf6757c165b68c?branch=f43
Log:
26.04.0
---
diff --git a/.gitignore b/.gitignore
index ba96a79..e9518bd 100644
--- a/.gitignore
+++ b/.gitignore
@@ -103,3 +103,4 @@
/kgpg-25.12.2.tar.xz
/kgpg-25.12.3.tar.xz
/kgpg-26.03.80.tar.xz
+/kgpg-26.04.0.tar.xz
diff --git a/kgpg.spec b/kgpg.spec
index 49ad6fa..3c9f55c 100644
--- a/kgpg.spec
+++ b/kgpg.spec
@@ -1,6 +1,6 @@
Name: kgpg
Summary: Manage GPG encryption keys
-Version: 26.03.80
+Version: 26.04.0
Release: 1%{?dist}
License: CC0-1.0 AND GPL-2.0-only AND GPL-2.0-or-later AND GPL-3.0-only AND (GPL-2.0-only OR GPL-3.0-only)
@@ -104,6 +104,9 @@ desktop-file-validate %{buildroot}%{_kf6_datadir}/applications/org.kde.%{name}.d
%changelog
+* Sat Apr 11 2026 Steve Cossette <farchord@gmail.com> - 26.04.0-1
+- 26.04.0
+
* Mon Mar 16 2026 Steve Cossette <farchord@gmail.com> - 26.03.80-1
- 26.03.80
diff --git a/sources b/sources
index 8e19acc..9349fc5 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-SHA512 (kgpg-26.03.80.tar.xz) = a38acf8aa5048e8b1f7788ede653aefacf7fe2fb71c076895f89c1ed23da86d3cd879aea75b31277f56b250db286172ba331b6e15f6271dd662476abe3464460
+SHA512 (kgpg-26.04.0.tar.xz) = 51ec4590a2b301be311db2d5a2dabb1bc28dba70b21f4a91feb60b89a4f9e7f7f9eaa0b5e55d0318f4925e0633902f216280730f393bbb821a7ca3d685427ec2
reply other threads:[~2026-06-23 17:57 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=178223745627.1.885008608273069265.rpms-kgpg-839bdf9fe410@fedoraproject.org \
--to=farchord@gmail.com \
--cc=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