From: Daniel Mendler via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: 74556@debbugs.gnu.org
Cc: Philip Kaludercic <philipk@posteo.net>
Subject: bug#74556: 30.0.92; Package upgrade can fail and results in deleted package
Date: Wed, 27 Nov 2024 12:37:17 +0100 [thread overview]
Message-ID: <87plmgq55e.fsf@daniel-mendler.de> (raw)
Package upgrade can fail when the package metadata is out of sync. The
upgrade process first deletes the package, tries to download the new
version. If the download fails for some reason (metadata out of sync or
the file not available), the upgrade aborts but the earlier package
deletion is not rolled back as one would expect for an upgrade
transaction. Ideally the download would be performed first such that the
upgrade process wouldn't lead to a missing package.
I just executed M-x package-upgrade-all. The following messages appeared
in the log:
Package ‘<package>-<old-version>’ deleted.
Contacting host: elpa.gnu.org:443
package--with-response-buffer-1:
https://elpa.gnu.org/devel/<pkgname>-<new-version>.tar: No Data
next reply other threads:[~2024-11-27 11:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-27 11:37 Daniel Mendler via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-11-28 11:11 ` bug#74556: 30.0.92; Package upgrade can fail and results in deleted package 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
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=87plmgq55e.fsf@daniel-mendler.de \
--to=bug-gnu-emacs@gnu.org \
--cc=74556@debbugs.gnu.org \
--cc=mail@daniel-mendler.de \
--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).