From: Eli Zaretskii <eliz@gnu.org>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: michael_heerdegen@web.de, 74400@debbugs.gnu.org
Subject: bug#74400: 31.0.50; tramp-loaddefs.elc suddenly owned by root
Date: Tue, 19 Nov 2024 17:54:33 +0200 [thread overview]
Message-ID: <86ldxfte12.fsf@gnu.org> (raw)
In-Reply-To: <877c8z8u9r.fsf@gmx.de> (message from Michael Albinus on Tue, 19 Nov 2024 10:09:20 +0100)
> From: Michael Albinus <michael.albinus@gmx.de>
> Cc: michael_heerdegen@web.de, 74400-done@debbugs.gnu.org
> Date: Tue, 19 Nov 2024 10:09:20 +0100
>
> My example doesn't claim to be the recipe which happened to Michael. But
> it shows, that 'sudo make install' could create root-owned files in the
> build dir, and that's what this bug report is about.
>
> I don't know whether it is important enough to change something. But we
> should know (and document), that it could happen.
If it's important enough, maybe.
I think "make install" uses chmod to give everyone access to the file
because some files could be owned by root. If that works, why is the
ownership important?
prev parent reply other threads:[~2024-11-19 15:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-17 16:17 bug#74400: 31.0.50; tramp-loaddefs.elc suddenly owned by root Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-17 16:34 ` Eli Zaretskii
2024-11-17 17:02 ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-17 17:47 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-17 18:23 ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-18 1:56 ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-18 8:37 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-18 12:49 ` Eli Zaretskii
2024-11-19 9:09 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-19 15:54 ` Eli Zaretskii [this message]
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=86ldxfte12.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=74400@debbugs.gnu.org \
--cc=michael.albinus@gmx.de \
--cc=michael_heerdegen@web.de \
/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).