From: Sebastian Wiesner <lunaryorn@gmail.com>
To: 14718@debbugs.gnu.org
Subject: bug#14718: 24.3.50; Endless loop in "package-read-all-archive-contents"
Date: Tue, 25 Jun 2013 22:19:43 +0200 [thread overview]
Message-ID: <m261x2x7s0.fsf@gmail.com> (raw)
If a package is contained in two or more archives,
"package-read-all-archive-contents" hangs in an endless loop. For
instance, in "emacs -Q":
ELISP> package-archives
(("gnu" . "http://elpa.gnu.org/packages/"))
ELISP> (package-refresh-contents)
nil
ELISP> (add-to-list 'package-archives
'("melpa" . "http://melpa.milkbox.net/packages/") t)
(("gnu" . "http://elpa.gnu.org/packages/")
("melpa" . "http://melpa.milkbox.net/packages/"))
ELISP> package-archives
(("gnu" . "http://elpa.gnu.org/packages/")
("melpa" . "http://melpa.milkbox.net/packages/"))
ELISP> (package-refresh-contents)
*** Eval error *** Quit during evaluation
The last invocation continues forever. "Quit during evaluation" is the
result of repeatedly pressing "C-g".
I inserted some "message" calls into functions called by
"package-refresh-contents", which indicate that the "while" loop at the
bottom of "package--add-to-archive-contents" is the root cause. This
loop seems to continue forever if "package--add-to-archive-contents" is
invoked with a "package" which is already contained in another archive.
Inserting a "(message "DEBUG: Looping for %s" package)" at the beginning
of the body of this loop repeats this message a few thousand times
before C-g succeeds in interrupting the evaluation. In my case, this
was the "yasnippet" package which is contained in GNU as well as in
MELPA.
Apparently the test of this loop is wrong, but since I do not understand
what the loop is supposed to do, I can't say how it is wrong.
next reply other threads:[~2013-06-25 20:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-25 20:19 Sebastian Wiesner [this message]
2013-06-26 0:45 ` bug#14718: 24.3.50; Endless loop in "package-read-all-archive-contents" Stefan Monnier
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=m261x2x7s0.fsf@gmail.com \
--to=lunaryorn@gmail.com \
--cc=14718@debbugs.gnu.org \
/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).