Stale Mirrors

[SpaceAgeHero]

Has this issue reoccured?
All databases are up to date for my installation for several days now again.

Edit: Looked at a few mirrors. All seem outdated since Feb 2nd:
aarch64/ 02-Feb-2025 02:23 -
armv7h/ 02-Feb-2025 02:23

[baslking]

If you want to have a guess when this happens, I suggest the Python release schedule for 3.13:
[url]https://peps.python.org/pep-0719/[/url]
Every time there is a major or bugfix update, I think we can expect the updates to hang for a while. The transition to 3.12 to 3.13 took over 2 weeks and it was already at 3.13.1 when that happened. The updates are stuck since the 3.13.2 bugfix release. There could well be more to it than that but I expect we will see a pause every 2 months with the Python bugfix, but then again correlation is not causation. so I may be totally wrong.

[shjim]

yawn!!

" patience is a virtue "

[SpaceAgeHero]

I've never experienced this over the last years. Why are Python updates blocking complete mirrors and why are "official" arch repos not affected?
I know this is all provided free of charge and voluntary, but what if new security issues arise that need to be patched urgently?

[bulletmark]

@baslking, any major update of Python, e.g. 3.12.7 -> 3.13.1 as we saw around 22-Jan require all packages that depend on Python to be rebuilt and pushed and given that is hundreds of packages that takes ages on ALARM. Minor updates, e.g. pending 3.13.1 -> 3.13.2 don't require any other packages to be rebuilt and only the Python package itself gets pushed so that is not the issue here.

[takaomag]

It seems all mirrors are out of sync.
For example, "https://ca.us.mirror.archlinuxarm.org/aarch64" is out of sync from 03-Feb-2025.

How is the current status?

[graysky]

Not out of sync. The toolchain has been updated and the rebuild in cranking away. When all package are rebuilt, mirror sync will be resumed.

[Musikolo]

Hi all,

It looks like mirrors stop syncing a month ago. I've checked a few of those and all of them stop syncing on Feb 1, Feb 2 or Feb 3. No more changes afterwards. You can search for "db.tar.gz" to locate the last the index DB update in your preferred mirror server. Sharing a few if you want to try yourself:
- Feb 1: [url]https://ca.us.mirror.archlinuxarm.org/aarch64/core/[/url]
- Feb 2: [url]http://dk.mirror.archlinuxarm.org/aarch64/core/?C=M&O=D[/url]
- Feb 3: [url]https://fl.us.mirror.archlinuxarm.org/aarch64/extra/[/url]

Apparently, this is the same issue that occurred back in Jan. Not sure what's going on and why this is occurring lately so frequently.

I hope permanent fix is found shortly.

Thanks.

[m3]

@Musikolo
Right before your post, @graysky explained what is happening.
What part of it you do not understand?
What permanent fix do you have in mind? Can you implement it yourself?

This is going on for ever, like a loop.
Python changes/upgrades require that hundreds of packages get rebuild. At the same time there is shortage of hands on deck.
Maintainers are going crazy working to deliver pkgs. And we can't stop complaining.

Mirror synchronization will be resumed. When?
When ALL PACKAGES are rebuilt. From the horse's mouth aka @graysky.

Patience is a virtue.
We need to stop bothering these people. Instead be thankful for their great work.

[baslking]

To add to what @m3 said, after a month of paused updates, you will still have a very difficult time finding a distribution anywhere close to being as up to date as this one!