-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot start spacemacs if elpa.gnu.org is down #5139
Comments
+1 |
Since I track develop, only diff --git a/core/core-configuration-layer.el b/core/core-configuration-layer.el
index 4b57943..218c385 100644
--- a/core/core-configuration-layer.el
+++ b/core/core-configuration-layer.el
@@ -132,7 +132,8 @@
(defvar configuration-layer--elpa-archives
'(("melpa" . "melpa.org/packages/")
("org" . "orgmode.org/elpa/")
- ("gnu" . "elpa.gnu.org/packages/"))
+ ;("gnu" . "elpa.gnu.org/packages/")
+ )
"List of ELPA archives required by Spacemacs.")
(defvar configuration-layer--package-archives-refreshed nil
|
I've figured out to start spacemacs correctly setting |
I wonder about the error |
@nixmaniack Thank you for the workaround, I was able to load spacemacs doing this @bmag I think it's a side effect of the failure to access elpa.gnu.org, since I don't see this message when commenting that repository. |
@axyz It would skip refreshing other package repos. |
Does this issue mean you normally can't start Spacemacs when you don't have network connectivity? |
@marten Unless there's some package missing, you should be able to start spacemacs normally without network. Reverting back to commit before pull( |
+1 |
sane temp fix 💬 syl20bnr @ February 19, 2016 4:38 PM
|
Seems we need more robustness here. I'll check to add an automatic rollback prompt when this happens. Thank you @a13ph for the link. |
Workaround did the trick so far. |
+1 |
I think the better workaround for now is to exclude the package that Spacemacs tries to download (which is uuidgen for most people). |
@TheBB In my case I had just asked spacemacs to install another package (ebib). Refreshing the configuration did not download it (probably because elpa.gnu.org was down), so I decided to restart spacemacs. |
Argh sorry guys about this, I hope we will be able to fix this mess "quickly". |
@syl20bnr I get this when trying to update packages:
|
BTW guys elpa.gnu.org is back up. EDIT: back down :( |
So when I have time to check the issue I cannot reproduce it. |
I mean it's cool that it works but it would have been easier to fix the issue if it was still down ;-) |
Actually I don't use https, maybe this is why I cannot reproduce it here. A fresh install (without https) does not block and gives me 10 errors:
|
Still having problem of not being able to connect to elpa On Fri, Feb 19, 2016 at 12:54 PM Eric Drechsel notifications@github.com
|
So it's impossible to set up a new installation currently? |
I wasn't able to. However, elpa appears to be back up now (It worked when I tried just now) |
Should be addressed in 0.105.11, hopefully next time it happens Spacemacs should load normally reporting just a few errors about uninstalled packages. Thank you for the feedback. |
Thank you! |
Thanks (By the way it also says not available for melpa but --insecure solved my all problems) |
Its happening again, 08:47 (EST) elpa.gnu.org is down |
This bit me today. It does eventually continue, but it hangs for a long long time. |
I just restarted Spacemacs and it will not finish loading with the following:
Looking at the
*Messages*
buffer I see this:Starting with
--debug-init
confirms the bug comes from elpa.gnu.org being down:The text was updated successfully, but these errors were encountered: