From: Philip Kaludercic <philipk@posteo.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: artscan@list.ru, 63757@debbugs.gnu.org,
Stefan Monnier <monnier@iro.umontreal.ca>
Subject: bug#63757: 29.0.91 order of package paths changed: random old versions of packages in load-path
Date: Wed, 07 Jun 2023 18:38:49 +0000 [thread overview]
Message-ID: <87pm67kthi.fsf@posteo.net> (raw)
In-Reply-To: <83sfb32sjw.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 07 Jun 2023 18:36:19 +0300")
[-- Attachment #1: Type: text/plain, Size: 1523 bytes --]
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Stefan Monnier <monnier@iro.umontreal.ca>
>> Cc: Eli Zaretskii <eliz@gnu.org>, artscan@list.ru, 63757@debbugs.gnu.org
>> Date: Mon, 05 Jun 2023 10:55:50 -0400
>>
>> > But in this case, if a regular package is upgraded, and a VC package
>> > weren't (even though the user might have written some patch they are
>> > relying on), it would be suddenly switch when starting up Emacs at some
>> > point.
>>
>> Yup. AFAIK both behaviors (staying with the VC package, and
>> switching to the non-VC package) can be "incorrect", depending on
>> the circumstances. So I don't see this as "a bug".
>>
>> Note also that in the session where we perform the install of the
>> upgraded package, the upgraded package will take precedence over the VC
>> package, so it's mildly more consistent to do the same at startup.
>>
>> If the user wants to keep using the older VC package, there's always to
>> option to use `package-pinned-packages` or to remove the non-VC package.
>>
>> If we want to do better, rather than forcing VC packages to the top we
>> should detect when the ordering between VC and non-VC packages changes
>> and emit a warning or prompt the user.
>
> So what's the bottom line here? Do we have an agreed-upon patch that
> should be installed on the emacs-29 branch? If so, can it be
> installed soon, please? Because I'd like to put out another Emacs 29
> pretest in a couple of days.
I think that Stefan's suggestion is the best way to go forward for now:
[-- Attachment #2: Type: text/plain, Size: 1912 bytes --]
From f47c9cdfa4f55a168246bd4fc19ad6c897e8906b Mon Sep 17 00:00:00 2001
From: Philip Kaludercic <philipk@posteo.net>
Date: Wed, 7 Jun 2023 20:37:13 +0200
Subject: [PATCH] ; Restore old behaviour of 'package--get-activatable-pkg'
* lisp/emacs-lisp/package.el (package--get-activatable-pkg): Do not
sort 'package-alist' to prefer VC packages. (Bug#63757)
---
lisp/emacs-lisp/package.el | 16 ++++------------
1 file changed, 4 insertions(+), 12 deletions(-)
diff --git a/lisp/emacs-lisp/package.el b/lisp/emacs-lisp/package.el
index 43368b59522..3e6acd9b388 100644
--- a/lisp/emacs-lisp/package.el
+++ b/lisp/emacs-lisp/package.el
@@ -924,22 +924,14 @@ package-activate-1
(defun package--get-activatable-pkg (pkg-name)
;; Is "activatable" a word?
- (let ((pkg-descs (sort (cdr (assq pkg-name package-alist))
- (lambda (p1 p2)
- (let ((v1 (package-desc-version p1))
- (v2 (package-desc-version p2)))
- (or
- ;; Prefer VC packages.
- (package-vc-p p1)
- (package-vc-p p2)
- ;; Prefer builtin packages.
- (package-disabled-p p1 v1)
- (not (package-disabled-p p2 v2))))))))
+ (let ((pkg-descs (cdr (assq pkg-name package-alist))))
;; Check if PACKAGE is available in `package-alist'.
(while
(when pkg-descs
(let ((available-version (package-desc-version (car pkg-descs))))
- (package-disabled-p pkg-name available-version)))
+ (or (package-disabled-p pkg-name available-version)
+ ;; Prefer a builtin package.
+ (package-built-in-p pkg-name available-version))))
(setq pkg-descs (cdr pkg-descs)))
(car pkg-descs)))
--
2.39.2
[-- Attachment #3: Type: text/plain, Size: 104 bytes --]
> If there's no agreement yet, can someone please spell out what is yet
> to be done here?
>
> Thanks.
next prev parent reply other threads:[~2023-06-07 18:38 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-27 16:30 bug#63757: 29.0.91 order of package paths changed: random old versions of packages in load-path Евгений Бойков via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-29 11:09 ` Eli Zaretskii
2023-05-29 14:24 ` Philip Kaludercic
2023-06-03 10:19 ` Philip Kaludercic
2023-06-03 10:38 ` Eli Zaretskii
2023-06-03 11:50 ` Евгений Бойков via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-03 12:53 ` Евгений Бойков via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-03 13:33 ` Евгений Бойков via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-03 14:06 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-04 4:46 ` Евгений Бойков via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-04 5:37 ` Евгений Бойков via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-04 5:41 ` Eli Zaretskii
2023-06-04 7:47 ` Philip Kaludercic
2023-06-04 8:03 ` Eli Zaretskii
2023-06-04 9:19 ` Philip Kaludercic
2023-06-04 10:14 ` Eli Zaretskii
2023-06-04 11:39 ` Philip Kaludercic
2023-06-04 12:08 ` Eli Zaretskii
2023-06-04 12:12 ` Philip Kaludercic
2023-06-04 12:19 ` Eli Zaretskii
2023-06-04 12:32 ` Philip Kaludercic
2023-06-04 12:46 ` Eli Zaretskii
2023-06-04 13:21 ` Philip Kaludercic
2023-06-04 14:03 ` Евгений Бойков via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-04 14:24 ` Philip Kaludercic
2023-06-04 14:30 ` Eli Zaretskii
2023-06-04 14:47 ` Евгений Бойков via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-04 14:55 ` Eli Zaretskii
2023-06-04 16:36 ` Евгений Бойков via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-04 15:12 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-04 15:20 ` Eli Zaretskii
2023-06-04 15:47 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-04 16:15 ` Philip Kaludercic
2023-06-04 16:30 ` Eli Zaretskii
2023-06-04 16:53 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-04 17:37 ` Philip Kaludercic
2023-06-04 18:32 ` Eli Zaretskii
2023-06-04 16:44 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-04 18:40 ` Philip Kaludercic
2023-06-04 19:38 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-05 7:55 ` Philip Kaludercic
2023-06-05 14:55 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-07 15:36 ` Eli Zaretskii
2023-06-07 18:38 ` Philip Kaludercic [this message]
2023-06-07 19:20 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-08 9:26 ` Eli Zaretskii
2023-06-04 16:28 ` Eli Zaretskii
2023-06-04 15:45 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-04 14:46 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-04 14:54 ` Eli Zaretskii
2023-06-04 15:03 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-04 12:14 ` Евгений Бойков via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-04 7:52 ` Евгений Бойков via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-04 8:06 ` Eli Zaretskii
2023-06-04 8:43 ` Евгений Бойков via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-04 8:54 ` Eli Zaretskii
2023-06-04 9:10 ` Ruijie Yu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-04 9:17 ` Philip Kaludercic
2023-06-04 10:16 ` Eli Zaretskii
2023-06-04 9:52 ` Евгений Бойков via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-04 14:54 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-29 13:25 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-29 15:44 ` Евгений Бойков via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-30 2:44 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-03 8:37 ` 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=87pm67kthi.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=63757@debbugs.gnu.org \
--cc=artscan@list.ru \
--cc=eliz@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).