Unable to install omarchy because of untrusted package signature

[iliyanMobisystems]

Last night when I was trying to install Omarchy via the script and the installation failed. That's a part of the log regarding the issue that occurred:

checking keyring...
downloading required keys...
:: Import PGP key F0134EE680CAC571, "Unknown Packager"? [Y/n] 
checking package integrity...
error: hyprshade: signature from "Omarchy <pkgs@omarchy.org>" is unknown trust
:: File /var/cache/pacman/pkg/hyprshade-4.0.0-1-any.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] error: aether: signature from "Omarchy <pkgs@omarchy.org>" is unknown trust

:: File /var/cache/pacman/pkg/aether-2.13.1-1-any.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] error: elephant: signature from "Omarchy <pkgs@omarchy.org>" is unknown trust

It looks like the package is not trusted, therefore the installation of it fails. As a I was looking for a solution I saw that in install-omarchy-on-cachyos.sh we're doing the following two things:

1. Adding omarchy as a source for packages with the following command on line 43:

# Add Omarchy repository to pacman.conf
echo -e "\n[omarchy]\nSigLevel = Optional TrustedOnly\nServer = https://pkgs.omarchy.org/\$arch" | sudo tee -a /etc/pacman.conf > /dev/null
sudo pacman -Syu

2. Removing the original setup of pacman.conf by Omarchy, line 69

# Remove pacman.sh from preflight/all.sh to prevent conflict with cachyos packages
sed -i '/run_logged \$OMARCHY_INSTALL\/preflight\/pacman\.sh/d' install/preflight/all.sh

If you take a look at the pacman.sh in Omarchy's repo we see that the SigLevel value for omarchy is Optional TrustAll while ours is Optional TrustedOnly. I changed it and tried again. The fix was working, although the installation later failed because of something regarding the nvim setup.

It may be a good idea for us to change the script in order to be consistent with the setup done by Omarchy

[GerritWanderer]

I was running into the same issue and solved it by adding the signed key manually to pacman:

curl -fsSLo omarchy.asc 'https://keys.openpgp.org/vks/v1/by-fingerprint/40DFB630FF42BCFFB047046CF0134EE680CAC571'
gpg --show-keys --with-fingerprint omarchy.asc
sudo pacman-key --add omarchy.asc
sudo pacman-key --lsign-key F0134EE680CAC571
sudo pacman -Sy --noconfirm omarchy/omarchy-keyring
sudo pacman -U /var/cache/pacman/pkg/omarchy-keyring-20251026-2-any.pkg.tar.zst

[HomeLabJunkie]

This also allowed me to progress through the install from new cachyos install this evening

[iliyanMobisystems]

I was running into the same issue and solved it by adding the signed key manually to pacman:

curl -fsSLo omarchy.asc 'https://keys.openpgp.org/vks/v1/by-fingerprint/40DFB630FF42BCFFB047046CF0134EE680CAC571'
gpg --show-keys --with-fingerprint omarchy.asc
sudo pacman-key --add omarchy.asc
sudo pacman-key --lsign-key F0134EE680CAC571
sudo pacman -Sy --noconfirm omarchy/omarchy-keyring
sudo pacman -U /var/cache/pacman/pkg/omarchy-keyring-20251026-2-any.pkg.tar.zst

I think that's the fix for this issue. Mine is more like a work around. I was also wondering, why do we have a different trust level for Omarchy's packages than the one Omarchy intended?

[GerritWanderer]

In the latest omarchy release (3.1.4) a migration was added, to add the signed key to both new and existing installations. So this should be resolved now?

basecamp/omarchy@0e5c22a
basecamp/omarchy@4bb626b

[HomeLabJunkie]

Tried a new install of cachyos and this script just now

[iliyanMobisystems]

In the latest omarchy release (3.1.4) a migration was added, to add the signed key to both new and existing installations. So this should be resolved now?

