all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Van Ly <van.ly@sdf.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Glenn Morris <rgm@gnu.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 15:06:18 +0000 (UTC)	[thread overview]
Message-ID: <34ea3c43-b527-eae2-9f21-404317ed6f3@SDF.ORG> (raw)
In-Reply-To: <83r18uhde4.fsf@gnu.org>

On Wed, 26 Jan 2022, Eli Zaretskii wrote:

>
> Isn't it customary to use sudo when installing stuff?
>

Taking GNU Screen as an example, the settings for the system go in 
/etc/screenrc, which would need chown to install in the first place, 
the user can install their settings in ~/.screenrc, without use of 
chown.

>> I guess they are to deal with tar defaulting to --same-owner for root.
>
> Most probably.
>
> In any case, I don't see any serious problem in the reported behavior,
> those are just warnings AFAIU.
>

I hesistated before reporting this bug, thinking my storage device 
had wornout and was spewing the error.  I got around to fscking then 
reported this.  A better looking log trace collapses and counts the 
repeating line and explains chown is not on the path is a help to 
know.  The autogen.sh script can detect chown is not on the path, 
right?

-- 
vl






  reply	other threads:[~2022-01-26 15:06 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 [this message]
2022-01-26 15:14         ` Eli Zaretskii
2022-01-26 17:51           ` Glenn Morris
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

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

  git send-email \
    --in-reply-to=34ea3c43-b527-eae2-9f21-404317ed6f3@SDF.ORG \
    --to=van.ly@sdf.org \
    --cc=53534@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=rgm@gnu.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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.