Skip to content
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

[Bug/Support]: workaround for when savannah is down/unresponsive #407

Open
3 tasks done
mahmoodsh36 opened this issue Jan 19, 2025 · 2 comments
Open
3 tasks done

Comments

@mahmoodsh36
Copy link

Confirmation

  • I have checked the documentation (README, Wiki, docstrings, etc)
  • I am checking these without reading them.
  • I have searched previous issues to see if my question is a duplicate.

Elpaca Version

master

Operating System

linux

Description

i was trying to update my packages when i found out some of them were failing to build, but then realized savannah is returning 429 errors

Warning (elpaca): Unable to read GNU-devel ELPA package file: (error "https://git.savannah.gnu.org/cgit/emacs/elpa.git/plain/elpa-packages responded with status 429")

i reckon we could get around this by using mirrors and modifying the urls elpaca-menu-elpas to point to mirrors instead of savannah itself, but im not sure how to go about doing it, help is appreciated.
for reference, a related issue was open for doom/straight.el: doomemacs/doomemacs#7171.
thank you.

progfolio added a commit that referenced this issue Jan 19, 2025
This should (hopefully) be more stable than the cgit variant.
If not, the general refactor here should make it easier to configure the ELPAs
to point to different URLs for their metadata and package specs.

Related: #405 #406 #407 #408

elpaca-menu-elpa--recipes: remove caching logic
elpaca-menu-elpa--metadata: remove caching logic
elpaca-menu-elpa--index: determine "devel" status dynamically
elpaca-menu--elpa: change NAME to symbol; handle caching.
elpaca-menu-gnu-elpa, elpaca-menu-non-gnu-elpa: update calling convention
elpaca-menu-gnu-devel-elpa, elpaca-menu-non-gnu-devel-elpa: remove
elpaca-menu-functions: remove devel variants of GNU/NONGNU menu functions.
progfolio added a commit that referenced this issue Jan 19, 2025
This should (hopefully) be more stable than the cgit variant.
If not, the general refactor here should make it easier to configure the ELPAs
to point to different URLs for their metadata and package specs.

Related: #405 #406 #407 #408

elpaca-menu-elpa--recipes: remove caching logic
elpaca-menu-elpa--metadata: remove caching logic
elpaca-menu-elpa--index: determine "devel" status dynamically
elpaca-menu--elpa: change NAME to symbol; handle caching.
elpaca-menu-gnu-elpa, elpaca-menu-non-gnu-elpa: update calling convention
elpaca-menu-gnu-devel-elpa, elpaca-menu-non-gnu-devel-elpa: remove
elpaca-menu-functions: remove devel variants of GNU/NONGNU menu functions.
progfolio added a commit that referenced this issue Jan 19, 2025
This should (hopefully) be more stable than the cgit variant.
If not, the general refactor here should make it easier to configure the ELPAs
to point to different URLs for their metadata and package specs.

Related: #405 #406 #407 #408

elpaca-menu-elpa--recipes: remove caching logic
elpaca-menu-elpa--metadata: remove caching logic
elpaca-menu-elpa--index: determine "devel" status dynamically
elpaca-menu--elpa: change NAME to symbol; handle caching.
elpaca-menu-gnu-elpa, elpaca-menu-non-gnu-elpa: update calling convention
elpaca-menu-gnu-devel-elpa, elpaca-menu-non-gnu-devel-elpa: remove
elpaca-menu-functions: remove devel variants of GNU/NONGNU menu functions.
@progfolio
Copy link
Owner

Confirmation

  • I have checked the documentation (README, Wiki, docstrings, etc)
  • I am checking these without reading them.
  • I have searched previous issues to see if my question is a duplicate.

Elpaca Version

master

Operating System

linux

Description

i was trying to update my packages when i found out some of them were failing to build, but then realized savannah is returning 429 errors

Yes. They've temporarily disabled cgit browsing due to abuse.

i reckon we could get around this by using mirrors and modifying the urls elpaca-menu-elpas to point to mirrors instead of savannah itself, but im not sure how to go about doing it, help is appreciated.

In general, this is how the URLs can be changed for the ELPA package specs by a user.
Note this should be done before the menu is used for any lookups.
Otherwise an elpaca-update-menus would need to be run for the affected menus.

  (require 'elpaca-menu-elpa)
  (setf (alist-get 'packages-url (alist-get 'gnu elpaca-menu-elpas))
        "https://git.savannah.gnu.org/gitweb/?p=emacs/elpa.git;a=blob_plain;f=elpa-packages;hb=HEAD"
        (alist-get 'packages-url (alist-get 'nongnu elpaca-menu-elpas))
        "https://git.savannah.gnu.org/gitweb/?p=emacs/nongnu.git;a=blob_plain;f=elpa-packages;hb=HEAD"))

The mirrors would have to point at the package specs.
A workaround for the time being is to use the gitweb interface in the example above, which I've made the default on latest version of Elpaca.
No change should be necessary on your end after upgrading.
Testing is appreciated.

@deejayem
Copy link

The mirrors would have to point at the package specs. A workaround for the time being is to use the gitweb interface in the example above, which I've made the default on latest version of Elpaca. No change should be necessary on your end after upgrading. Testing is appreciated.

The issue has been resolved for me with the latest version.

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

No branches or pull requests

3 participants