all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefankangas@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>, 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: Thu, 2 Jan 2025 14:13:31 -0600	[thread overview]
Message-ID: <CADwFkm=LGZ6eEWvC2uXgGK9oqdWRsRxs6fSzay7g=kZAhkL4gA@mail.gmail.com> (raw)
In-Reply-To: <86ldxfte12.fsf@gnu.org>

Eli Zaretskii <eliz@gnu.org> writes:

>> 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?

Does everyone get write rights, though?  If not, how can you run
commands like "git clean -fxd" as a regular root after "make install"?





  reply	other threads:[~2025-01-02 20:13 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 [this message]
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
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

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

  git send-email \
    --in-reply-to='CADwFkm=LGZ6eEWvC2uXgGK9oqdWRsRxs6fSzay7g=kZAhkL4gA@mail.gmail.com' \
    --to=stefankangas@gmail.com \
    --cc=74400@debbugs.gnu.org \
    --cc=eliz@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 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.