Skip to content

Should we switch to emacsmirror/nongnu_elpa rather than Savannah nongnu_elpa? #1189

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

Open
milanglacier opened this issue Apr 2, 2025 · 7 comments

Comments

@milanglacier
Copy link
Contributor

milanglacier commented Apr 2, 2025

Savannah has recently experienced accessibility issues frequently, possibly due to frequent DDoS attacks. Consequently, we are unable to update packages or bootstrap Emacs.

Should we consider switching from https://git.savannah.gnu.org/git/emacs/nongnu.git to https://github.com/emacsmirror/nongnu_elpa.git in the straight-use-recipes call when defining the nongnu-elpa recipe in bootstrap.el?

@milanglacier milanglacier changed the title Should we switch to emacsmirror/nongnu_elpa rather than Savannah GNU ELPA? Should we switch to emacsmirror/nongnu_elpa rather than Savannah nongnu_elpa? Apr 2, 2025
@raxod502
Copy link
Member

raxod502 commented Apr 3, 2025

That seems reasonable, yes, if there's reasonable data parity between the two. For backwards compatibility and customizability, I might suggest introducing a new recipe repository name and user option, same as for GNU ELPA:

straight.el/bootstrap.el

Lines 124 to 132 in b89c950

(if straight-recipes-gnu-elpa-use-mirror
(straight-use-recipes
'(gnu-elpa-mirror :type git :host github
:repo "emacs-straight/gnu-elpa-mirror"
:build nil))
(straight-use-recipes `(gnu-elpa :type git
:repo ,straight-recipes-gnu-elpa-url
:local-repo "elpa"
:build nil)))

@milanglacier
Copy link
Contributor Author

I think a new defcustom for this should work.

I think #1191 is also indirectly related to this issue.

@martenlienen
Copy link

Would it be an acceptable first solution to fix the typo in #1147 and merge that? Non-GNU ELPA has had a lot of problems in the past two weeks and then users could switch out the repo URL for https://github.com/emacsmirror/nongnu_elpa or some other mirror. Alternatively, accessing the repo over its git URL git://git.savannah.gnu.org/emacs/nongnu.git also seemed to work fine, compared to the http that is in the code right now.

@raxod502
Copy link
Member

Sure. As a local workaround, you can also use straight-recipe-overrides in your init-file before loading straight.el, which lets you override the recipe directly, no upstream changes needed.

@martenlienen
Copy link

The following snippet before the straight.el bootstrap section in my init.el works for me.

(custom-set-variables
 '(straight-recipe-overrides '((nil
                                (nongnu-elpa :type git
                                             :repo "https://github.com/emacsmirror/nongnu_elpa"
                                             :depth (full single-branch)
                                             :local-repo "nongnu-elpa"
                                             :build nil)
                                (ws-butler :type git
                                           :repo "https://github.com/emacsmirror/nongnu_elpa"
                                           :branch "elpa/ws-butler"
                                           :depth (full single-branch)
                                           :local-repo "ws-butler")))))

ws-butler is the package that triggered this for me in the first place when it moved to NonGNU ELPA.

SeanMooney added a commit to SeanMooney/emacs that referenced this issue May 2, 2025
This change applies
radian-software/straight.el#1189 (comment)
to workaround the load issues cause by bots scraping
savannah.nongnu.org
@SeanMooney
Copy link

The following snippet before the straight.el bootstrap section in my init.el works for me.

(custom-set-variables
'(straight-recipe-overrides '((nil
(nongnu-elpa :type git
:repo "https://github.com/emacsmirror/nongnu_elpa"
:depth (full single-branch)
:local-repo "nongnu-elpa"
:build nil)
(ws-butler :type git
:repo "https://github.com/emacsmirror/nongnu_elpa"
:branch "elpa/ws-butler"
:depth (full single-branch)
:local-repo "ws-butler")))))

ws-butler is the package that triggered this for me in the first place when it moved to NonGNU ELPA.

This works well for me too, thanks for the suggestion.

@milanglacier
Copy link
Contributor Author

milanglacier commented May 5, 2025

An alternative approach, particularly if you feel you are concerning about "overriding" something in your config.

(straight-use-package
 '(ws-butler :type git
             :repo "https://github.com/emacsmirror/nongnu_elpa"
             :branch "elpa/ws-butler"
             :depth (full single-branch)
             :local-repo "ws-butler"))

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

4 participants