From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] void-release-keys: Add 20230628 signing key.
Date: Mon, 10 Jul 2023 20:25:44 +0200 [thread overview]
Message-ID: <20230710182544.cCmdwzF3A1W0P7hI0rptMlQtLD0YspHWbSTIpR2sCb4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-44951@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 375 bytes --]
There is an updated pull request by classabbyamp against master on the void-packages repository
https://github.com/the-maldridge/void-packages new-key
https://github.com/void-linux/void-packages/pull/44951
void-release-keys: Add 20230628 signing key.
Keys staged for image release.
A patch file from https://github.com/void-linux/void-packages/pull/44951.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-new-key-44951.patch --]
[-- Type: text/x-diff, Size: 1631 bytes --]
From 45cfaab7f901865f6c1d8e5a2dfe585cb08c4796 Mon Sep 17 00:00:00 2001
From: Michael Aldridge <maldridge@voidlinux.org>
Date: Sun, 9 Jul 2023 22:52:59 -0500
Subject: [PATCH] void-release-keys: Add 20230628 signing key.
keys are now placed in /usr/share/void-release-keys because they are no
longer specifically signify keys
---
srcpkgs/void-release-keys/files/void-release-20230628.pub | 2 ++
srcpkgs/void-release-keys/template | 4 ++--
2 files changed, 4 insertions(+), 2 deletions(-)
create mode 100644 srcpkgs/void-release-keys/files/void-release-20230628.pub
diff --git a/srcpkgs/void-release-keys/files/void-release-20230628.pub b/srcpkgs/void-release-keys/files/void-release-20230628.pub
new file mode 100644
index 000000000000..441d6a56ee02
--- /dev/null
+++ b/srcpkgs/void-release-keys/files/void-release-20230628.pub
@@ -0,0 +1,2 @@
+untrusted comment: minisign public key 5D7153E025EC26B6
+RWS2Juwl4FNxXe0NtAdYushNLM3GtJ6poGkZ0Up1P/9YLcCK4xlSWAfs
diff --git a/srcpkgs/void-release-keys/template b/srcpkgs/void-release-keys/template
index f1512322d2eb..b0ceac53fb92 100644
--- a/srcpkgs/void-release-keys/template
+++ b/srcpkgs/void-release-keys/template
@@ -1,7 +1,7 @@
# Template file for 'void-release-keys'
pkgname=void-release-keys
version=1
-revision=5
+revision=6
short_desc="Void Linux Release Keys"
maintainer="Void Release Engineering <releases@voidlinux.org>"
license="Public Domain"
@@ -9,6 +9,6 @@ homepage="http://www.voidlinux.org"
do_install() {
for _i in ${FILESDIR}/* ; do
- vinstall $_i 644 etc/signify/
+ vinstall $_i 644 usr/share/void-release-keys
done
}
next prev parent reply other threads:[~2023-07-10 18:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-10 3:53 [PR PATCH] " the-maldridge
2023-07-10 4:21 ` [PR PATCH] [Updated] " the-maldridge
2023-07-10 18:25 ` classabbyamp [this message]
2023-07-11 2:11 ` the-maldridge
2023-07-11 2:13 ` [PR PATCH] [Merged]: " the-maldridge
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=20230710182544.cCmdwzF3A1W0P7hI0rptMlQtLD0YspHWbSTIpR2sCb4@z \
--to=classabbyamp@users.noreply.github.com \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).