-
Notifications
You must be signed in to change notification settings - Fork 675
Description
From the discord server where a user was first getting hung on ntp
Then hung on wkd...
we then got "past it" by doing the above. But then user would also get "corrupted package" only worked when he did the above, plus bellow:
Steps:
From the docs: https://archinstall.archlinux.page/help/known_issues.html#waiting-for-arch-linux-keyring-sync-archlinux-keyring-wkd-sync-to-complete-2679
Checks:
Latest ISO. (Released 1st of each month)
Latest Archinstall version (archinstall -v) should return same version as in releases page.
My second thought is that this can also be related to system time (Motherboard settings) and selected Timezone.
Anyways not really a big issue since its all already documented, just thought i'd post here and see if maybe someone has better insight.
-
why this happens in some cases (I personally have never had the issue just using
-key --init, making sure archinstall is latest ver, other contributor says its ISP related, I have no idea). -
if its a frequent issue (I think I've seen this pop up quite a bit) we could put in main FAQ or solve in code ?

