From: joseph--- 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: adam.porter@47ap.net, philipk@posteo.net, 65666@debbugs.gnu.org
Subject: bug#65666: Lockfiles break package-vc-install-from-checkout
Date: Fri, 01 Sep 2023 06:18:39 +0000 [thread overview]
Message-ID: <d83a1c6ee1409f03a2be88a8c39bb89992f72f3e@breatheoutbreathe.in> (raw)
In-Reply-To: <83edjicui8.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 515 bytes --]
Eli Zaretskii <eliz@gnu.org> writes:
> We should not try to native-compile lock files, obviously. Some code
> naïvely uses "*.el" to find all the Lisp files; it should filter out
> lock files.
Please see attached patch.
> P.S. Please always say in what version of Emacs you see the problem
> you report. Bonus points for including all of the information
> collected by report-emacs-bug about your system and Emacs
> configurations.
Thanks - I'm on 29.0.92. I'll include that information next time.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-Don-t-native-compile-lock-files.patch --]
[-- Type: text/x-diff; name="0001-Don-t-native-compile-lock-files.patch", Size: 912 bytes --]
From 7b38b0bfd8c9da08daf734f6d0062d31dd54b947 Mon Sep 17 00:00:00 2001
From: Joseph Turner <joseph@breatheoutbreathe.in>
Date: Thu, 31 Aug 2023 23:11:53 -0700
Subject: [PATCH] Don't native compile lock files
* lisp/emacs-lisp/package.el (package--delete-directory):
Check that each file exists before compiling.
---
lisp/emacs-lisp/package.el | 1 +
1 file changed, 1 insertion(+)
diff --git a/lisp/emacs-lisp/package.el b/lisp/emacs-lisp/package.el
index e1172d69bf0..52a538e0627 100644
--- a/lisp/emacs-lisp/package.el
+++ b/lisp/emacs-lisp/package.el
@@ -2485,6 +2485,7 @@ compiled."
(when (featurep 'native-compile)
(cl-loop
for file in (directory-files-recursively dir "\\.el\\'")
+ when (file-exists-p file)
do (comp-clean-up-stale-eln (comp-el-to-eln-filename file))))
(if (file-symlink-p (directory-file-name dir))
(delete-file (directory-file-name dir))
--
2.41.0
next prev parent reply other threads:[~2023-09-01 6:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-31 21:47 bug#65666: Lockfiles break package-vc-install-from-checkout Joseph Turner via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-01 5:50 ` Eli Zaretskii
2023-09-01 6:18 ` joseph--- via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-09-01 12:52 ` Philip Kaludercic
2023-09-01 23:43 ` Joseph Turner via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-02 7:49 ` Eli Zaretskii
2023-09-02 17:15 ` Joseph Turner via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-02 17:21 ` Eli Zaretskii
2023-09-03 7:03 ` Philip Kaludercic
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=d83a1c6ee1409f03a2be88a8c39bb89992f72f3e@breatheoutbreathe.in \
--to=bug-gnu-emacs@gnu.org \
--cc=65666@debbugs.gnu.org \
--cc=adam.porter@47ap.net \
--cc=eliz@gnu.org \
--cc=joseph@breatheoutbreathe.in \
--cc=philipk@posteo.net \
/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).