Technically, keyring being installed first, in the same (full) procedure is irrelevant, as the signatures are checked before the new keyring is installed (bringing the new signature in).
Hmm yes so you mean we find a BUG on pacman?
On my test I do remove the package on the first run when pacman asks me if I want thatā¦ and on second round it do not bails out on the package but seems it updates the key on first round ?? interesting little issue ā¦
I see that it asks to fetch the key on first roundā¦ so seems it updates the key on that but as it was checking for the package before already it fail to install the package on first run but on second it can do itā¦
this makes it clear I think/hope 
?
2 Likes
Looks like the Arch wiki recommendation
sudo pacman -Sy archlinux-keyring
sudo pacman -Su
is generally useful to solve the libinih update issue in all cases that I have tested.
(Note that the double sudo pacman -Syu was my suggestion to Bryan, and at my first tests it seemed to fix it, but actually was not accurate. Sorry about that.)
Note also that the ISO has a separate hotfix.
4 Likes
This is not a joke! We all know pacman has NO bugs!!! 
Itās just the luck of a feature, or it is intentional
The server was down while I was answeringā¦
Indeed! Your video made it clearer to how odd it looksā¦
2 Likes
Even DT had trouble with libinih 
2 Likes
impossibleā¦ 
1 Like
He is human after all 
I donāt think this is an issue from the Appollo ISO. I have seen this many times happen.
had the same issue by arch linux.
2 Likes
Nah it is not an issue we do produce ā¦ for offline install it will simply be a regular update where user needs to do an update of the archlinux-keyring firstā¦
But for online installs we have a little issue on the ISO because we forget that pacstrap is using the keyring from the ISO while installing packages fresh from the reposā¦ so we need to update the archlinux keyring before we start pacstrap
6 Likes
That sounds like a good idea.
A post was merged into an existing topic: Apollo neo RC1 ISO testing