Remove the dead [community] repository after 'failed retrieving file community.db'
Cause, date and repository list confirmed against the Arch news post of 2025-02-17, which names the six repositories, the 2025-03-01 removal and the .pacnew shipped with pacman>=6.0.2-7. The forum thread carries the exact symptom. Omarchy's pacman-stable.conf was read locally and on the quattro branch: it lists only [core], [extra], [multilib] and [omarchy]. The defect is the Omarchy branch: it says 'delete the section as above', which leads the reader to the plain-Arch sudo pacman -Syu that the ALPM guard refuses, and it refers to 'the second command' when the block has one. Read on 4.0.4-1: omarchy-refresh-pacman saves .bak copies, copies the channel's pacman.conf and mirrorlist, runs the pre-refresh-pacman hook, then runs pacman -Syyuu --noconfirm, which can downgrade packages as well as upgrade them. The fix now gives a separate Omarchy procedure and states what the refresh actually does. Nothing was run. Second audit confirmed the corrected text: Arch news of 2025-02-17 (retrieved) names the six repositories, the 2025-03-01 removal and the .pacnew shipped with pacman>=6.0.2-7, matching the cause. Forum thread 303841 carries the exact 404 output and the fix of removing [community]. On this machine /etc/pacman.conf and /usr/share/omarchy/default/pacman/pacman-stable.conf list only [core], [extra], [multilib] and [omarchy]. Read /usr/share/omarchy/bin/omarchy-refresh-pacman on 4.0.4-1: it writes /etc/pacman.conf.bak and /etc/pacman.d/mirrorlist.bak, copies the channel files, runs the pre-refresh-pacman hook, then sudo env OMARCHY_UPDATE_PACMAN=1 pacman -Syyuu --noconfirm, exactly as the fix and danger say. The ALPM guard (/usr/share/libalpm/hooks/00-omarchy-update-guard.hook, /usr/bin/omarchy-update-pacman-guard) refuses -S with -u, so the Omarchy branch correctly routes through omarchy update. Minor: the pacdiff example uses DIFFPROG='nvim -d', which a plain Arch reader may not have installed. Nothing was run.
omarchy refresh pacman replaces /etc/pacman.conf and /etc/pacman.d/mirrorlist wholesale, dropping any third-party repositories you added (backups are written to /etc/pacman.conf.bak and /etc/pacman.d/mirrorlist.bak).
Symptom
Every sync stops on the community database, on every mirror in the list:
:: Synchronizing package databases...
core downloading...
extra downloading...
community downloading...
error: failed retrieving file 'community.db' from arch.mirror.constant.com : The requested URL returned error: 404
error: failed retrieving file 'community.db' from us.mirrors.cicku.me : The requested URL returned error: 404
error: failed to synchronize all databases (failed to retrieve some files)
Nothing was changed on the machine. It just stopped updating one day, usually on a box that had not been updated for a long time or a distro that stopped shipping config updates.
Cause
Arch merged [community] into [extra] in 2023 and kept the old repository online but empty. On 2025-03-01 Arch deleted [community], [community-testing], [testing], [testing-debug], [staging] and [staging-debug] from the mirrors. A pacman.conf that still lists any of them now asks every mirror for a file that no longer exists, and pacman aborts the whole sync. The replacement pacman.conf without those sections shipped as /etc/pacman.conf.pacnew with pacman 6.0.2-7, so systems that never merged that .pacnew are the ones that break.
Fix
Find the dead sections:
grep -n -A2 -E '^\[(community|community-testing|testing|testing-debug|staging|staging-debug)\]' /etc/pacman.conf
ls -l /etc/pacman.conf.pacnew 2>/dev/null
**Plain Arch, EndeavourOS, Manjaro.** Back up, then delete each matched section header together with its Include = line:
sudo cp /etc/pacman.conf /etc/pacman.conf.bak
sudoedit /etc/pacman.conf
Remove blocks like these entirely:
[community]
Include = /etc/pacman.d/mirrorlist
If a .pacnew exists, merge it instead of hand-editing, since it carries the other changes you also missed:
sudo pacman -S --needed pacman-contrib
sudo DIFFPROG='nvim -d' pacdiff
Then do a full upgrade, never a bare -Sy:
sudo pacman -Syu
**Omarchy 4.** The pacman.conf Omarchy installs (/usr/share/omarchy/default/pacman/pacman-stable.conf) lists only [core], [extra], [multilib] and [omarchy], so this only happens if an old pacman.conf was restored over it. Either delete the dead sections with the same backup and sudoedit steps above and then update through Omarchy (direct sudo pacman -Syu is refused by Omarchy's ALPM guard):
omarchy update
or put Omarchy's own file back. This saves /etc/pacman.conf.bak and /etc/pacman.d/mirrorlist.bak, overwrites both files with the stable channel's copies (dropping every third-party repository you added), then runs pacman -Syyuu --noconfirm, which can downgrade packages to the channel's versions as well as upgrade them:
omarchy refresh pacman
Verify
pacman-conf --repo-list no longer prints community, and the next full upgrade synchronizes every database without a 404.