From: Eli Zaretskii <eliz@gnu.org>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: michael_heerdegen@web.de, 74400-done@debbugs.gnu.org
Subject: bug#74400: 31.0.50; tramp-loaddefs.elc suddenly owned by root
Date: Mon, 18 Nov 2024 14:49:27 +0200 [thread overview]
Message-ID: <86ed38vh9k.fsf@gnu.org> (raw)
In-Reply-To: <87y11h6iow.fsf@gmx.de> (message from Michael Albinus on Mon, 18 Nov 2024 09:37:51 +0100)
> From: Michael Albinus <michael.albinus@gmx.de>
> Cc: Eli Zaretskii <eliz@gnu.org>, 74400-done@debbugs.gnu.org
> Date: Mon, 18 Nov 2024 09:37:51 +0100
>
> Michael Heerdegen <michael_heerdegen@web.de> writes:
>
> Hi Michael,
>
> >> I try to recover everything I can find in my memory.
> >
> > No idea to be honest. Let's not waste time and assume I made nonsense.
> > I can reopen in case it comes back.
>
> Wait, I could reproduce the problem:
>
> --8<---------------cut here---------------start------------->8---
> # rm lisp/net/tramp-loaddefs.elc
> # sudo make install
> # ll lisp/net/*loaddefs*
> -rw-rw----+ 1 albinus albinus 110234 Nov 17 17:37 lisp/net/tramp-loaddefs.el
> -rw-r--r--+ 1 root root 122088 Nov 18 09:27 lisp/net/tramp-loaddefs.elc
> --8<---------------cut here---------------end--------------->8---
But note that here the time stamps of the two files are very diferent,
which seems to indicate that tramp-loaddefs.el was somehow
byte-compiled as part of "make install". Whereas in the OP, we saw a
different picture:
| /home/micha/software/emacs/lisp/net:
| drwxr-xr-x 2 micha micha 4,0K Nov 16 17:03 .
| drwxr-xr-x 28 micha micha 20K Nov 16 17:03 ..
| [...]
| -rw-rw-r-- 1 micha micha 108K Nov 15 17:01 tramp-loaddefs.el
| -rw-r--r-- 1 root root 120K Nov 15 17:01 tramp-loaddefs.elc
Look, ma: same time stamp. Which seems to indicate they were both
produced at the same time, so probably by the same command.
next prev parent reply other threads:[~2024-11-18 12:49 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 [this message]
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
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=86ed38vh9k.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=74400-done@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).