From 66caeb5ca7dbe497fa40c5a5d321548f7a879b27 Mon Sep 17 00:00:00 2001
From: Craig Jennings <c@cjennings.net>
Date: Thu, 25 Jun 2026 14:39:08 -0400
Subject: fix(archsetup): keep pacman.conf world-readable for AUR builds

User-level makepkg reads /etc/pacman.conf to resolve dependencies, so a root-only file makes every AUR build (starting with yay) fail with "could not be read: Permission denied". A current archangel ISO ships the base pacman.conf as 0600. archsetup already edits the file (ParallelDownloads, Color, multilib), so it now chmods it back to 0644, the Arch default, before the AUR installer runs.

The ZFS VM test path surfaced this on a fresh archangel base. The older btrfs base shipped it 0644.
---
 archsetup | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/archsetup b/archsetup
index cc62751..ae87c3a 100755
--- a/archsetup
+++ b/archsetup
@@ -965,6 +965,13 @@ prerequisites() {
     # enable multilib repository (required for 32-bit libraries, Steam, etc.)
     action="enabling multilib repository" && display "task" "$action"
     sed -i '/^#\[multilib\]/{s/^#//;n;s/^#//}' /etc/pacman.conf
+
+    # Keep pacman.conf world-readable. User-level makepkg/yay reads it to
+    # resolve dependencies, so a root-only file makes every AUR build fail with
+    # "/etc/pacman.conf could not be read: Permission denied". Some base images
+    # (a current archangel ISO) ship it 0600; 0644 is the Arch default.
+    chmod 644 /etc/pacman.conf
+
     pacman -Sy >> "$logfile" 2>&1
 
     action="Package Mirrors" && display "subtitle" "$action"
-- 
cgit v1.2.3