From f4f905943b4abec276fba2a34eb9f7da166a7b6b Mon Sep 17 00:00:00 2001 From: Peter Jung Date: Mon, 19 Aug 2024 20:29:36 +0200 Subject: [PATCH] clamares-online: Lets hope it works now Signed-off-by: Peter Jung --- archiso/airootfs/usr/local/bin/calamares-online.sh | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/archiso/airootfs/usr/local/bin/calamares-online.sh b/archiso/airootfs/usr/local/bin/calamares-online.sh index 763339a..b34155e 100755 --- a/archiso/airootfs/usr/local/bin/calamares-online.sh +++ b/archiso/airootfs/usr/local/bin/calamares-online.sh @@ -26,12 +26,14 @@ catch_chrooted_pacman_log() { } Main() { + # Remove current keyring first, to completle intiate it + sudo rm -rf /etc/pacman.d/gnupg # We are using this, because archlinux is signing the keyring often with a newly created keyring # This results into a failed installation for the user. # Installing archlinux-keyring fails due not being correctly signed # Mitigate this by installing the latest archlinux-keyring on the ISO, before starting the installation # The issue could also happen, when the installation does rank the mirrors and then a "faulty" mirror gets used - sudo pacman -Sy --noconfirm archlinux-keyring + sudo pacman -Sy --noconfirm archlinux-keyring cachyos-keyring # Also populate the keys, before starting the Installer, to avoid above issue sudo pacman-key --init sudo pacman-key --populate archlinux cachyos