From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] Revert "xbps-src/chroot.sh: sanitize PATH."
Date: Sun, 07 Jul 2019 09:05:19 +0200 [thread overview]
Message-ID: <20190707070519.JcGcGvulWyCXRLjblbnJNQhnKjVK5tmQSxKYeIOUlzs@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-12875@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 513 bytes --]
There is an updated pull request by Johnnynator against master on the void-packages repository
https://github.com/Johnnynator/void-packages revert-e0e48d6f6a3e3975bd867d5ae9485ebfbb76a687
https://github.com/void-linux/void-packages/pull/12875
Revert "xbps-src/chroot.sh: sanitize PATH."
This reverts commit e0e48d6f6a3e3975bd867d5ae9485ebfbb76a687.
This commit broke xbps-src on Distros with split bin sbin like Debian
A patch file from https://github.com/void-linux/void-packages/pull/12875.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-revert-e0e48d6f6a3e3975bd867d5ae9485ebfbb76a687-12875.patch --]
[-- Type: application/text/x-diff, Size: 995 bytes --]
From 2f7978dc4dd685144203bc15e17fa31bcc469cd3 Mon Sep 17 00:00:00 2001
From: John <johnz@posteo.net>
Date: Sun, 7 Jul 2019 09:04:12 +0200
Subject: [PATCH] xbps-src/chroot.sh: readd /usr/sbin to PATH
This partially reverts commit e0e48d6f6a3e3975bd867d5ae9485ebfbb76a687
This commit broke xbps-src on Distros with split bin sbin like Debian
---
common/xbps-src/shutils/chroot.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/common/xbps-src/shutils/chroot.sh b/common/xbps-src/shutils/chroot.sh
index 17ba9dde6ca..d0a28203516 100644
--- a/common/xbps-src/shutils/chroot.sh
+++ b/common/xbps-src/shutils/chroot.sh
@@ -26,7 +26,7 @@ XBPS_SRC_VERSION="$XBPS_SRC_VERSION"
. /etc/xbps/xbps-src.conf
-PATH=/void-packages:/usr/bin
+PATH=/void-packages:/usr/bin:/usr/sbin
exec env -i -- SHELL=/bin/sh PATH="\$PATH" DISTCC_HOSTS="\$XBPS_DISTCC_HOSTS" DISTCC_DIR="/host/distcc" \
${XBPS_ARCH+XBPS_ARCH=$XBPS_ARCH} ${XBPS_CHECK_PKGS+XBPS_CHECK_PKGS=$XBPS_CHECK_PKGS} \
next prev parent reply other threads:[~2019-07-07 7:05 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-07 6:58 [PR PATCH] " voidlinux-github
2019-07-07 6:59 ` voidlinux-github
2019-07-07 7:02 ` voidlinux-github
2019-07-07 7:04 ` voidlinux-github
2019-07-07 7:05 ` voidlinux-github [this message]
2019-07-07 7:05 ` [PR PATCH] [Updated] " voidlinux-github
2019-07-07 7:06 ` voidlinux-github
2019-07-07 7:07 ` voidlinux-github
2019-07-07 7:07 ` voidlinux-github
2019-07-07 7:07 ` voidlinux-github
2019-07-07 7:08 ` voidlinux-github
2019-07-07 7:08 ` voidlinux-github
2019-07-07 7:10 ` voidlinux-github
2019-07-07 7:11 ` voidlinux-github
2019-07-07 7:12 ` voidlinux-github
2019-07-07 7:13 ` voidlinux-github
2019-07-07 7:15 ` voidlinux-github
2019-07-07 7:17 ` [PR PATCH] [Updated] " voidlinux-github
2019-07-07 7:17 ` voidlinux-github
2019-07-07 7:19 ` voidlinux-github
2019-07-07 7:19 ` voidlinux-github
2019-07-07 7:21 ` voidlinux-github
2019-07-07 7:23 ` voidlinux-github
2019-07-07 7:23 ` voidlinux-github
2019-07-07 7:27 ` voidlinux-github
2019-07-07 7:28 ` [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=20190707070519.JcGcGvulWyCXRLjblbnJNQhnKjVK5tmQSxKYeIOUlzs@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).