Fix yay or paru dying on a libalpm.so version mismatch
Checked on this Omarchy 4 workstation: yay 13.0.1-1 is installed from the [omarchy] repo (pacman -Si yay reports Repository: omarchy, pacman -Sl omarchy lists yay and yay-debug, and yay is line 147 of /usr/share/omarchy/install/omarchy-base.packages), paru is not installed, and pacman 7.1.0.r9.g54d9411-2 ships libalpm.so.16 and libalpm.so.16.0.1 plus the unversioned /usr/lib/libalpm.so. ldd /usr/bin/yay lists only libc: yay 12.6.0 (2026-06-07) switched to dyalpm, which dlopens libalpm.so.16 and falls back to libalpm.so (Jguer/dyalpm internal/lib/loader.go at v0.1.4, the version yay 13.0.1's go.mod pins), so the record's loader error cannot come from the yay Omarchy 4 ships. The error is real for yay 12.5.x and earlier and for paru, whose AUR PKGBUILD still depends on libalpm.so>=14. The cited issues 3877 and 3902 (both December 2025, Omarchy 3.2.3, yay 12.5.x, both closed) support the symptom and show it was Omarchy's own repo shipping a yay built against libalpm.so.15 while core moved to .16, which the cause did not say. alpm.rs issue 59 is about paru only, so 'a lag against alpm.rs' is the wrong cause for yay. The fix opened with sudo pacman -Syu, which the ALPM guard (/usr/bin/omarchy-update-pacman-guard, aborts on -S plus -u without OMARCHY_UPDATE_PACMAN=1 or OMARCHY_ALLOW_DIRECT_PACMAN=1) blocks on Omarchy 4. The original claim that omarchy-update aborts at 'Update AUR packages' was accepted here at first and is wrong: /usr/share/omarchy/bin/omarchy-update-aur-pkgs runs yay inside an if-body whose last command is echo, so the script exits 0 whatever yay returned and omarchy-update continues. Corrected 2026-09-07 after a sibling audit (aur-package-deleted-merged-or-renamed) read the script. The symptom now says the AUR step prints the error and is skipped over. The danger's claim that Omarchy replaces a hand-built yay on the next update is only true for the yay package name, and omarchy-reinstall-pkgs conflicts with yay-bin. The omarchy-pkgs yay PKGBUILD is byte-identical to the AUR one. Not exercised: I did not break libalpm or rebuild yay or paru here, and I did not test what yay 13 prints if libalpm.so.16 is absent.
A widely copied workaround is ln -s /usr/lib/libalpm.so.16 /usr/lib/libalpm.so.15. That makes the helper run against an ABI-incompatible library and can corrupt the pacman database when it writes to it. If you must use it to bootstrap, remove both symlinks immediately after rebuilding: sudo unlink /usr/lib/libalpm.so.15 && sudo unlink /usr/lib/libalpm.so.15.0.0. On Omarchy, a yay built from the AUR PKGBUILD has the same package name and version as the [omarchy] repo one, so the next repo version bump upgrades it in place. yay-bin does not get that treatment: it stays a foreign package, omarchy update hands it to yay -Sua, and omarchy-reinstall-pkgs fails on the yay versus yay-bin conflict because it runs pacman with --noconfirm.
Symptom
Right after a pacman upgrade, every AUR helper invocation dies:
yay: error while loading shared libraries: libalpm.so.15: cannot open shared object file: No such file or directory
(or libalpm.so.14 or libalpm.so.16, the number moves). paru shows the same. This is a yay 12.5.x or older, or a paru, problem: yay 12.6.0 and later, including the yay 13.0.1 Omarchy 4 ships, load libalpm at runtime and do not fail this way. On Omarchy, if any AUR package is installed (pacman -Qem prints something), the "Update AUR packages" step of omarchy update prints the loader error and the update carries on without touching the AUR packages, because omarchy-update-aur-pkgs ends with an echo and exits 0 whatever yay returned. With no AUR packages installed that step never runs yay, so the update completes and only direct yay use fails.
Cause
yay up to 12.5.x was linked at build time against a specific libalpm soname (cgo), and paru still is (its AUR PKGBUILD depends on libalpm.so>=14). When pacman bumps that soname, as pacman 7.1.0 did on 2025-12-13 by moving to libalpm.so=16-64, a helper built against the old one cannot start, and because it is the tool you would use to rebuild itself, you are stuck. For paru the wait was for the Rust alpm crate to support libalpm 16 (archlinux/alpm.rs issue 59). For yay the wait was for a rebuilt release. On Omarchy 3 in December 2025 the yay in Omarchy's own repo was still built against libalpm.so.15 while pacman came from Arch core with .16, which is what omacom/omarchy issues 3877 and 3902 record.
Since yay 12.6.0 (2026-06-07) yay no longer links libalpm at all. It loads libalpm.so.16 at runtime through dyalpm and falls back to the unversioned /usr/lib/libalpm.so that the pacman package always installs, so ldd /usr/bin/yay lists only libc. Omarchy 4 ships yay 13.0.1 from its [omarchy] repo, and that build cannot produce this loader error. If you see it on Omarchy 4, the machine is still running an older yay or you are running paru.
Fix
First confirm which helper and which build you have:
pacman -Qi yay | grep -E '^(Version|Packager)'
pacman -Ql pacman | grep libalpm.so
ldd /usr/bin/yay | grep alpm || echo "yay loads libalpm at runtime"
**Omarchy 4.** yay comes from the [omarchy] repo, not the AUR, and the current build loads libalpm at runtime. Bring the system current through the supported path, which also refreshes the repo's yay:
omarchy update
If yay is still an older build that ldd shows linked to a missing libalpm.so.N, reinstall the repo package (no -u, so the update guard does not fire):
sudo pacman -S yay
Only if the repo build is also broken, build the AUR yay package by hand. Do not use pacman -Syu here: the ALPM guard aborts it. Install the build tools with a plain -S after omarchy update has already synced the databases:
sudo pacman -S --needed git base-devel go
cd /tmp && rm -rf yay
git clone https://aur.archlinux.org/yay.git
cd yay
makepkg -si
Prefer yay over yay-bin on Omarchy so the package name matches the repo one. Then re-run the update:
omarchy update
**Plain Arch.** Rebuild the helper from the AUR with makepkg, which needs no AUR helper:
sudo pacman -Syu --needed git base-devel go
cd /tmp && rm -rf yay
git clone https://aur.archlinux.org/yay.git
cd yay
makepkg -si
Or skip compilation with the prebuilt package:
cd /tmp && rm -rf yay-bin
git clone https://aur.archlinux.org/yay-bin.git
cd yay-bin
makepkg -si
For paru substitute https://aur.archlinux.org/paru.git (or paru-bin.git). The paru PKGBUILD runs cargo update alpm alpm-utils during the build, so it picks up the crate release that matches the installed libalpm.
Verify
yay --version prints a version instead of the loader error, and yay -Sua runs.
Sources
- https://github.com/basecamp/omarchy/issues/3877
- https://github.com/basecamp/omarchy/issues/3902
- https://github.com/archlinux/alpm.rs/issues/59
- https://raw.githubusercontent.com/basecamp/omarchy/master/bin/omarchy-update-aur-pkgs
- https://github.com/omacom/omarchy/issues/3877
- https://github.com/omacom/omarchy/issues/3902
- https://github.com/basecamp/omarchy/blob/quattro/bin/omarchy-update-aur-pkgs
- https://github.com/omacom/omarchy-pkgs/blob/master/pkgbuilds/yay/PKGBUILD
- https://github.com/omacom/omarchy-pkgs/blob/master/README.md
- https://github.com/Jguer/yay/releases
- https://github.com/Jguer/yay/blob/next/go.mod
- https://github.com/Jguer/dyalpm/blob/v0.1.4/internal/lib/loader.go
- https://aur.archlinux.org/cgit/aur.git/plain/PKGBUILD?h=yay
- https://aur.archlinux.org/cgit/aur.git/plain/PKGBUILD?h=yay-bin
- https://aur.archlinux.org/cgit/aur.git/plain/PKGBUILD?h=paru
- https://archlinux.org/packages/core/x86_64/pacman/