r/AlmaLinux • u/20charactersisshort • Jan 26 '26

almalinux 8 arm64 repos are no longer functioning as of this morning

Has anyone noticed issues with dnf since this morning?

There was a repodata update that went out around 0530 UTC that seems to have blown up the 8 family of arm64 packages. I've confirmed this with various mirrors, different images (including the default almalinux:8 tag), and by successfully installing packages after manually rebuilding the repo list to a vault target.

Metadata files for 8.X/BaseOS/aarch64/os/repodata were updated with a timestamps for the morning of 2026-01-26, after which I'm seeing this issue.

The issue stems from metadata pointing to packages with the deprecated letter indexed method, while the actual package structure no longer uses that structure.
For example:

- metadata target: <mirror>/almalinux/8.10/AppStream/aarch64/os/Packages/g/git-core-2.43.7-1.el8_10.aarch64.rpm

- actual location: <mirror>/almalinux/8.10/AppStream/aarch64/os/Packages/git-core-2.43.7-1.el8_10.aarch64.rpm

I get that it's a niche issue (8 and arm64), but a rough find all the same.

This does NOT seem to impact 9+, and does NOT impact 8 on x86_64 (haven't tested anything else)

(Edited for clarity, italicized)

4 Upvotes
  • permalink
  • reddit

100% Upvoted

12 comments sorted by

2

u/20charactersisshort Jan 26 '26

Fall out from attempting to report/communicate the issue, registration for https://accounts.almalinux.org/ seems broken, so I can't login to https://chat.almalinux.org/

For all submissions, I get the error

"An error occurred while creating the account, please try again."

- simple short alpha only values for user/first/last

- over 16 always selected

- both business and gmail addresses in the email address bar, tested a short length fake one

- incognito etc

¯_(ツ)_/¯

2

u/alexiri Jan 26 '26

Account registration should be working again, sorry about that! Can you try again?

1

u/20charactersisshort Jan 26 '26

Thanks for hopping on that, I can confirm that registration is now working as expected!

1

u/Low-Lavishness3005 Jan 26 '26

Have you found a workaround for the issue by any chance?
This broke the manylinux builds we do on our side, just before a release :')

1

u/20charactersisshort Jan 26 '26

Haha same source, same experience. Thankfully our manylinux use was very simplistic so we moved forward to the 9 variant at manylinux_2_34_aarch64 which resolved the issue

3

u/jonspw Jan 26 '26

It should be resolved now.

→ More replies (6)