From 376fea3c81b66df281ffb73219f5a3c82f679fea Mon Sep 17 00:00:00 2001 From: Craig Jennings Date: Tue, 26 May 2026 19:04:00 -0500 Subject: fix(archsetup): stop yay hanging on its diff prompt during unattended installs A VM test run hung for 80 minutes and timed out. yay was blocking on "Diffs to show?" for an AUR package whose build files already existed, waiting for input that never comes in a headless install. --noconfirm doesn't cover yay's diff and clean menus. I added --answerdiff None --answerclean None to the yay call in aur_install: show no diffs, don't clean, proceed. This is the right answer for an unattended run and matches the --noconfirm posture already in place. It likely explains the recurring 90-minute VM-test timeouts that read like slow AUR builds. --- archsetup | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/archsetup b/archsetup index 566a186..88b7c2e 100755 --- a/archsetup +++ b/archsetup @@ -595,7 +595,11 @@ pacman_install() { # AUR Install aur_install() { - retry_install "$1" "AUR" "sudo -u \"$username\" yay -S --noconfirm \"$1\"" + # --answerdiff/--answerclean None: yay's diff and clean menus aren't covered + # by --noconfirm, so on a headless install they block forever waiting for + # input (seen hanging on a "Diffs to show?" prompt when build files exist). + # None means show no diffs and don't clean -- the right answer for unattended. + retry_install "$1" "AUR" "sudo -u \"$username\" yay -S --noconfirm --answerdiff None --answerclean None \"$1\"" } # Git Install -- cgit v1.2.3