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

IgnorePkg / IgnoreGroup / HoldPkg holding packages back and the partial upgrade that follows

archomarchyendeavouroscachyosmanjarodesktoplaptop
CORRECTED An auditor found the fix wrong or incomplete and rewrote it.
AUDIT NOTE

Checked /etc/pacman.conf on this Omarchy 4 workstation: HoldPkg = pacman glibc, no IgnorePkg, byte-identical to /usr/share/omarchy/default/pacman/pacman-stable.conf and to the quattro copy fetched via gh. pacman -Qo says it is owned by pacman 7.1.0.r9.g54d9411-2 and pacman -Qii pacman lists it as a backup file, so hand edits get a .pacnew rather than being overwritten on plain Arch. What was wrong, from source: the HoldPkg symptom block quoted a prompt pacman never prints. src/pacman/remove.c prints warning: %s is designated as a HoldPkg. then :: HoldPkg was found in target list. Do you want to continue? [y/N], and that is the only HoldPkg check in pacman (config->holdpkg is set in src/pacman/conf.c and read nowhere else), so it fires only in pacman -R, never when a -S transaction replaces a held package as the record and its step 6 claimed. alpm_error.c has no "user aborted the operation" string. Step 1's grep 'ignoring package upgrade' /var/log/pacman.log can never match: lib/libalpm/sync.c check_literal emits it via _alpm_log only, with no alpm_logaction, and pacman's cb_log writes that to stderr (compare add.c, whose directory permissions differ warning does call alpm_logaction and is the only [ALPM] warning: shape in this machine's pacman.log). pacman -Qu marks held packages [ignored] (src/pacman/query.c) and replaces it. The Omarchy note was wrong in the other direction: the skip question uses noyes in src/pacman/callback.c, so --noconfirm answers No, libalpm returns ALPM_ERR_UNSATISFIED_DEPS and pacman aborts. Read /usr/share/omarchy/bin/omarchy-update-system-pkgs and -when-conflicted here, which retry only on unresolvable package conflicts detected or exists in filesystem, so the update stops with the ERR trap banner from omarchy-update rather than "quietly doing less". Steps 4 and 5 ran bare sudo pacman -Syu, which /usr/bin/omarchy-update-pacman-guard aborts (both -S and -u present, no env var). A grep of /usr/share/omarchy/bin found no IgnorePkg or --ignore handling, so the Omarchy branch is the OMARCHY_ALLOW_DIRECT_PACMAN=1 bypass. Biggest Omarchy 4 miss: /usr/share/omarchy/bin/omarchy-refresh-pacman (called by omarchy-reinstall-pkgs) does cp -f $OMARCHY_PATH/default/pacman/pacman-$channel.conf /etc/pacman.conf, runs the pre-refresh-pacman hook, then pacman -Syyuu --noconfirm, so a hand-added IgnorePkg is dropped and the held package upgraded in one run. The shipped sample ~/.config/omarchy/hooks/pre-refresh-pacman.d/add-custom-repo.sample names extra IgnorePkg lines as its use case, and pacman.conf(5) confirms Include accepts general options, which is the drop-in route. omarchy-update itself never rewrites pacman.conf (the three migrations touching it use targeted sed). Confirmed on this machine: /tmp/omarchy-update.log is absent after reboot, paccache -rk2 in omarchy-update-pkg-prune. Not exercised: no IgnorePkg was set and no upgrade was run, so the abort path was traced in source and scripts, not observed.

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

Lifting a kernel or GPU hold and upgrading can pull in the exact regression you were avoiding: a kernel that breaks a DKMS module, an NVIDIA driver that breaks your display. Before removing such a hold, make sure linux-lts is installed and selectable in the boot menu and that the old packages are still in /var/cache/pacman/pkg so you can roll back (Omarchy runs paccache -rk2 before every update, so the previous version is normally still there). Never leave IgnorePkg = glibc or IgnorePkg = pacman in place: that guarantees a partial upgrade you cannot recover from with pacman itself. On Omarchy 4, omarchy refresh pacman and omarchy reinstall pkgs replace /etc/pacman.conf with the channel template and then upgrade everything, so a hold you set by hand is silently dropped and the held package is upgraded in that run unless a pre-refresh-pacman hook puts it back. If a partial upgrade has already broken things, never "fix" it by symlinking libfoo.so.5 to libfoo.so.6: soname bumps mean the ABI is incompatible, and you will get silent memory corruption instead of a clean error.

Symptom


warning: linux: ignoring package upgrade (7.1.9.arch1-1 => 7.1.10.arch1-1)
warning: nvidia-dkms: ignoring package upgrade (580.95.05-1 => 580.105.08-1)
:: The following package cannot be upgraded due to unresolvable dependencies:
      nvidia-utils
:: Do you want to skip the above package for this upgrade? [y/N]

Under --noconfirm (which is how omarchy update runs pacman) that question is answered No and the run stops with error: failed to prepare transaction (could not satisfy dependencies).

Or, when you try to remove a held package with pacman -R:


warning: pacman is designated as a HoldPkg.
:: HoldPkg was found in target list. Do you want to continue? [y/N]

Weeks later, on a system that reports itself fully updated: libfoo.so.6: cannot open shared object file: No such file or directory.

Cause

A package listed in IgnorePkg/IgnoreGroup in /etc/pacman.conf (or passed via --ignore) is skipped by -Syu, but pacman upgrades everything *around* it. That is a partial upgrade, which Arch does not support: the held package is now linked against library sonames that no longer exist. HoldPkg is a different mechanism: it is checked only by pacman -R (src/pacman/remove.c), which asks for confirmation before removing a listed package. It never blocks an upgrade, and a -S transaction that removes a held package through a conflict or a replacement does not prompt at all. Omarchy ships HoldPkg = pacman glibc in /etc/pacman.conf as a safety net and no IgnorePkg. Two Omarchy 4 specifics: the ignoring package upgrade warning is printed to stderr only and never written to /var/log/pacman.log, and omarchy refresh pacman (also run by omarchy reinstall pkgs) overwrites /etc/pacman.conf with the channel template from /usr/share/omarchy/default/pacman/, so a hold added by hand disappears and the held package is upgraded in that same run.

Fix

**1. Find out what is actually held:**


grep -nE '^\s*(IgnorePkg|IgnoreGroup|HoldPkg)' /etc/pacman.conf
grep -rnE '^\s*(IgnorePkg|IgnoreGroup)' /etc/pacman.d/ 2>/dev/null
pacman -Qu                          # held packages are listed with a trailing [ignored]

Do not grep /var/log/pacman.log for ignoring package upgrade: pacman prints that warning to stderr only and never logs it. On Omarchy the update transcript /tmp/omarchy-update.log has it, until the next reboot clears /tmp.

**2. Almost always the right move, remove the holds and take the whole upgrade:**


sudoedit /etc/pacman.conf          # delete or comment the IgnorePkg/IgnoreGroup lines
# Arch:
sudo pacman -Syu
# Omarchy:
omarchy update

/etc/pacman.conf is owned by the pacman package and is one of its backup files, so a pacman upgrade leaves your edits alone and writes a .pacnew instead.

**3. If you are holding a package for a real reason (a driver regression), pin the whole version-locked set, not one package, and treat it as temporary:**


# /etc/pacman.conf  [options]
IgnorePkg = linux linux-headers nvidia-dkms nvidia-utils lib32-nvidia-utils

On Omarchy 4 that line does not survive omarchy refresh pacman or omarchy reinstall pkgs: both copy /usr/share/omarchy/default/pacman/pacman-<channel>.conf over /etc/pacman.conf (the old file goes to /etc/pacman.conf.bak), then run pacman -Syyuu --noconfirm, which upgrades the package you were holding. The supported place to re-apply it is a pre-refresh-pacman hook, which runs between the copy and the upgrade. The shipped sample ~/.config/omarchy/hooks/pre-refresh-pacman.d/add-custom-repo.sample names extra IgnorePkg lines as a use case. A minimal hook:


#!/bin/bash
# ~/.config/omarchy/hooks/pre-refresh-pacman.d/ignorepkg   (any name without .sample)
grep -q '^IgnorePkg = linux ' /etc/pacman.conf ||
  sudo sed -i '0,/^\[core\]/s||IgnorePkg = linux linux-headers nvidia-dkms nvidia-utils lib32-nvidia-utils\n\n[core]|' /etc/pacman.conf

omarchy update itself does not rewrite /etc/pacman.conf, so a hold survives ordinary updates.

**4. To skip for exactly one transaction instead of permanently:**


# Arch:
sudo pacman -Syu --ignore linux,linux-headers
# Omarchy: the update guard blocks any pacman line carrying both -S and -u, and
# omarchy update has no --ignore passthrough, so bypass it for this one run.
# You skip the snapshot, keyring refresh and migrations that omarchy update does.
sudo env OMARCHY_ALLOW_DIRECT_PACMAN=1 pacman -Syu --ignore linux,linux-headers

**5. If you already created a partial upgrade and things are broken, complete it. Do not symlink libraries or reinstall pieces:**


sudo pacman -Syu                   # Arch
omarchy update                     # Omarchy
sudo pacman -S $(pacman -Qqn)      # last resort: reinstall every repo package
yay -S --rebuildall $(pacman -Qqm | tr '\n' ' ')   # rebuild AUR pkgs after soname bumps

**6. HoldPkg prompt:** it appears only in pacman -R. Answer y only when you are deliberately replacing the package in the same step. Never pacman -Rdd glibc.

**Omarchy note:** omarchy update runs pacman -Syu --noconfirm, so the "skip the above package" question is answered No and pacman aborts with failed to prepare transaction (could not satisfy dependencies). omarchy-update-system-pkgs-when-conflicted retries only for unresolvable package conflicts detected and exists in filesystem errors, so an IgnorePkg dependency clash ends the update with the red "Something went wrong during the update!" banner and nothing is upgraded. Fix the hold (step 2 or 3) and run omarchy update again. Afterwards:


pacman -Qu                          # anything still pending? [ignored] marks a hold

Verify

sudo pacman -Syu reports "there is nothing to do" with no ignoring package upgrade warnings. grep -nE '^\s*(IgnorePkg|IgnoreGroup)' /etc/pacman.conf returns nothing uncommented. pacman -Qu prints nothing.

Sources

ignorepkg-holdpkg-blocking-upgrade