From: Michael Heerdegen via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: 74400@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>,
Stefan Kangas <stefankangas@gmail.com>
Subject: bug#74400: 31.0.50; tramp-loaddefs.elc suddenly owned by root
Date: Sat, 04 Jan 2025 23:11:05 +0100 [thread overview]
Message-ID: <87y0zqtekm.fsf@web.de> (raw)
In-Reply-To: <871pxia302.fsf@gmx.de> (Michael Albinus's message of "Sat, 04 Jan 2025 18:43:41 +0100")
Michael Albinus <michael.albinus@gmx.de> writes:
> What about the appended patch?
This surely can't harm,yes. I dunno if this is what happened in my case
(my habit is "make + sudo make install"), but I don't know where to dig
or what could have happened either. Ok.
So let me have a look at your patch:
>
> diff --git a/INSTALL b/INSTALL
> index d2705d3a44d..a8c3cd5a8e6 100644
> --- a/INSTALL
> +++ b/INSTALL
> @@ -671,6 +671,13 @@ for its Lisp files by giving values for 'make' variables as part of
> the command. See the section below called 'MAKE VARIABLES' for more
> information on this.
>
> +If the directories, 'make install' copies the files to, are not writable
> +with your own permissions, you might prefer calling 'sudo make install'.
> +Note, that this command checks the completeness of all needed files; if
Something's weird about your commas (or your comma key). I would remove
all but the third (after the word "permissions") - Eli may be able to
help more.
> +there are missing files they will be generated by internal invocations
> +of 'make'. In order to avoid files with root ownership in your
> +installation directories, you should always call 'make; sudo make install'.
Do you really mean "installation directories"?
Thx,
Michael.
next prev parent reply other threads:[~2025-01-04 22:11 UTC|newest]
Thread overview: 26+ 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
2025-01-02 20:13 ` Stefan Kangas
2025-01-02 21:05 ` Eli Zaretskii
2025-01-02 21:20 ` Stefan Kangas
2025-01-03 7:55 ` Eli Zaretskii
2025-01-02 2:00 ` Stefan Kangas
2025-01-02 15:36 ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2025-01-02 15:40 ` Stefan Kangas
2025-01-02 15:41 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2025-01-02 17:14 ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2025-01-02 17:25 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2025-01-02 17:43 ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2025-01-04 17:43 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2025-01-04 22:11 ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2025-01-05 6:55 ` Eli Zaretskii
2025-01-05 8:29 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2025-01-05 8:21 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=87y0zqtekm.fsf@web.de \
--to=bug-gnu-emacs@gnu.org \
--cc=74400@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=michael.albinus@gmx.de \
--cc=michael_heerdegen@web.de \
--cc=stefankangas@gmail.com \
/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).