Update

[mikev1963]

I get the following error when updating Omarchy:

looking for conflicting packages...
:: unable to satisfy dependency 'libaqumarine.so=13-64' required by hyprtoolkit
:: installing aquamarine (0.15.0-2) breaks dependency libaqumarine.so=13-64 required by hyprland
error: failed to prepare transaction (could not satisfy dependency)

Something went wrong during the update.

[Fail-Safe]

Thanks for the report — this looks like an ABI skew in Try Omarchy's package holds, not a bad Omarchy update script.

Hyprland is already on IgnorePkg (pinned patched build), but aquamarine was not. Arch Linux ARM has moved to aquamarine 0.15 (libaquamarine.so=14) while the pinned Hyprland still needs libaquamarine.so=13, so pacman aborts mid-transaction.

Opened a fix to hold aquamarine with Hyprland: #136

Workaround on an existing VM (until a new/reset image ships the hold):

# Edit both — Omarchy's update hook restores /etc/pacman.conf from the share copy
sudo sed -i 's/^IgnorePkg = linux-aarch64 linux-aarch64-headers hyprland$/IgnorePkg = linux-aarch64 linux-aarch64-headers hyprland aquamarine/' \
  /usr/share/try-omarchy/pacman.conf /etc/pacman.conf

Then retry the Omarchy update.

[mikev1963]

I now get the following errors after applying your workaround above.

Prune package cache
[sudo] password for omarchy:
==> no candidate packages found for pruning

gpg: key F0134EE680CAC571: "Omarchy pkgs@omarchy.org" not changed
gpg: Total number processed: 1
gpg: unchanged: 1
-> Locally signed 1 key.
==> Updating trust database...
gpg: next trustdb check due at 2026-10-21
:: Synchronizing package databases...
core is up to date
extra is up to date
alarm is up to date
aur is up to date
Error: 'omarchy-keyring' has no aarch64 build: not in the Arch Linux ARM repositories and not in the AUR
pub ed25519 2025-08-28 [SC]
40DFB630FF42BCFFB047046CF0134EE680CAC571
uid [ full ] Omarchy pkgs@omarchy.org
sub cv25519 2025-08-28 [E]

Update Arch signing keys
Keys are correct

Update system packages
:: Synchronizing package databases...
core is up to date
extra is up to date
alarm is up to date
aur is up to date
:: Starting full system upgrade...
resolving dependencies...
looking for conflicting packages...
:: unable to satisfy dependency 'libaquamarine.so=13-64' required by hyprtoolkit
:: installing aquamarine (0.15.0-2) breaks dependency 'libaquamarine.so=13-64' required by hyprland
error: failed to prepare transaction (could not satisfy dependencies)

Something went wrong during the update!

Please review the output above carefully, correct the error, and retry the update.

If you need assistance, get help from the community at https://omarchy.org/discord

[Fail-Safe]

Thanks for retrying — that log shows two separate issues, and the aquamarine conflict means the hold is not active in the pacman config the updater is using.

1. aquamarine is still being upgraded

IgnorePkg would skip that package entirely. Seeing installing aquamarine (0.15.0-2) means it is not on the live IgnorePkg line (sed likely did not match, or /etc/pacman.conf was overwritten again).

Please paste:

grep -n '^IgnorePkg' /etc/pacman.conf /usr/share/try-omarchy/pacman.conf
grep -E '^\[' /etc/pacman.conf

Robust manual hold (does not depend on an exact prior line):

for f in /usr/share/try-omarchy/pacman.conf /etc/pacman.conf; do
  sudo cp -a "$f" "$f.bak"
  if grep -q '^IgnorePkg = ' "$f"; then
    if ! grep -q '^IgnorePkg = .*\<aquamarine\>' "$f"; then
      sudo sed -i 's/^IgnorePkg = .*/& aquamarine/' "$f"
    fi
  else
    echo 'IgnorePkg line missing — stop and paste the grep output above' >&2
    exit 1
  fi
done
grep -n '^IgnorePkg' /usr/share/try-omarchy/pacman.conf /etc/pacman.conf

Edit both files: Omarchy’s pre-refresh hook copies the share file over /etc/pacman.conf on every update.

2. omarchy-keyring / missing repos

Your sync only lists core / extra / alarm / aur. A healthy Try Omarchy guest should also refresh [omarchy] and [try-omarchy]. Without [omarchy], omarchy-pkg-add omarchy-keyring cannot see the ARM keyring package and falls through to that “no aarch64 build” error.

If grep '^\[' does not show both [omarchy] and [try-omarchy], the ARM pacman restore did not stick — paste that output and we can narrow the next step (restore vs reset).

The aquamarine IgnorePkg fix in #136 only ships in new/reset guest images; existing VMs need the manual hold (or a reset onto a build that includes #136).

[mikev1963]

thanks. All fixed

[Fail-Safe]

Factory-build follow-up for the same aquamarine ABI break: #142

#136 holds aquamarine for already-built guests / updates. #142 also vendors aquamarine 0.14.0-2 so empty-root image builds can resolve again while ALA only publishes .so=14.