AUR packages never update because omarchy update skipped the AUR step and still exited green
Re-audited against /usr/share/omarchy/bin/omarchy-update-aur-pkgs, omarchy-pkg-aur-accessible, omarchy-hook and omarchy-update as installed on this workstation (omarchy 4.0.2-1, kernel 7.1.9-arch1-2), and against the same files at omacom/omarchy@quattro, which are identical for the AUR pair. What held, confirmed on this machine: the probe is character for character the single curl -sf --connect-timeout 30 --retry 3 --retry-delay 3 -A "omarchy-update" "https://aur.archlinux.org/rpc/?v=5&type=info&arg=base" the record quotes, the red line is verbatim, /tmp/omarchy-update.log is the real transcript path (exec env OMARCHY_UPDATE_LOGGED=1 script -qefc "$script_command" "/tmp/omarchy-update.log"), omarchy-hook really runs ~/.config/omarchy/hooks/<name>.d/* skipping .sample, and omarchy-notification-send "headline" "description" is the real positional signature. yay -Sua carries no sysupgrade flag on pacman's own command line, so it does not trip omarchy-update-pacman-guard, whose hook /usr/share/libalpm/hooks/00-omarchy-update-guard.hook needs both a sync and a sysupgrade flag. Four things were wrong. First and worst, the fix's warn-stale-aur drop-in cannot work: omarchy-update runs omarchy-hook post-update on the line BEFORE omarchy-update-aur-pkgs (confirmed in the installed script and in quattro), so it reports the pre-update pending count on every run, and yay -Qua needs the AUR RPC to answer (yay(8): -S, -Si, -Sl, -Ss, -Su, -Sc, -Qu ... extended to support both AUR and repo packages), so during the outage the record is about it returns nothing and the warning never fires. It is broken in both directions. Second, the first-pass note called this a five-line script verified character for character and missed the actual command, which is yay -Sua --noconfirm --cleanafter --ignore gcc14,gcc14-libs. That --ignore predates 2026-02-02 (upstream commit 88784781 changed the line and the flag was already there), so it was present when the record was first audited. It makes the record's verify field false on any machine with those packages: both are real AUR packages (AUR RPC reports gcc14 and gcc14-libs at 14.3.1+r516+g5998566829ee-1, package base gcc14) and they stay pending forever by design, so a reader concludes the skip is happening when it is not. Third, the record names one silent-skip condition where there are four, and the one it omits that matters most is yay failing or being absent: the script has no set -e and its then-branch ends on a bare echo, so the exit status is 0 whatever yay did, and yay is not a dependency of omarchy (pacman -Qi omarchy Depends On has no yay, pacman -Qi yay shows Required By: None, and yay appears in /usr/share/omarchy/install/omarchy-base.packages only). Nothing under /usr/share/omarchy mentions paru, so a user who switched helpers loses the step silently. Fourth, step 3's hand-run yay -Sua --cleanafter dropped the --ignore and would start the gcc source build upstream avoids. Severity and frequency left alone: the extra paths widen the record but I have no measurement to justify moving either. NOT exercised: I ran no omarchy update, no yay command of any kind, and no pacman transaction, so every behavioural claim here is read from the shipping scripts and from yay(8) rather than observed. This machine has zero foreign packages (pacman -Qm is empty), so condition 4 is the one it would hit and I could not have tested the others here anyway.
Use yay -Sua (AUR only), never yay -Syu. The latter is a full system upgrade and will be aborted by the Omarchy pacman guard, or, if you bypass the guard, will skip migrations and post-update hooks. Keep --ignore gcc14,gcc14-libs when you run the step by hand: dropping it starts a source build of gcc from scratch, which is exactly why upstream excludes it. If a DKMS AUR package rebuilds here, it builds against the **installed** kernel headers, so if you have not rebooted since a kernel upgrade you can end up with a module built for a kernel you are not running. Reboot after DKMS rebuilds.
Symptom
omarchy update finishes successfully but AUR/foreign packages never move, for weeks or months. In the common case the only sign is one red line buried in the transcript:
AUR is unavailable (so skipping updates)
In the worse cases there is no line at all: the AUR step can also do nothing when yay is missing or its build fails, and when you have no explicitly installed foreign packages. Either way the run ends on the green success banner. Eventually a stale AUR package breaks against a newer library and the user reports it as a broken update, not as a skipped one.
Cause
omarchy-update-aur-pkgs is the entire AUR step, and it can decline to do anything in four different ways. All four leave omarchy update exiting 0 with its success banner, because the script sets no set -e and both branches end on a zero-status echo. On 4.0.2-1 and on quattro HEAD it is:
if pacman -Qem >/dev/null; then
if omarchy-pkg-aur-accessible; then
echo -e "\e[32m\nUpdate AUR packages\e[0m"
yay -Sua --noconfirm --cleanafter --ignore gcc14,gcc14-libs
echo
else
echo -e "\e[31m\nAUR is unavailable (so skipping updates)\e[0m"
echo
fi
fi
- **The reachability probe fails.**
omarchy-pkg-aur-accessibleis one request:
curl -sf --connect-timeout 30 --retry 3 --retry-delay 3 -A "omarchy-update" \
"https://aur.archlinux.org/rpc/?v=5&type=info&arg=base"
Any AUR outage, DNS failure, captive portal, corporate proxy, VPN or Tailscale split-DNS, or firewall rule blocking that single request makes the whole step a no-op. It probes aur.archlinux.org only, so yay may well be able to reach the package git repos fine. This is the only case that prints the red line.
- **
yayfails and nothing notices.** A failed build, a PGP key it cannot import, oryaynot being installed at all, all pass for success, because the trailingechosets the exit status.yayis **not** a dependency of theomarchypackage. It appears only as a name in/usr/share/omarchy/install/omarchy-base.packages, sopacman -R yayis not blocked, and nothing under/usr/share/omarchyever callsparu.
- **
gcc14andgcc14-libsare permanently excluded** by--ignore gcc14,gcc14-libs. Upstream does that on purpose, because they are source builds of gcc. It does mean an emptyyay -Quais the wrong success test on any machine that has them.
- **
pacman -Qemfinds nothing** and the step is skipped with no output whatever. That is usually right, but-Qemis explicitly installed foreign packages only, so a machine whose AUR packages are all dependency-installed (pacman -Qdm) never reaches the AUR step at all.
Fix
# 1. Reproduce the exact probe the updater uses
curl -sf --connect-timeout 30 -A omarchy-update \
"https://aur.archlinux.org/rpc/?v=5&type=info&arg=base" >/dev/null \
&& echo AUR-REACHABLE || echo AUR-BLOCKED
# 2. Read the last run's transcript. This is the reliable detector, because it
# records what the run DID rather than what is pending now.
grep -nE 'Update AUR packages|AUR is unavailable' /tmp/omarchy-update.log
# 3. What is installed from outside the repos, and what is pending?
pacman -Qm # ALL foreign packages, dependency-installed ones included
pacman -Qem # only the explicitly installed ones the updater gates on
yay -Qua # pending AUR updates. Needs the AUR reachable to answer.
# 4. Is yay even there? Nothing in Omarchy drives the AUR without it.
pacman -Q yay
# 5. If the probe fails but the AUR is reachable for you, do the step by hand.
# -Sua is AUR only and does not trip the Omarchy pacman guard. Keep
# upstream's --ignore, or you start a source build of gcc.
yay -Sua --cleanafter --ignore gcc14,gcc14-libs
# 6. Chase the network cause
resolvectl query aur.archlinux.org
curl -sI https://aur.archlinux.org | head -1
tailscale status # exit node or MagicDNS hijacking resolution?
cat /etc/resolv.conf
**Make the silence loud, but not with a post-update hook.** Two things stop that working. omarchy-update runs its steps in this order:
omarchy-update-system-pkgs
omarchy-migrate
omarchy-hook post-update
omarchy-update-aur-pkgs
so a post-update hook fires **before** the AUR step and can only see the state going in. And yay -Qua queries the AUR RPC itself, so during the very outage you want flagged it returns nothing and the warning never fires.
Check the transcript after the update instead:
mkdir -p ~/.local/bin
cat > ~/.local/bin/check-aur-skipped <<'EOF'
#!/bin/bash
# Did the last omarchy update actually run its AUR step?
log=/tmp/omarchy-update.log
[[ -r $log ]] || { echo "no update transcript at $log"; exit 0; }
if grep -q 'AUR is unavailable (so skipping updates)' "$log"; then
omarchy-notification-send "AUR step skipped" \
"The last omarchy update could not reach the AUR"
elif ! grep -q 'Update AUR packages' "$log"; then
omarchy-notification-send "AUR step never ran" \
"No explicitly installed foreign packages, or the step was not reached"
fi
exit 0
EOF
chmod +x ~/.local/bin/check-aur-skipped
Run check-aur-skipped once the update has finished. /tmp/omarchy-update.log is the live transcript of the run in progress, which is the other reason a hook cannot read it usefully.
Verify
Read the transcript, not the pending list:
grep -nE 'Update AUR packages|AUR is unavailable' /tmp/omarchy-update.log
A good run shows the green Update AUR packages heading and no AUR is unavailable (so skipping updates). **Neither** line means the step never ran at all, so then check pacman -Qm for foreign packages and pacman -Q yay.
Do not use an empty yay -Qua as the test. gcc14 and gcc14-libs sit on upstream's permanent --ignore list, so on a machine that has them they stay listed after every successful update, and yay -Qua cannot answer at all while the AUR is unreachable.
Sources
- https://raw.githubusercontent.com/basecamp/omarchy/quattro/bin/omarchy-update-aur-pkgs
- https://raw.githubusercontent.com/basecamp/omarchy/quattro/bin/omarchy-pkg-aur-accessible
- https://raw.githubusercontent.com/basecamp/omarchy/quattro/bin/omarchy-update
- https://raw.githubusercontent.com/basecamp/omarchy/quattro/docs/update-process.md
- https://raw.githubusercontent.com/omacom/omarchy/quattro/bin/omarchy-update-aur-pkgs
- https://raw.githubusercontent.com/omacom/omarchy/quattro/bin/omarchy-pkg-aur-accessible
- https://raw.githubusercontent.com/omacom/omarchy/quattro/bin/omarchy-update
- https://raw.githubusercontent.com/omacom/omarchy/quattro/bin/omarchy-hook
- https://github.com/omacom/omarchy/commit/88784781
- https://aur.archlinux.org/packages/gcc14