Fix 'error: target not found' for a package that exists
The four causes are sound, and Omarchy enabling [multilib] is confirmed locally. Two defects. First, the record's AUR example is visual-studio-code-bin, but on Omarchy 4 that package is in the [omarchy] pacman repository (pacman -Si visual-studio-code-bin reports Repository: omarchy, 1.138.0-1). So pacman installs it on Omarchy and the example sends the reader to the AUR for nothing. Second, cited issue #6191 does not show 'target not found'. It is an Omarchy 3.8.2 download 404 from stale metadata, closed after the reporter ran a bare sudo pacman -Sy, which is the partial-upgrade step this corpus forbids. The aarch64 claim actually comes from issue #8645 (open), which the cause names but the record did not cite. Fix and sources are corrected. Second audit confirmed the corrected text: Second pass on the record as corrected on 2026-10-04. Its two findings still hold: visual-studio-code-bin is in the [omarchy] repository (pacman -Si reports Repository: omarchy, 1.138.0-1), and the aarch64 claim comes from issue #8645, still open and titled 'Install menu offers x86_64-only packages on aarch64: every entry fails with target not found'. Confirmed locally: pacman-conf --repo-list prints core, extra, multilib, omarchy, so the claim that Omarchy enables multilib holds, and pacman -Si steam reports multilib. Forum thread 258910 is exactly the steam / pacman -Syy / enable multilib case. Every sync in the fix is a full upgrade, with omarchy update on Omarchy, and pacman -Fy syncs only the file database, so it is not a partial upgrade. No install was run.
Fixing it with sudo pacman -Sy <package> is a partial upgrade and can break shared libraries. Always sync and upgrade together.
Symptom
A package you can see on archlinux.org, the AUR website or in a guide will not install:
$ sudo pacman -S steam
error: target not found: steam
Re-running with sudo pacman -Syy changes nothing. Common with steam, lib32-* packages, AUR packages like visual-studio-code-bin, and packages that were renamed.
Cause
pacman only searches the repositories enabled in /etc/pacman.conf, using the database copies it last downloaded. Four different causes produce the same message. (1) The package is in the AUR, which pacman does not read at all. (2) It is in [multilib], which plain Arch ships disabled. (3) The local databases are stale, so they lack a package or version that was added after the last sync. (4) The name changed, was merged into another package, or does not exist for your architecture (Omarchy's install menu offers some x86_64-only packages on aarch64, upstream issue #8645).
Fix
Work out which cause applies:
pacman -Ss '^steam$' # in an enabled repo?
yay -Ss steam # in the AUR?
pacman-conf --repo-list # which repos are enabled
pacman -F libfoo.so # which package ships a file (after: sudo pacman -Fy)
**In the AUR.** Install with the helper instead of pacman. Omarchy 4 ships yay:
yay -S <package>
On Omarchy 4, check pacman -Si <package> first. The [omarchy] repository carries some packages that are AUR-only on plain Arch, visual-studio-code-bin among them, and those install with sudo pacman -S.
**In multilib, plain Arch.** Uncomment both lines in /etc/pacman.conf:
[multilib]
Include = /etc/pacman.d/mirrorlist
then sudo pacman -Syu followed by sudo pacman -S steam. Omarchy 4 already enables [multilib], so skip this there.
**Stale databases.** Sync and upgrade together, then install. Never pacman -Sy <pkg> or a bare pacman -Sy on its own:
omarchy update # Omarchy 4
sudo pacman -Syu # plain Arch
sudo pacman -S <package>
**Renamed, merged or wrong architecture.** Look the package up on archlinux.org or the AUR page, which states replacements, or search by description with pacman -Ss <keyword>. On aarch64, packages built only for x86_64 do not exist at all, and Omarchy's install menu still offers some of them (issue #8645).
Verify
pacman -Si <package> (repo) or yay -Si <package> (AUR) prints the package details, and the install proceeds.