From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Melpa crashed?
Date: Fri, 19 Feb 2016 11:49:44 -0500 [thread overview]
Message-ID: <87h9h4myqf.fsf@alphaville.usersys.redhat.com> (raw)
In-Reply-To: 944F3BA8-305B-4FEF-B7AF-0D261F149D00@gmail.com
童俊翔 <tongjunxiang@gmail.com> writes:
> Yes, my configuration is the same as https://github.com/melpa/melpa#usage
>
> For information about GNU Emacs and the GNU system, type C-h C-a.
> Opening TLS connection to ‘melpa.org’...
> Opening TLS connection with ‘gnutls-cli --x509cafile nil -p 443 melpa.org’...failed
> Opening TLS connection with ‘gnutls-cli --x509cafile nil -p 443 melpa.org --protocols ssl3’...failed
> Opening TLS connection with ‘openssl s_client -connect melpa.org:443 -no_ssl2 -ign_eof’...
> error in process sentinel: Error retrieving: http://elpa.gnu.org/packages/archive-contents (error connection-failed
> "failed with code 22
> " :host "elpa.gnu.org" :service 80)
> error in process sentinel: Error retrieving: http://elpa.gnu.org/packages/archive-contents (error connection-failed
> "failed with code 22
> " :host "elpa.gnu.org" :service 80)
> Opening TLS connection with ‘openssl s_client -connect melpa.org:443 -no_ssl2 -ign_eof’...done
> Opening TLS connection to ‘melpa.org’...done
> Mark saved where search started
> Package refresh done
> Install package ‘org-20160215’? (y or n) y
> Package menu: Operation started [Installing 1]
> Saving file /Users/mac/.emacs...
> Wrote /Users/mac/.emacs [2 times]
> Contacting host: elpa.gnu.org:80
> Parsing tar file...done
> cl--assertion-failed: Assertion failed: (or (= (buffer-size tar-data-buffer) (buffer-size)) (eq tar-data-swapped (>
> (buffer-size tar-data-buffer) (buffer-size))))
>
> It seems that I can not connect to elpa, although I can connect melpa, I still can not install packages through
> melpa.
>
> What’s the problem?
>
> On 19 Feb 2016, at 23:05, Josiah Schwab <jschwab@gmail.com> wrote:
>
> Hello Junxiang,
>
> On 19 February 2016 at 06:11 PST, 童俊翔 wrote:
>
> error in process filter: Error retrieving: https://melpa.org/packagesarchive-contents (error http 404) [2
> times]
What Josiah Schwab pointed out is that this URL
https://melpa.org/packagesarchive-contents
looks wrong. It should look like this:
https://melpa.org/packages/archive-contents
^---Note the slash
so his suggestion is that wherever you configured this, you probably typed
https://melpa.org/packages
but you should have typed
https://melpa.org/packages/
instead.
>
> What’s the problem?
>
> This suggests to me that you forgot the final slash in the MELPA URL.
>
> Does your configuration match https://github.com/melpa/melpa#usage ?
>
> Best,
> Josiah
--
Nick
next prev parent reply other threads:[~2016-02-19 16:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-19 14:11 Melpa crashed? 童俊翔
2016-02-19 15:05 ` Josiah Schwab
2016-02-19 16:29 ` 童俊翔
2016-02-19 16:49 ` Nick Dokos [this message]
2016-02-19 19:09 ` Will O'Brien
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h9h4myqf.fsf@alphaville.usersys.redhat.com \
--to=ndokos@gmail.com \
--cc=emacs-orgmode@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/org-mode.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).