public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Jon Stanley <jonstanley@gmail.com>
To: git-commits@fedoraproject.org
Subject: [rpms/keychecker] epel10: New version, initial import to EPEL7
Date: Fri, 21 Aug 2026 04:03:00 GMT	[thread overview]
Message-ID: <178728498015.1.4323275246452186753.rpms-keychecker-a049d34ba787@fedoraproject.org> (raw)

A new commit has been pushed.

Repo   : rpms/keychecker
Branch : epel10
Commit : a049d34ba787962d52b5ab0bdfb85a322b6d09e8
Author : Jon Stanley <jonstanley@gmail.com>
Date   : 2017-06-11T22:08:07+00:00
Stats  : +56/-0 in 3 file(s)
URL    : https://src.fedoraproject.org/rpms/keychecker/c/a049d34ba787962d52b5ab0bdfb85a322b6d09e8?branch=epel10

Log:
New version, initial import to EPEL7

---
diff --git a/.gitignore b/.gitignore
new file mode 100644
index 0000000..2948295
--- /dev/null
+++ b/.gitignore
@@ -0,0 +1 @@
+/v1.0.tar.gz

diff --git a/keychecker.spec b/keychecker.spec
new file mode 100644
index 0000000..e55ae33
--- /dev/null
+++ b/keychecker.spec
@@ -0,0 +1,54 @@
+Name:           keychecker
+Version:        1.0
+Release:        1%{?dist}
+Summary:        Generate list of installed packages sorted by GPG key
+
+Group:          Applications/System
+License:        GPLv2+
+URL:            https://github.com/jds2001/keychecker
+Source0:        https://github.com/jds2001/%{name}/archive/v%{version}.tar.gz
+BuildArch:      noarch
+%if 0%{rhel} <=6
+Requires:      python-argparse
+%endif
+
+%description
+Separately list rpm's based on the GPG key they were signed with
+
+%prep
+%setup -q
+
+
+%build
+
+%install
+rm -rf $RPM_BUILD_ROOT
+install -Dpm 0755 key_checker.py $RPM_BUILD_ROOT%{_bindir}/keychecker
+
+%clean
+rm -rf $RPM_BUILD_ROOT
+
+
+%files
+%defattr(-,root,root,-)
+%{_bindir}/keychecker
+%doc README LICENSE known_keys.txt
+
+%changelog
+* Sun Jun 11 2017 Jon Stanley <jonstanley@gmail.com> - 1.0-1
+- Python 3 compatibility (carlgeorge)
+- Migrate to argparse
+- Various minor cleanups
+- Remove BuildRoot tag as no longer needed
+
+* Sun Aug 16 2009 Jon Stanley <jonstanley@gmail.com> - 0.2-1
+- Add option for getting keys from a file
+
+* Tue Jul 28 2009 Jon Stanley <jonstanley@gmail.com> - 0.1-3
+- Fix spec typo
+
+* Sun Jul 26 2009 Jon Stanley <jonstanley@gmail.com> - 0.1-2
+- Review fixup (combine install lines)
+
+* Sun Jul 26 2009 Jon Stanley <jonstanley@gmail.com> - 0.1-1
+- Initial package

diff --git a/sources b/sources
index e69de29..9834dbf 100644
--- a/sources
+++ b/sources
@@ -0,0 +1 @@
+SHA512 (v1.0.tar.gz) = 65c2105bf40af48c16ece482aa801973be69ae8550af34d338171e6443a3340fe0d5d53971553d29bfa0dd80699828029646da365c7a86a76e901171c948a0bc

                 reply	other threads:[~2026-08-21  4:03 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=178728498015.1.4323275246452186753.rpms-keychecker-a049d34ba787@fedoraproject.org \
    --to=jonstanley@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