From: Prince213 <Prince213@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] proot: update to 5.3.1.
Date: Wed, 10 May 2023 15:56:05 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43832@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 486 bytes --]
There is a new pull request by Prince213 against master on the void-packages repository
https://github.com/Prince213/void-packages proot-5.3.1
https://github.com/void-linux/void-packages/pull/43832
proot: update to 5.3.1.
#### Testing the changes
- I tested the changes in this PR: **briefly**
#### Local build testing
- I built this PR locally for my native architecture, x86_64-glibc
A patch file from https://github.com/void-linux/void-packages/pull/43832.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-proot-5.3.1-43832.patch --]
[-- Type: text/x-diff, Size: 2220 bytes --]
From 586f499548d3c07bc8c7608fe3e9d863a8234727 Mon Sep 17 00:00:00 2001
From: Sizhe Zhao <prc.zhao@outlook.com>
Date: Wed, 10 May 2023 21:50:51 +0000
Subject: [PATCH] proot: update to 5.3.1.
---
.../patches/disable-seccomp-based-tracing.patch | 17 -----------------
srcpkgs/proot/template | 4 ++--
2 files changed, 2 insertions(+), 19 deletions(-)
delete mode 100644 srcpkgs/proot/patches/disable-seccomp-based-tracing.patch
diff --git a/srcpkgs/proot/patches/disable-seccomp-based-tracing.patch b/srcpkgs/proot/patches/disable-seccomp-based-tracing.patch
deleted file mode 100644
index 76cb4e048b6f..000000000000
--- a/srcpkgs/proot/patches/disable-seccomp-based-tracing.patch
+++ /dev/null
@@ -1,17 +0,0 @@
-# Based on a patch by Simon McVittie <smcv@debian.org>:
-# https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847292#16
-
-# Stops proot from segfaulting by disabling seccomp.
-# https://github.com/proot-me/proot/issues/106
-
---- a/src/GNUmakefile
-+++ b/src/GNUmakefile
-@@ -132,7 +132,7 @@ ifneq ($(and $(HAS_SWIG),$(HAS_PYTHON_CONFIG)),)
- CHECK_PYTHON_EXTENSION = /bin/echo -e "\#define HAVE_PYTHON_EXTENSION"
- endif
-
--CHECK_FEATURES = process_vm seccomp_filter
-+CHECK_FEATURES = process_vm
- CHECK_PROGRAMS = $(foreach feature,$(CHECK_FEATURES),.check_$(feature))
- CHECK_OBJECTS = $(foreach feature,$(CHECK_FEATURES),.check_$(feature).o)
- CHECK_RESULTS = $(foreach feature,$(CHECK_FEATURES),.check_$(feature).res)
diff --git a/srcpkgs/proot/template b/srcpkgs/proot/template
index 4cfa54265a0c..0e8f00f83f17 100644
--- a/srcpkgs/proot/template
+++ b/srcpkgs/proot/template
@@ -1,6 +1,6 @@
# Template file for 'proot'
pkgname=proot
-version=5.2.0
+version=5.3.1
revision=1
archs="x86_64* i686* aarch64* arm*"
build_wrksrc=src
@@ -14,7 +14,7 @@ maintainer="Piraty <mail@piraty.dev>"
license="GPL-2.0-or-later"
homepage="https://proot-me.github.io"
distfiles="https://github.com/proot-me/PRoot/archive/v${version}.tar.gz"
-checksum=1f25f9ef147bc96c9d7cd23218b7a7229f149757d91c832482b1a865b52aa62e
+checksum=966afe32bf9a9d0e80836a8874d4dd829c51750060d9e0f30d330b1ed7eec8c2
if [ "$XBPS_TARGET_LIBC" = "musl" ]; then
makedepends+=" musl-legacy-compat"
next reply other threads:[~2023-05-10 13:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-10 13:56 Prince213 [this message]
2023-05-13 14:08 ` [PR PATCH] [Closed]: " Prince213
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-43832@inbox.vuxu.org \
--to=prince213@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).