From: sgn <sgn@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] python3-grpcio: correct asm for boringssl
Date: Wed, 17 Feb 2021 14:27:33 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28816@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 555 bytes --]
There is a new pull request by sgn against master on the void-packages repository
https://github.com/sgn/void-packages python3-grpcio-fix-boringssl
https://github.com/void-linux/void-packages/pull/28816
python3-grpcio: correct asm for boringssl
The line was changed to:
if BUILD_WITH_BORING_SSL_ASM and not BUILD_WITH_SYSTEM_OPENSSL:
---
I'm not sure if we should switch to use system's {open,libre}ssl instead of bundled boringssl.
Also `re2-devel`.
A patch file from https://github.com/void-linux/void-packages/pull/28816.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-python3-grpcio-fix-boringssl-28816.patch --]
[-- Type: text/x-diff, Size: 1084 bytes --]
From 3f6f862e10d8eadb682ebb278db61189014082d9 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, 17 Feb 2021 20:24:28 +0700
Subject: [PATCH] python3-grpcio: correct asm for boringssl
The line was changed to:
if BUILD_WITH_BORING_SSL_ASM and not BUILD_WITH_SYSTEM_OPENSSL:
---
srcpkgs/python3-grpcio/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/python3-grpcio/template b/srcpkgs/python3-grpcio/template
index 76b88b3c8c4..749846e54cd 100644
--- a/srcpkgs/python3-grpcio/template
+++ b/srcpkgs/python3-grpcio/template
@@ -1,7 +1,7 @@
# Template file for 'python3-grpcio'
pkgname=python3-grpcio
version=1.35.0
-revision=1
+revision=2
archs="x86_64* i686* aarch64* armv[67]* ppc64le*"
wrksrc="${pkgname#*-}-${version}"
build_style=python3-module
@@ -47,5 +47,5 @@ post_patch() {
vsed -i setup.py \
-e "s/asm_key = .*/asm_key = '${asm_key}'/" \
- -e "s/if BUILD_WITH_BORING_SSL_ASM:/if False:/"
+ -e "s/if BUILD_WITH_BORING_SSL_ASM.*:/if False:/"
}
next reply other threads:[~2021-02-17 13:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-17 13:27 sgn [this message]
2021-02-17 14:53 ` ericonr
2021-02-17 14:53 ` ericonr
2021-02-17 15:27 ` ahesford
2021-02-17 15:32 ` [PR PATCH] [Closed]: " ahesford
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-28816@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).