-
Notifications
You must be signed in to change notification settings - Fork 41
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
"Failed to download `gnu' archive" error in silex/emacs:25-dev #56
Comments
Thanks for reporting! That's very weird, the dockerfiles between 25.3 and 26.3 are identical. My guess is more that you found some bug in 25.3. Can you confirm that it also happens with |
Sure, I will try the previous images and let you know. Right now I'm trying to track down the issue by running silex/emacs:25-dev here on my laptop. At first I thought it was some kind of reoccurrence of this problem: https://lists.gnu.org/archive/html/emacs-devel/2018-02/msg00142.html . But then I noticed the log output. Emacs is actually contacting http://elpa.gnu.org on port 80 |
From a quick look it look at https://travis-ci.org/Silex/docker-emacs/jobs/638014344 (https://api.travis-ci.org/v3/job/638014344/log.txt) we see this:
For 24.5 here's the output:
This is weird. I guess Emacs 25 does things differently. |
Well, one thing I'm doing differently is invoking Emacs with
so I'm going to have to copy the new gpg public key used to sign packages because my "elpa/gnupg" directory is someplace else. |
With the default value of Also, a bit of history in #52 |
Ok, so far my tests reveal that if I use the https URL of elpa 25.3 works, but 24.5 does not work?! this is getting weirder :-) |
Yes, I'm using the default There must be something about my Whereas if I run
as mentioned above, and without touching gnu's URL in the |
I've just about got this narrowed down, and I think my issue is just because the way I'm launching emacs I don't see the updated gpg keys for ELPA in |
Yep, that was it. In my CircleCI config I am setting What finally seems to fix this for me, is to perform the download like so:
Using a tip from usbarmory/usbarmory-debian-base_image#9 to disable ipv6 for better reliability. [Edit: correction, the key downloads are still laughably inconsistent. I guess I need to pick a specific keyserver rather than the round-robin DNS that seems to be happening here] |
Ok, done. For posterity the change I made was:
Again, I need to do this because I'm running |
Thanks for debugging. I still have weird issues. For example, by me
I need to figure out what is happening, maybe the key is not installed properly. |
Might be because you haven't called
Works for me with |
Ha, it never occured to me that Emacs was broken to the point that you had to call Everything works as expected then 🎉
The only thing I noticed is that I install Cask before fixing the ELPA key, and probably that Cask would be happier if it was the other way around. Also, I wonder if it'd be possible to import the ELPA key system-wide so you wouldn't have to import the key yourself? |
Interesting. Per the manual, what you're seeing is defined behavior for 40.1.1 Summary: Sequence of Actions at Startup Scanning through the rest of the document you can see there are various site configuration files and hooks that run during the startup sequence, you might be able to use them arrange to initialize those gpg keys. |
Thanks for the information. Emacs just ignore system wide gpg keys and looks in |
I'm running into this issue testing inf-clojure and I'm not sure how to take the lessons above and apply them. When running on silex/emacs:25-dev I have the following output: cask install
Loading package information... done
Package operations: 4 installs, 0 removals
- Installing [ 1/4] clojure-mode (5.11)... downloading
- Installing [ 1/4] clojure-mode (5.11)... done
- Installing [ 2/4] emacs (24.4)... already present
- Installing [ 3/4] assess (latest)... downloading
Dependency assess failed to install: Package `seq-2.14' is unavailable
Output:
nil
Makefile:8: recipe for target 'elpa' failed
make: *** [elpa] Error 255 But the exact same build steps work on silex/emacs:26-dev and silex/emacs:master-dev. If interesting or helpful, the circle-ci config file is https://github.com/clojure-emacs/inf-clojure/blob/master/.circleci/config.yml and the makefile is a simple one at https://github.com/clojure-emacs/inf-clojure/blob/master/Makefile. Also confusing why emacs has |
@dpsutton: can you run Anyway, if it's indeed the same issue I guess cask creates its own |
@Silex I tried with with --debug:
vs without debug
tried with --verbose
|
Ok I ran some checks: Emacs 25 contains seq version 2.3 You require version 2.14. You need to either lower the required version or install a newer version. Maybe @NicolasPetton or @DamienCassou can help, I don't use Cask so I don't know. |
That's incredibly awesome of you. Thank you so much. The only dependency i see is just a single |
You might need to add GNU ELPA to your list of package archives. I'm not using Cask so I can't be of much more help. |
I think my issue turns out to be unrelated. I figured it was the pkg key stuff but thanks to @Silex 's help I see it was inf-clojure requires assess requires m-buffer which requires seq 2.14. Thank you all for your help and sorry to have polluted this issue with something non-related |
I've recently updated the
elisp-lint
package and introduced a new dependency onpackage-lint
. I'm running this linter in CircleCI using Docker images defined here.However, tonight I'm seeing my CI tests running in the Emacs 25.3 container based
silex/emacs:25-dev
) are failing early with a missing dependencylet-alist
(which is needed forpackage-lint
). However exactly the same tests run successfully insilex/emacs:24-dev
,silex/emacs:26-dev
,silex/emacs:27-dev
andsilex/emacs:master-dev
. So I think there's something specific in the 25.3 image.let-alist
is distributed from elpa.gnu.org. I remember there was an update to the gpg key for that archive a while back. Is it possible the new key isn't installed properly for this one specific image?The text was updated successfully, but these errors were encountered: