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

Fix a package that exists in both [omarchy] and the AUR updating from the wrong source

omarchyarchcachyosdesktoplaptop
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 mechanism holds. libalpm sync.c check_literal upgrades when the repo version is higher and downgrades only with enable_downgrade. yay's getPackageNamesBySource in high_level.go treats any installed name found in a sync DB as a repo package. AUR builds show Validated By : None on this machine, the awk|comm listing runs cleanly, and the ALPM guard (omarchy-update-pacman-guard) blocks only -S together with -u, so pacman -S omarchy/<pkg> is allowed. Issue #4577 supports the menu symptom and the edge-channel suggestion. The cause's numbers are wrong. They came from this workstation's stale sync DB, dated 2026-09-18, not from the live repo. Fetching https://pkgs.omarchy.org/stable/x86_64/omarchy.db on 2026-10-05 gave 254 packages, with visual-studio-code-bin 1.140.0-1 (equal to the AUR) and cursor-bin 3.23.12-1 (AUR 3.23.23-1). The claim that the repo 'lags the AUR on purpose' is unsupported: in #4577 an Omarchy maintainer says it is rebuilt from the AUR every 6 hours and treated the lag as a bug. Cause rewritten, and frequency lowered to occasional because the repo tracks the AUR closely. The fix gains a note that the edge channel swaps in omarchy-dev and omarchy-settings-dev (omarchy-channel-set).

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

Option 1 can downgrade the package. For editors and browsers that is usually harmless, but an application that migrated its profile or settings format in the newer version may not read it after a downgrade. Close the application first and back up its config directory if it matters.

Symptom

One of these, for a package such as visual-studio-code-bin, cursor-bin or localsend-bin:

  • You installed it from the AUR to get a newer version, and now every update prints

warning: visual-studio-code-bin: local (1.140.0-1) is newer than omarchy (1.138.0-1)

and the package never moves again, even when the AUR has a newer release. yay -Qua does not list it.

  • yay -S visual-studio-code-bin, or Install > AUR in the Omarchy menu on older releases, downloaded the [omarchy] build instead of the AUR one (issue #4577).
  • A package you built from the AUR was silently replaced by the [omarchy] build at the next omarchy update.

Cause

pacman does not record which repository or AUR build a package came from. It matches by name. If a sync repository carries a package with the same name, the installed copy is treated as that repo's package: pacman -Syu upgrades it from the repo when the repo version is higher, and only warns local (...) is newer than omarchy (...) when it is lower (libalpm check_literal, which downgrades only with -uu).

yay decides what is an AUR package the same way: any installed package whose name is found in a sync database is a repo package, and only the rest are foreign (yay getPackageNamesBySource). So yay -Sua, which is what omarchy update runs for AUR, skips it forever. A bare name in yay -S also resolves to the repo first.

The [omarchy] repository carries many AUR names (pacman -Slq omarchy | grep -E -- '-(bin|git)$'). An Omarchy maintainer says in issue #4577 that it is rebuilt from the AUR every 6 hours, so it is usually close behind the AUR rather than far behind on purpose. On 2026-10-05 the live stable repo had visual-studio-code-bin 1.140.0-1, the same as the AUR, and cursor-bin 3.23.12-1 against the AUR's 3.23.23-1. Any window where the AUR is ahead, or a local sync database that has not been refreshed, is enough for a hand-built AUR copy to be stranded or replaced.

Fix

List every installed package that was built locally (from the AUR) but has the same name as a repo package. Validated By: None marks a package installed from a local file:


LC_ALL=C pacman -Qi \
  | awk -F' *: ' '/^Name/{n=$2} /^Validated By/{if($2=="None") print n}' \
  | sort | comm -12 - <(pacman -Slq | sort -u)

For each one, compare the three versions:


pkg=visual-studio-code-bin
pacman -Q "$pkg"
pacman -Si "omarchy/$pkg" | grep -E '^(Repository|Version)'
yay -Si "aur/$pkg" | grep -E '^(Repository|Version)'

Option 1, recommended: go back to the [omarchy] build so omarchy update maintains it. An explicit -S of a repo package is allowed by the update guard and will downgrade if the repo is behind, printing warning: downgrading package ...:


sudo pacman -S "omarchy/$pkg"

If you need newer versions from Omarchy itself, the Update > Channel menu offers the edge channel (issue #4577). Switching channel rewrites /etc/pacman.conf and the mirrorlist, and edge also replaces omarchy and omarchy-settings with omarchy-dev and omarchy-settings-dev, so treat it as a change of release track and not a per-package setting.

Option 2: keep the AUR build and update it by hand, because no automatic path will:


yay -S "aur/$pkg"

The aur/ prefix forces the AUR. Expect omarchy update to swap it back to the [omarchy] build whenever the repo version passes yours.

Plain Arch with another unofficial repo (chaotic-aur, CachyOS) has the same shadowing. The listing above finds it there too.

Verify

pacman -Qi <pkg> | grep 'Validated By' shows a signature or checksum (repo build) for Option 1. The awk listing above prints nothing, or only the packages you chose to keep on Option 2. The is newer than omarchy warning no longer appears in /tmp/omarchy-update.log.

Sources

omarchy-repo-shadows-aur-package