童俊翔 <tongjunxi...@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 <jsch...@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
