Recently when I was trying to install EndeavourOS it keeps getting all kinds of pacstrap errors. A few days ago it was about a conflict between exfat-utils and exfatprogs, and now it becomes a libinih key problem?
I was trying to install the BSPWM community edition but I think any other version with online installation has the same problem. The only workaround for me right now is to use offline installation. I tried it on both a virtual machine (VirtualBox) and a physical machine, and I got the same results. Any idea what is causing this? (Also, this is my first post here so if I wrote anything inappropriate please be nice to me :P)
Update:
For anyone still not sure how to fix this, do the following steps:
before running calamares installer, open a terminal and run
sudo pacman -Sy archlinux-keyring
then you start the calamares as usual and install either online or offline
Note: yes you run the command outside the installer
Big thank to @pycrk for the solution and @Greyed for clarification
I’m using EndeavourOS_Apollo_22_1.iso. I tried an old one but it had the same issue. As I mentioned the offline installation works and the problem seems to be something related to the sources of pactrap.
i have updated my EOS installation now and become also an error. with the same package: libinih
the file is corrupted or invalid PGP Signature
Fehler: libinih: signature from "Maxime Gauduin <alucryd@gmail.com>" is marginal trust
:: Datei /var/cache/pacman/pkg/libinih-55-2-x86_64.pkg.tar.zst ist beschädigt (Ungültiges oder beschädigtes Paket (PGP-Signatur)).
I’d like to to know more about how this error occurred. Was it because the core library package “libinih” got updated and therefore got a new PGP-key, and the Installer is checking it against the outdated PGP-key that came with the ISO ? I’m just curious
I came here to post about this. I ran in to the same issue. Silly question - shouldn’t the installer update keys prior to downloading anything from the live environment? I get that this probably doesn’t happen often (keys being rotated my guess) but still, seems a sensible step to take.
yes the PGP Key from the package libinih was new and the archlinux-keyring(on my laptop) was outdated, when the system compares the keys, the system gets in trouble. I am not sure about the procedure in the ISO installer.
It is outside the installer. On the lower left corner of the live environment there are a few pinned icons to the task bar. One is for the terminal. Open the terminal and run:
sudo pacman -Sy archlinux-keyring
I would advise running the “Update Mirrors” task in the Welcome app before doing so. If you don’t you run the risk of hitting an unresponsive mirror.