OPINIONATED OMARCHY
TROUBLESHOOTING CORPUS
790
RECORDS
790
AUDITED
0
UNCHECKED
2388
SOURCES
LIVE
pacman-aur low common DISPUTE

Make yay (and omarchy update) actually update -git AUR packages

archomarchyendeavouroscachyosmanjaroauryaydesktoplaptop
CORRECTED An auditor found the fix wrong or incomplete and rewrote it. · checked against Omarchy omarchy 4.0.4-1 on 2026-10-05
AUDIT NOTE

The yay README confirms yay -Y --gendb, yay -Syu --devel and yay -Y --devel --save. The local yay --help for 13.0.1 lists --devel, --save, --gendb and --rebuild. The mechanism and fix are correct. The cause misquotes Omarchy's AUR step. On 4.0.4-1, /usr/share/omarchy/bin/omarchy-update-aur-pkgs runs yay -Sua --noconfirm --cleanafter --ignore gcc14,gcc14-libs, only when pacman -Qem finds foreign packages and the AUR is reachable. The cause is corrected to the exact command. The conclusion stands, because no --devel is passed and a saved devel setting in ~/.config/yay/config.json still applies to that call. Second audit confirmed the corrected text: Second pass on the record as corrected on 2026-10-04, whose finding (the cause now quotes the real AUR step) still holds. Confirmed on this machine: /usr/share/omarchy/bin/omarchy-update-aur-pkgs on 4.0.4-1 runs yay -Sua --noconfirm --cleanafter --ignore gcc14,gcc14-libs only when pacman -Qem finds foreign packages and the AUR is reachable, with no --devel. The quattro branch adds a --sudo wrapper and || exit 1 but still passes no --devel, so the cause holds on edge too. The yay README (Jguer/yay) documents yay -Y --gendb, yay -Syu --devel and yay -Y --devel --save, and its FAQ says packages not installed through yay are missing from the hash cache until --gendb. Local man yay (yay 13.0.1-1) documents --devel as a git ls-remote check against the hash recorded at install time, lists -Qu among the operations extended to the AUR (so yay -Qua is valid), and gives yay --devel --save as setting devel to true in the config. --rebuild and --cleanafter exist in yay --help. Nothing was executed against the AUR.

The cause above was rewritten on 2026-10-04 to match this note; the fix was corrected by the audit itself.

Symptom

An AUR package ending in -git (built from the latest upstream commit) never updates. yay -Syu and omarchy update both say there is nothing to do for it, while upstream has had dozens of commits and the installed version string is months old.

Cause

A -git package's version in the AUR only changes when the maintainer edits the PKGBUILD, which is rare, because the real version comes from upstream at build time. yay only checks upstream for new commits when development checking is enabled with --devel, and it compares against a commit hash it recorded when it installed the package. Without --devel, or for packages installed by makepkg or another helper (so yay has no recorded hash), yay never rebuilds them. On Omarchy 4 the AUR step of omarchy update (/usr/share/omarchy/bin/omarchy-update-aur-pkgs) runs yay -Sua --noconfirm --cleanafter --ignore gcc14,gcc14-libs when foreign packages are installed. It does not pass --devel, so -git packages are not rebuilt unless devel checking is saved in yay's config.

Fix

Record the current commit of every installed development package once, so yay has something to compare with:


yay -Y --gendb

Then turn development checking on permanently. This writes ~/.config/yay/config.json, so every later yay, yay -Syu and the yay -Sua inside omarchy update checks -git packages:


yay -Y --devel --save

Or check once without saving the setting:


yay -Sua --devel

Force one package to rebuild now regardless:


yay -S --rebuild <package>-git

Development checking runs git ls-remote against every -git package's upstream on each update, which adds time proportional to how many you have.

Verify

grep '"devel"' ~/.config/yay/config.json shows true, and yay -Qua lists a -git package after its upstream gets a new commit.

Sources

yay-git-packages-never-update-devel