unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Van Ly <van.ly@sdf.org>, 53534@debbugs.gnu.org
Subject: bug#53534: 28.0.91; on netbsd 'gmake install' outputs 'find: chown: No such file or directory'
Date: Wed, 26 Jan 2022 12:51:51 -0500	[thread overview]
Message-ID: <27bkzye66g.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <83y232fs0y.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 26 Jan 2022 17:14:37 +0200")

Eli Zaretskii wrote:

> That won't help, because AFAIU when you use sudo, it changes your PATH
> accordingly.

It might, or it might not. It depends on how sudo is configured.

Alternative suggestions for fixing the various issues that exist here:

1) Don't use tar.
2) Use tar --no-same-owner (if tar doesn't have this option, then it
won't have the issue that chown seeks to fix).
3) Only run chown if UID = 0, and use chown root:root rather than the
current installuser logic, which seems broken (I notice now that most of
my emacs installations in /usr/local/share are owned by my user account
instead of root).





  reply	other threads:[~2022-01-26 17:51 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-25 23:03 bug#53534: 28.0.91; on netbsd 'gmake install' outputs 'find: chown: No such file or directory' Van Ly
2022-01-26  3:32 ` Eli Zaretskii
2022-01-26  4:26   ` Glenn Morris
2022-01-26 12:47     ` Eli Zaretskii
2022-01-26 15:06       ` Van Ly
2022-01-26 15:14         ` Eli Zaretskii
2022-01-26 17:51           ` Glenn Morris [this message]
2022-01-26 18:02             ` Glenn Morris
2022-01-27  2:22               ` Glenn Morris
2022-01-27  7:12                 ` Eli Zaretskii
2022-02-02 18:21                   ` Glenn Morris
2022-02-02 18:34                     ` Glenn Morris
2022-02-02 19:22                       ` Eli Zaretskii
2022-02-02 18:57                     ` Eli Zaretskii
2022-01-26 18:04           ` Van Ly

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=27bkzye66g.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=53534@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=van.ly@sdf.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).