From: dkwo <dkwo@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] umurmur: patch for openssl3
Date: Sun, 05 Feb 2023 19:08:12 +0100 [thread overview]
Message-ID: <20230205180812.-a1ErXoKTjSK-AuhMQiLTQwgU6zKQqdBTnqC6LYVPGo@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41991@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 469 bytes --]
There is an updated pull request by dkwo against master on the void-packages repository
https://github.com/dkwo/void-packages O3um
https://github.com/void-linux/void-packages/pull/41991
umurmur: patch for openssl3
- I tested the changes in this PR: no
- I built this PR locally for my native architecture, (x86_64-musl)
Add a patch to build with openssl3 #37681 @Duncaen
A patch file from https://github.com/void-linux/void-packages/pull/41991.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-O3um-41991.patch --]
[-- Type: text/x-diff, Size: 1494 bytes --]
From 01db4bbd576b4f649e93ca24c0af3816036bf6ba Mon Sep 17 00:00:00 2001
From: dkwo <nicolopiazzalunga@gmail.com>
Date: Tue, 31 Jan 2023 09:17:44 -0500
Subject: [PATCH] umurmur: patch for openssl3
---
.../umurmur/patches/remove-crypto-mem-ctrl.patch | 16 ++++++++++++++++
srcpkgs/umurmur/template | 2 +-
2 files changed, 17 insertions(+), 1 deletion(-)
create mode 100644 srcpkgs/umurmur/patches/remove-crypto-mem-ctrl.patch
diff --git a/srcpkgs/umurmur/patches/remove-crypto-mem-ctrl.patch b/srcpkgs/umurmur/patches/remove-crypto-mem-ctrl.patch
new file mode 100644
index 000000000000..17a9e5b3b0d2
--- /dev/null
+++ b/srcpkgs/umurmur/patches/remove-crypto-mem-ctrl.patch
@@ -0,0 +1,16 @@
+From: https://git.alpinelinux.org/aports/plain/main/umurmur/remove-crypto-mem-ctrl.patch
+
+fix build with OpenSSL 3
+
+--- umurmur-0.2.20.orig/src/ssli_openssl.c
++++ umurmur-0.2.20/src/ssli_openssl.c
+@@ -142,8 +142,6 @@
+
+ Log_info("Generating new server certificate.");
+
+- CRYPTO_mem_ctrl(CRYPTO_MEM_CHECK_ON);
+-
+ x509 = X509_new();
+ if (!x509)
+ goto err_out;
+
diff --git a/srcpkgs/umurmur/template b/srcpkgs/umurmur/template
index 11eb69f05b07..a5690d44de4b 100644
--- a/srcpkgs/umurmur/template
+++ b/srcpkgs/umurmur/template
@@ -1,7 +1,7 @@
# Template file for 'umurmur'
pkgname=umurmur
version=0.2.20
-revision=2
+revision=3
build_style=gnu-configure
configure_args="--enable-shmapi --with-ssl=openssl"
conf_files="/etc/umurmur/umurmur.conf"
next prev parent reply other threads:[~2023-02-05 18:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-31 14:21 [PR PATCH] " dkwo
2023-02-04 2:34 ` kruceter
2023-02-05 6:17 ` [PR REVIEW] " Vaelatern
2023-02-05 18:08 ` dkwo
2023-02-05 18:08 ` dkwo [this message]
2023-02-06 1:22 ` [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=20230205180812.-a1ErXoKTjSK-AuhMQiLTQwgU6zKQqdBTnqC6LYVPGo@z \
--to=dkwo@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).