unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Albinus via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Michael Heerdegen <michael_heerdegen@web.de>,
	74400-done@debbugs.gnu.org, stefankangas@gmail.com
Subject: bug#74400: 31.0.50; tramp-loaddefs.elc suddenly owned by root
Date: Sun, 05 Jan 2025 09:29:11 +0100	[thread overview]
Message-ID: <87o70l8y08.fsf@gmx.de> (raw)
In-Reply-To: <86ikqtagxi.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 05 Jan 2025 08:55:05 +0200")

Version: 30.1

Eli Zaretskii <eliz@gnu.org> writes:

Hi Eli,

> And I have a question: why not suggest to use 'make && sudo make
> install' to begin with, instead of showing a dangerous command and
> then explaining why not use it?  Like this:
>
>   If the directories where 'make install' installs files are not
>   writable by your user, you might prefer invoking 'make && sudo make
>   install' instead.  This first invokes 'make' to make sure all the
>   required files are rebuilt with your user's permissions and
>   ownership, and then installs them using the permissions of root.

Thanks a lot, I've installed this version. Pushed to emacs-30, and closing
the bug.

Best regards, Michael.





  reply	other threads:[~2025-01-05  8:29 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
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 [this message]
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=87o70l8y08.fsf@gmx.de \
    --to=bug-gnu-emacs@gnu.org \
    --cc=74400-done@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).