From: Tim Cross <theophilusx@gmail.com>
To: Emacs developers <emacs-devel@gnu.org>
Subject: ELPA Issues?
Date: Mon, 16 Apr 2012 18:30:03 +1000 [thread overview]
Message-ID: <CAC=50j8hEyej+ZPU_x5LJA+8YxBKH_TT3HrkpgD+npd7d=3e9g@mail.gmail.com> (raw)
Is there a problem with the ELPA archive site at present?
Emacs version form today ("107918
eggert@cs.ucla.edu-20120416011813-5owp5impbhuv3w02")
emacs -Q
m-x list-packages
shows package listing with message "Failed to download 'gnu' archive
However, if you are like me an often have debug on error enabled, you
get the backtrace
Debugger entered--Lisp error: (error "Trying to parse HTTP response
code in odd buffer: *http elpa.gnu.org:80*<2>")
signal(error ("Trying to parse HTTP response code in odd buffer:
*http elpa.gnu.org:80*<2>"))
error("Trying to parse HTTP response code in odd buffer: %s" " *http
elpa.gnu.org:80*<2>")
url-http-parse-response()
package-handle-response()
package--download-one-archive(("gnu" .
"http://elpa.gnu.org/packages/") "archive-contents")
#[nil "\30\302\"\207" [archive package--download-one-archive
"archive-contents"] 3]()
package-refresh-contents()
list-packages(nil)
call-interactively(list-packages t nil)
execute-extended-command(nil)
call-interactively(execute-extended-command nil nil)
It strikes me that this error message is not very helpful. It took a
bit of time before I was able to work out there was some issue with
downloading the archive, but even now I'm not clear on exactly
what/why there is an issue. Thought it might be worth a bug report,
but wanted to see what the status of the elpa archive site was as this
make a difference between a bug report concerning error
handling/reporting and a bug report of some deeper issue witht he
list-packages functionality.
Tim
--
Tim Cross
next reply other threads:[~2012-04-16 8:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-16 8:30 Tim Cross [this message]
2012-04-16 10:55 ` ELPA Issues? Chong Yidong
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAC=50j8hEyej+ZPU_x5LJA+8YxBKH_TT3HrkpgD+npd7d=3e9g@mail.gmail.com' \
--to=theophilusx@gmail.com \
--cc=emacs-devel@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.