Github messages for voidlinux
 help / color / mirror / Atom feed
From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] New package: void-release-keys-1
Date: Mon, 20 Jan 2020 01:12:03 +0100	[thread overview]
Message-ID: <20200120001203.lK891d8_EAxHmBpfP_6_xgAz4ZJDv860Bo-U7qkXuYw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-18410@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 550 bytes --]

There is an updated pull request by the-maldridge against master on the void-packages repository

https://github.com/the-maldridge/void-packages release-keys
https://github.com/void-linux/void-packages/pull/18410

New package: void-release-keys-1
This commit adds the initial signify key and allows bootstrapping trust via the existing key infrastructure used by xbps.  The key should be validated against the master in keybase by either @Duncaen or @Gottox.

A patch file from https://github.com/void-linux/void-packages/pull/18410.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-release-keys-18410.patch --]
[-- Type: text/x-diff, Size: 1494 bytes --]

From 4ddb3638e47b6b57ea8f48a0e1ceca030aefbf97 Mon Sep 17 00:00:00 2001
From: Michael Aldridge <maldridge@VoidLinux.org>
Date: Sun, 19 Jan 2020 15:36:16 -0800
Subject: [PATCH] New package: void-release-keys-1

---
 .../files/void-release-20191109.pub               |  2 ++
 srcpkgs/void-release-keys/template                | 15 +++++++++++++++
 2 files changed, 17 insertions(+)
 create mode 100644 srcpkgs/void-release-keys/files/void-release-20191109.pub
 create mode 100644 srcpkgs/void-release-keys/template

diff --git a/srcpkgs/void-release-keys/files/void-release-20191109.pub b/srcpkgs/void-release-keys/files/void-release-20191109.pub
new file mode 100644
index 00000000000..bc1ce16dbf0
--- /dev/null
+++ b/srcpkgs/void-release-keys/files/void-release-20191109.pub
@@ -0,0 +1,2 @@
+untrusted comment: This key is only valid for releases with date 20191109.
+RWSFkPfJ0Jkg3EIuGjZoCn1/GSChINr/WHdJcdAh1s0d5P+C+ejdCC64
diff --git a/srcpkgs/void-release-keys/template b/srcpkgs/void-release-keys/template
new file mode 100644
index 00000000000..f9451a73b7b
--- /dev/null
+++ b/srcpkgs/void-release-keys/template
@@ -0,0 +1,15 @@
+# Template file for 'void-release-keys'
+pkgname=void-release-keys
+version=1
+revision=1
+archs=noarch
+short_desc="Void Linux Release Keys"
+maintainer="Void Release Engineering <releases@voidlinux.org>"
+license="Public domain"
+homepage="http://www.voidlinux.org"
+
+do_install() {
+	for _i in ${FILESDIR}/* ; do
+		vinstall $_i 644 etc/signify/
+	done
+}

  parent reply	other threads:[~2020-01-20  0:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-19 23:38 [PR PATCH] " voidlinux-github
2020-01-20  0:07 ` [PR PATCH] [Updated] " voidlinux-github
2020-01-20  0:12 ` voidlinux-github [this message]
2020-01-20  0:27 ` [PR PATCH] [Merged]: " voidlinux-github

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=20200120001203.lK891d8_EAxHmBpfP_6_xgAz4ZJDv860Bo-U7qkXuYw@z \
    --to=voidlinux-github@inbox.vuxu.org \
    --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).