Housekeeping #3505
armv7h repo and archlinuxarm mirrors out-of-sync since 28th June
0%
Description
Hi
Not sure if this a related issue to https://labs.parabola.nu/issues/3497
It seems some pacakge have not received the update from upstream archarm after the 28th June, despite packages being updated there after this date and the relevant package for x86_64 updating in parabola repos in the same time period.
For example. Dino:
Upstream it was updated on the 29th June, https://archlinuxarm.org/packages/armv7h/dino with 0.4.2.3
however for the corresponding package in parabola extra https://www.parabola.nu/packages/extra/armv7h/dino/ is not updated and is still 0.4.2.2 whilst extra x86_64 shows as updated 0.4.2.3 updated shortly after its upstream as expected.
pacman -Syu shows no update either for this and others and pacman -Ss dino shows the older version.
The last package updates for armv7h where on the 28th June in parabola, but as mentioned above others like this one have had an update since upstream.
Just thought i'd mention the issue, incase its a similar issue to this https://labs.parabola.nu/issues/3497 and something got clogged.
Many Thanks in advance,
Ry
History
Updated by bill-auger 10 months ago
- Assignee set to bill-auger
- Status changed from open to in progress
it is not related to #3497 - the archarm repo mirrors really have not changed - i noticed this because the packages website shows icu 73; but mirrors still have only icu 72
i believe that this 'sync' file would be the tell-tale sign, when they start flowing again:
$ date --utc --date=@$(curl -s http://dk.mirror.archlinuxarm.org/armv7h/sync) Wed Jun 28 14:37:12 UTC 2023
i wrote to the archarm maintainer yesterday - ive not got answer yet
nothing is broken right?
Updated by bill-auger 10 months ago
- Subject changed from Armv7h arch arm repo upstream not in sync after 28th June to armv7h repo and archlinuxarm mirrors out-of-sync since 28th June
still no reply fro the archarm maintainer - the servers tracker does not have 'forwarded-upstream' state but that is essential the deal - i dont think there is anything we can do without some suggestion from the archarm maintainer
Updated by bill-auger 10 months ago
ok, some people in the IRC channel had some information - the problem is known to the maintainer and is being worked on - it is somehow related to the latest devtools and github rate-limiting downloads - arch is supposedly experiencing similar problems, though not as noticeable from the user perspective