basecamp/omarchy@0e5c22a basecamp/omarchy@4bb626b

AFAIK the scripts inside the "migrations" folder are executed only when updating an existing install of Omarchy and the changes in basecamp/omarchy@0e5c22a, change the pacman.sh script which we're not running. Therefore none of these changes resolve our issue on new installations.

[iliyanMobisystems]

Tried a new install of cachyos and this script just now

You ran @GerritWanderer's script before running the install script, right?

[iliyanMobisystems]

I start to not like this part of the installation script:

sed -i '/run_logged \$OMARCHY_INSTALL\/preflight\/pacman\.sh/d' install/preflight/all.sh

If think we should leave the execution of pacman.sh, but remove the part where they're changing pacman.conf:

sudo cp -f ~/.local/share/omarchy/default/pacman/pacman.conf /etc/pacman.conf

[HomeLabJunkie]

Tried a new install of cachyos and this script just now

You ran @GerritWanderer's script before running the install script, right?

I installed cachyos, rebooted and then followed this.

Clone the repository

git clone https://github.com/mroboff/omarchy-on-cachyos.git

Navigate to the project directory

cd omarchy-on-cachyos/bin

Make the script executable

chmod +x install-omarchy-on-cachyos.sh

Run the installation script

./install-omarchy-on-cachyos.sh

after I posted the screenshot with all the errors. I once again ran the following

curl -fsSLo omarchy.asc 'https://keys.openpgp.org/vks/v1/by-fingerprint/40DFB630FF42BCFFB047046CF0134EE680CAC571'
gpg --show-keys --with-fingerprint omarchy.asc
sudo pacman-key --add omarchy.asc
sudo pacman-key --lsign-key F0134EE680CAC571
sudo pacman -Sy --noconfirm omarchy/omarchy-keyring
sudo pacman -U /var/cache/pacman/pkg/omarchy-keyring-20251026-2-any.pkg.tar.zst

Then ran ./install-omarchy-on-cachyos.sh again and it seems to have finished with no further errors. however some things in hyperland don't work. I'm going to try again but seems to be something amiss.

[iliyanMobisystems]

What features seem to miss?

[pedroadame]

I ran into this issue yesterday on an already installed system. It would be nice if we had a way to update, not only omarchy, but also omarchy-on-cachyos. I installed before the omarchy-updater was fixed due to the .git folder issue and I would like to fix that without a reinstall

[iliyanMobisystems]

I ran into this issue yesterday on an already installed system. It would be nice if we had a way to update, not only omarchy, but also omarchy-on-cachyos. I installed before the omarchy-updater was fixed due to the .git folder issue and I would like to fix that without a reinstall

What is this ".git folder issue" you're referring to?

[pedroadame]

What is this ".git folder issue" you're referring to?

It's #9, has been fixed but I prefer avoiding a reinstall, so a way update omarchy-on-cachyos without reinstalling would be pretty nice.

[tonyymacc]

Just in case it hasn't been addressed somewhere else yet, I was able to get the script working working with the latest version of Omarchy (v3.1.7) after making a small adjust to the portion of the script that adds the omarchy repo to the pacman config file which was to change "Optional TrustedOnly" to "Optional TrustAll".

echo -e "\n[omarchy]\nSigLevel = Optional TrustAll\nServer = https://pkgs.omarchy.org/\$arch" | sudo tee -a /etc/pacman.conf > /dev/null
sudo pacman -Syu

I believe this was the change that @iliyanMobisystems was referring to in the beginning of the thread, as it matches the original Omarchy config.

[AnbuBlackOpsTech]

I had to change the /etc/pacman.conf [omarchy] entries from TrustedAll or TrustedOnly to TrustAll in addition with changing

echo -e "\n[omarchy]\nSigLevel = Optional TrustAll\nServer = https://pkgs.omarchy.org/$arch" | sudo tee -a /etc/pacman.conf > /dev/null

In the .sh file