From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: xbps-src binary-bootstrap fails
Date: Sun, 26 Jan 2020 20:35:22 +0100 [thread overview]
Message-ID: <20200126193522.56tQfSOjnqoQdY3tXCQ_HZfjUxO8IRmqWJoYyInnBuo@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-18282@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1183 bytes --]
New comment by furryfixer on void-packages repository
https://github.com/void-linux/void-packages/issues/18282#issuecomment-578535035
Comment:
I accept the criticism. Although running as root is never recommended if avoidable, it has been tempting, and successful until recently, for me to use xbps-src within a larger Install script which MUST run with elevated privileges. This is of course easily changed. The current documentation for xbps-src has a mild statement that running it as root is not required. I had known this, but we should be aware that most "xbps-" commands require elevated privileges in common usage, so this could be a trap for the unwary.
So the maintainers have at least three basic options, if not more.
- (1) Ignore errors that only occur running as root, and place a stronger admonition/warning in the documentation.
- (2) Repair the xbps-src binary-bootstrap process to work for root. For now, this might be as simple as creating a "tmp" subdirectory.
- (3) Modifying xbps-src to prevent running as uid 0.
I think one of these should happen, but not up to me. Depending on your decision, you may close this when you feel appropriate.
next prev parent reply other threads:[~2020-01-26 19:35 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-13 5:01 [ISSUE] " voidlinux-github
2020-01-13 18:01 ` voidlinux-github
2020-01-13 20:01 ` voidlinux-github
2020-01-24 13:00 ` voidlinux-github
2020-01-24 16:58 ` voidlinux-github
2020-01-24 17:05 ` voidlinux-github
2020-01-24 17:08 ` voidlinux-github
2020-01-24 17:11 ` voidlinux-github
2020-01-24 17:11 ` voidlinux-github
2020-01-24 20:10 ` voidlinux-github
2020-01-24 20:12 ` voidlinux-github
2020-01-24 20:12 ` voidlinux-github
2020-01-26 0:13 ` voidlinux-github
2020-01-26 2:05 ` voidlinux-github
2020-01-26 2:12 ` voidlinux-github
2020-01-26 13:29 ` voidlinux-github
2020-01-26 13:38 ` voidlinux-github
2020-01-26 19:35 ` voidlinux-github [this message]
2020-02-17 4:45 ` [ISSUE] [CLOSED] " xtraeme
2020-02-17 4:45 ` xtraeme
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=20200126193522.56tQfSOjnqoQdY3tXCQ_HZfjUxO8IRmqWJoYyInnBuo@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).