From: Philip Kaludercic <philipk@posteo.net>
To: Daniel Mendler <mail@daniel-mendler.de>
Cc: Eli Zaretskii <eliz@gnu.org>, 74556@debbugs.gnu.org
Subject: bug#74556: 30.0.92; Package upgrade can fail and results in deleted package
Date: Tue, 10 Dec 2024 20:12:15 +0000 [thread overview]
Message-ID: <87ldwnxppc.fsf@posteo.net> (raw)
In-Reply-To: <87zfl3h93m.fsf@daniel-mendler.de> (Daniel Mendler's message of "Tue, 10 Dec 2024 16:05:17 +0100")
[-- Attachment #1: Type: text/plain, Size: 1772 bytes --]
Daniel Mendler <mail@daniel-mendler.de> writes:
> Philip Kaludercic <philipk@posteo.net> writes:
>
>> Eli Zaretskii <eliz@gnu.org> writes:
>>
>>>> Cc: 74556@debbugs.gnu.org
>>>> From: Philip Kaludercic <philipk@posteo.net>
>>>> Date: Thu, 28 Nov 2024 11:34:51 +0000
>>>>
>>>> Philip Kaludercic <philipk@posteo.net> writes:
>>>>
>>>> [...]
>>>>
>>>> > It might make sense to try and "deactivate" a package before installing
>>>> > the new package. Looking into some second-try fallback for
>>>> > package-install to refresh the package index if a package was not found
>>>> > would also be a good idea ^^
>>>>
>>>> This might do it?
>>>
>>> Philip, please install this on the emacs-30 branch, unless you see any
>>> problems with the change. We'd like to make another pretest soon.
>>
>> Done. But we should keep the report open as there might be better
>> approaches to discuss in the future.
>
> Hello Philip,
>
> I just tried the modified `package-upgrade' function and it doesn't seem
> to work. It seems to break the upgrade procedure in an even worse way,
> at least in my setup. Now `package-install' is tried first with the
> package symbol, which will be a no-op, since the package is already
> installed. Afterwards the package is deleted and we always end up with
> no package. Probably `package-install' should also be called with a
> package descriptor of the new package version?
Right, my sincere apologies for that oversight. That being said, I
don't feel comfortable fixing this right now as I am short on time to
fix and test something like this on the "emacs-30" branch. My vote
would be to revert the commit and try to tackle the issue on the
"master" branch. An alternative I can propose that would be closer to
the original code might be
[-- Attachment #2: Type: text/plain, Size: 1450 bytes --]
diff --git a/lisp/emacs-lisp/package.el b/lisp/emacs-lisp/package.el
index fad0762e126..93b647edcea 100644
--- a/lisp/emacs-lisp/package.el
+++ b/lisp/emacs-lisp/package.el
@@ -2268,16 +2285,14 @@ package-upgrade
;; `pkg-desc' will be nil when the package is an "active built-in".
(if (and pkg-desc (package-vc-p pkg-desc))
(package-vc-upgrade pkg-desc)
- (package-install package
- ;; An active built-in has never been "selected"
- ;; before. Mark it as installed explicitly.
- (and pkg-desc 'dont-select))
- ;; We delete the old package via the descriptor after installing
- ;; the new package to avoid losing the package if there issues
- ;; during installation (Bug#74556).
- (when pkg-desc
- (cl-assert (package-desc-dir pkg-desc))
- (package-delete pkg-desc 'force 'dont-unselect)))))
+ (unwind-protect
+ (when pkg-desc
+ (cl-assert (package-desc-dir pkg-desc))
+ (package-delete pkg-desc 'force 'dont-unselect))
+ (package-install package
+ ;; An active built-in has never been "selected"
+ ;; before. Mark it as installed explicitly.
+ (and pkg-desc 'dont-select))))))
(defun package--upgradeable-packages (&optional include-builtins)
;; Initialize the package system to get the list of package
[-- Attachment #3: Type: text/plain, Size: 22 bytes --]
> Thanks!
>
> Daniel
next prev parent reply other threads:[~2024-12-10 20:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-27 11:37 bug#74556: 30.0.92; Package upgrade can fail and results in deleted package Daniel Mendler via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-28 11:11 ` Philip Kaludercic
2024-11-28 11:34 ` Philip Kaludercic
2024-12-07 12:29 ` Eli Zaretskii
2024-12-07 20:48 ` Philip Kaludercic
2024-12-10 15:05 ` Daniel Mendler via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-10 20:12 ` Philip Kaludercic [this message]
2024-12-10 20:24 ` Daniel Mendler via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-10 20:31 ` Philip Kaludercic
2024-12-11 3:30 ` Eli Zaretskii
2024-12-11 3:34 ` 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=87ldwnxppc.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=74556@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=mail@daniel-mendler.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).