From: Roland Everaert <reveatwork@gmail.com>
To: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Unable to access the org-mode ELPA repo
Date: Fri, 4 Nov 2016 10:48:34 +0100 [thread overview]
Message-ID: <CACdPZ9JYjHP5hkncZex1f-6DS2j3Q=__vaXANpmNfjPK_imFgQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2618 bytes --]
Hi,
I am using emacs on a Windows 7 machine at work. I have decided, today, to
switch to ELPA to install org-mode (or any other package), but I am totally
unable to configure emacs properly to reach the repositories.
I have the following errors when emacs starts or when I ask emacs to
refresh the ELPA packages list:
"You can run the command ‘package-list-packages’ with M-x pa-l- RET
Mark saved where search started
error in process sentinel: Error retrieving:
http://elpa.gnu.org/packages/archive-contents (error connection-failed
"failed with code 10060
" :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 10060
" :host "elpa.gnu.org" :service 80)
Making completion list...
Package refresh done
error in process sentinel: Error retrieving:
http://orgmode.org/elpa/archive-contents (error connection-failed "failed
with code 10060
" :host "orgmode.org" :service 80)
error in process sentinel: Error retrieving:
http://orgmode.org/elpa/archive-contents (error connection-failed "failed
with code 10060
" :host "orgmode.org" :service 80)
read-number: Command attempted to use minibuffer while in minibuffer
Contacting host: elpa.gnu.org:80
Failed to download ‘gnu’ archive.
Contacting host: orgmode.org:80
Failed to download ‘org’ archive.
You can run the command ‘package-refresh-contents’ with M-x pa-r- RET
Failed to download ‘org’ archive."
Below is the configuration at the beginning of my .emacs init file:
"(eval-after-load "url"
'(progn
(require 'w32-registry)
(defadvice url-retrieve (before
w32-set-proxy-dynamically
activate)
"Before retrieving a URL, query the IE Proxy settings, and use them."
(let ((proxy (w32reg-get-ie-proxy-config)))
(setq url-using-proxy proxy
url-proxy-services proxy)))))
(require 'package)
(add-to-list 'package-archives '("org" . "http://orgmode.org/elpa/") t)
;; Added by Package.el. This must come before configurations of
;; installed packages. Don't delete this line. If you don't want it,
;; just comment it out by adding a semicolon to the start of the line.
;; You may delete these explanatory comments.
(package-initialize)"
As you can see in the error messages, the problem appears even with the
gnu archive. I suspect a proxy settings issue, but I don't know how to
diagnose the problem and find the solution.
Any help appreciated,
Roland.
[-- Attachment #2: Type: text/html, Size: 3564 bytes --]
reply other threads:[~2016-11-04 9:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CACdPZ9JYjHP5hkncZex1f-6DS2j3Q=__vaXANpmNfjPK_imFgQ@mail.gmail.com' \
--to=reveatwork@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).