Conflict and provider prompts during -Syu, and what happens when you answer wrong
Checked against pacman 7.1.0 source at tag v7.1.0 (src/pacman/callback.c, src/pacman/util.c, lib/libalpm/deps.c, lib/libalpm/alpm.h), the pacman(8) man page on this machine, /usr/share/omarchy/bin/omarchy-update, omarchy-update-system-pkgs, omarchy-update-system-pkgs-when-conflicted, omarchy-update-pacman-guard and omarchy-pkg-add, and the Arch package JSON for pipewire-jack, jack2 and pipewire-media-session. What held: under --noconfirm question() returns its preset, the conflict question uses noyes() so the preset is No and the transaction aborts with unresolvable package conflicts detected, which is exactly what the Omarchy handler greps for, and both quoted Omarchy strings are verbatim. The handler re-runs pacman without --noconfirm only when stdin and stderr are terminals and OMARCHY_UPDATE_UNATTENDED is unset. pipewire-jack 1:1.6.8-1 provides jack and the three libjack sonames and conflicts jack, jack2 and pipewire-jack-client. pacman-contrib is in omarchy-base.packages and installed here. What was wrong: the record treats the provider prompt and the conflict prompt as the same failure, and they are not. select_question() under --noconfirm returns the default 1, so inside omarchy update (and omarchy-pkg-add, which runs pacman -S --noconfirm --needed) a provider question is answered silently with the first provider in repo order then alphabetical order (jack2 sorts before pipewire-jack), nothing aborts, and the Omarchy conflict handler never sees it. deps.c also returns early without asking when a provider is already installed, which is why this prompt is rare on an installed desktop. The Replace X with Y? question uses yesno(), so it defaults to Yes under --noconfirm and is not a conflict at all. pacman(8) documents --noconfirm and --confirm but has no --ask entry: --ask <bitmask> exists only in pacman.c and flips the default for the question types in the mask (4 is ALPM_QUESTION_CONFLICT_PKG), so it belongs in the record as the way to script a Yes. The fix's sudo pacman -Syu pipewire-jack and the verify's sudo pacman -Syu are both stopped by omarchy-update-pacman-guard on Omarchy 4, which aborts whenever the command line carries both -S and -u without OMARCHY_ALLOW_DIRECT_PACMAN=1 or OMARCHY_UPDATE_PACMAN=1. The symptom said Omarchy shows its message instead of pacman's lines, but omarchy-update-system-pkgs replays the captured stderr first (cat "$errors" >&2), so pacman's error lines come first and the Omarchy line after. omarchy update -y never re-runs interactively, which the record did not say. pipewire-media-session is still in extra (1:0.4.3-1, described as deprecated), so the earlier audit note calling it dropped was wrong and the wireplumber advice stands. Omarchy installs wireplumber, so that prompt does not fire on a stock install. NOT exercised: no conflict was induced, no upgrade was run, and the interactive re-run was not observed.
Running pacman -R jack2 (or worse, -Rns / -Rdd) *before* the replacement is installed cascades: it takes ffmpeg, mpv, fluidsynth and everything downstream, which on a desktop can strip your browser, media player and parts of the compositor's dependency tree. Always let the conflict be resolved inside a single -S/-Syu transaction so the replacement goes in as the old package comes out. -Rdd skips dependency checks entirely and leaves an unbootable or unusable system. Never use it to "win" a conflict prompt.
Symptom
An upgrade stops on a question:
:: pipewire-jack and jack2 are in conflict (jack). Remove jack2? [y/N]
or asks you to pick:
:: There are 2 providers available for jack:
:: Repository extra
1) jack2 2) pipewire-jack
Enter a number (default=1):
or aborts outright:
:: pipewire-jack-1:1.4.7-1 and jack2-1.9.22-1 are in conflict
error: unresolvable package conflicts detected
error: failed to prepare transaction (conflicting dependencies)
On Omarchy 4 omarchy update prints those pacman error lines and then, for the conflict case only, A package conflict stopped this upgrade. Running it again so you can answer: or This upgrade needs an answer. Run omarchy update interactively to give it. A provider question never shows up in omarchy update at all: pacman answers it with the default and carries on.
Cause
Two packages Provides the same virtual name (jack, pipewire-session-manager, libjack.so) and pacman will not keep both. pacman asks three different questions here, and --noconfirm answers each with its default:
- **Conflict** (
X and Y are in conflict. Remove Y? [y/N]): default **No**. Under--noconfirmpacman answers No and aborts the whole transaction withunresolvable package conflicts detected, so one retired package blocks every other upgrade behind it. Answering **y** on the wrong prompt makes pacman drop the conflicting package *and everything that depends on it*, which is the classic way to remove half a desktop with one keystroke. - **Provider** (
There are 2 providers available for jack ... Enter a number (default=1)): default **1**, the first provider in repository order then alphabetical order. Under--noconfirmpacman takes it silently, so a script can installjack2where you wantedpipewire-jackand nothing reports it. pacman only asks when no provider is installed yet, which is why this prompt is rare on an existing desktop and common on a fresh install or after a removal. - **Replace** (
Replace X with extra/Y? [Y/n]): default **Yes**. This is the repository telling you a package was renamed or absorbed. It is not a conflict, and accepting it is the normal path.
Omarchy 4 runs pacman non-interactively in two places: omarchy-update-system-pkgs runs pacman -Syu --noconfirm, and omarchy-pkg-add runs pacman -S --noconfirm --needed. So on Omarchy a conflict stops the upgrade and gets handed back to you, a provider question gets the first provider, and a replace goes through. pacman also has an undocumented --ask <bitmask> that flips the default for the question types in the mask (4 is the conflict question), which is how a script can say Yes without answering every other prompt.
Fix
**Never answer blind. In a second terminal, find out what depends on the package being removed:**
sudo pacman -S --needed pacman-contrib # already installed on Omarchy 4
pactree -r jack2 # what needs it
pacman -Qi jack2 | grep -i 'required by'
**The answers that hold in practice:**
pipewire-jackvsjack2: answer **y** on any modern PipeWire desktop (Omarchy, Arch, EndeavourOS, CachyOS).pipewire-jackprovidesjack libjack.so libjackserver.so libjacknet.so, so ffmpeg/mpv/fluidsynth keep working. Keepjack2**only** if you deliberately run a real JACK server (Ardour with jackd, Bitwig).wireplumbervspipewire-media-session: choose **wireplumber**.pipewire-media-sessionis still in the repos but marked deprecated, and Omarchy installswireplumber.- A provider prompt offering an AUR
-gitvariant of something in the repos: pick the repo one unless you installed the-giton purpose. Replace X with extra/Y? [Y/n]: answer **y**. That is a rename, not a conflict.
**Make the choice explicitly instead of answering a prompt, in one transaction:**
# plain Arch
sudo pacman -Syu pipewire-jack # pacman removes jack2 as part of the same upgrade
sudo pacman -Syu wireplumber
# Omarchy 4: the pacman guard stops any command carrying both -S and -u
sudo env OMARCHY_ALLOW_DIRECT_PACMAN=1 pacman -Syu pipewire-jack
**Omarchy 4, conflict case:** the --noconfirm upgrade answers No and stops. omarchy update detects unresolvable package conflicts detected and re-runs pacman without --noconfirm so you get the [y/N] prompt, but only when stdin and stderr are a real terminal and you did not pass -y. Run it from an actual terminal:
omarchy update
omarchy update -y promises not to ask and prints This upgrade needs an answer. Run omarchy update interactively to give it. instead.
**Omarchy 4, provider case:** omarchy update and omarchy pkg add take provider 1 without telling you. If a fresh install or a script pulled in jack2, swap it in one transaction with the env OMARCHY_ALLOW_DIRECT_PACMAN=1 command above and answer **y** to removing jack2.
**Read the removal list before pressing y.** If the Packages (n) To remove: block is longer than a line or two, answer N and investigate first.
Verify
sudo pacman -Syu completes with no conflict prompt remaining and reports "there is nothing to do" on a second run. For the audio case: pacman -Q pipewire-jack succeeds, pactree -r jack2 errors with "package not found", wpctl status still lists your sinks and sources, and audio still plays.
Sources
- https://forum.endeavouros.com/t/pipewire-jack-and-jack2-are-in-conflict-jack/22882
- https://wiki.archlinux.org/title/PipeWire
- https://github.com/basecamp/omarchy/blob/quattro/bin/omarchy-update-system-pkgs-when-conflicted
- https://github.com/basecamp/omarchy/blob/quattro/bin/omarchy-update-system-pkgs
- https://wiki.archlinux.org/title/Pacman
- https://gitlab.archlinux.org/pacman/pacman/-/raw/v7.1.0/src/pacman/callback.c
- https://gitlab.archlinux.org/pacman/pacman/-/raw/v7.1.0/src/pacman/util.c
- https://gitlab.archlinux.org/pacman/pacman/-/raw/v7.1.0/lib/libalpm/deps.c
- https://gitlab.archlinux.org/pacman/pacman/-/raw/v7.1.0/lib/libalpm/alpm.h
- https://archlinux.org/packages/extra/x86_64/pipewire-jack/
- https://archlinux.org/packages/extra/x86_64/jack2/
- https://archlinux.org/packages/extra/x86_64/pipewire-media-session/