From: sgn <sgn@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] keybase: use hand-generated tarball
Date: Wed, 08 Jul 2020 18:27:41 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-23472@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 670 bytes --]
There is a new pull request by sgn against master on the void-packages repository
https://github.com/sgn/void-packages keybase-signed-tarball
https://github.com/void-linux/void-packages/pull/23472
keybase: use hand-generated tarball
GitHub tarballs can be changed at anytime, which renders GitHub
auto-generated tarball invalid at sometime [1]
Use keybase manual generated tarball that is verified with their code
signing key [2]
[1] https://github.com/keybase/client/issues/10800
[2] https://keybase.io/docs/server_security/code_signing_key.asc
---
@Vaelatern
A patch file from https://github.com/void-linux/void-packages/pull/23472.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-keybase-signed-tarball-23472.patch --]
[-- Type: text/x-diff, Size: 1565 bytes --]
From 091c0413b75c6362520f39d34a17efa9e80ad339 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=C4=90o=C3=A0n=20Tr=E1=BA=A7n=20C=C3=B4ng=20Danh?=
<congdanhqx@gmail.com>
Date: Wed, 8 Jul 2020 23:14:48 +0700
Subject: [PATCH] keybase: use hand-generated tarball
GitHub tarballs can be changed at anytime, which renders GitHub
auto-generated tarball invalid at sometime [1]
Use keybase manual generated tarball that is verified with their code
signing key [2]
[1] https://github.com/keybase/client/issues/10800
[2] https://keybase.io/docs/server_security/code_signing_key.asc
---
srcpkgs/keybase/template | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/keybase/template b/srcpkgs/keybase/template
index be4e07e5ede..48214c6dc1a 100644
--- a/srcpkgs/keybase/template
+++ b/srcpkgs/keybase/template
@@ -2,7 +2,7 @@
pkgname=keybase
version=5.5.1
revision=1
-wrksrc="client-${version}"
+wrksrc="client-v${version}"
build_style=go
go_import_path="github.com/keybase/client"
go_package="${go_import_path}/go/keybase
@@ -16,8 +16,8 @@ short_desc="Client for keybase.io"
maintainer="Toyam Cox <Vaelatern@voidlinux.org>"
license="BSD-3-Clause"
homepage="https://keybase.io/"
-distfiles="https://github.com/keybase/client/archive/v${version}.tar.gz"
-checksum=a65dc4b62fc1299dd17da52ddd2484fa1dc1e7d2a4776c3a6e112ee020980b12
+distfiles="https://github.com/keybase/client/releases/download/v$version/keybase-v$version.tar.xz"
+checksum=a70abf39c68cef1effccf4b9b9b1ed2e9cad20ab4f6c4b66160b610eca1ec874
post_install() {
vlicense LICENSE
next reply other threads:[~2020-07-08 16:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-08 16:27 sgn [this message]
2020-07-08 18:06 ` Chocimier
2020-07-09 0:12 ` sgn
2020-07-11 19:35 ` Chocimier
2020-07-12 0:55 ` sgn
2020-07-12 2:38 ` q66
2020-07-13 18:23 ` [PR PATCH] [Merged]: " Vaelatern
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-23472@inbox.vuxu.org \
--to=sgn@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).