Core Update 167: Update linker config before calling GPG

This avoids log messages like:
ldconfig: /lib/ld-linux-x86-64.so.2 is not a symbolic link

Signed-off-by: Peter Müller <peter.mueller@ipfire.org>

diff --git a/config/rootfiles/core/167/update.sh b/config/rootfiles/core/167/update.sh
index cd518cfb974e7afd65c1b020f95e096561d83695..44b50f82d21d4b1d08ba3e1320595cd84a31c5ad 100644 (file)
--- a/config/rootfiles/core/167/update.sh
+++ b/config/rootfiles/core/167/update.sh
@@ -310,9 +310,6 @@ rm -rvf \
        /usr/share/zoneinfo/US/Pacific-New \
        /var/lib/GeoIP
 
-# Delete old 2007 Pakfire key from GPG keyring
-GNUPGHOME="/opt/pakfire/etc/.gnupg" gpg --batch --yes --delete-keys 179740DC4D8C47DC63C099C74BDE364C64D96617
-
 # Stop services
 /etc/init.d/ipsec stop
 
@@ -322,6 +319,9 @@ extract_files
 # update linker config
 ldconfig
 
+# Delete old 2007 Pakfire key from GPG keyring
+GNUPGHOME="/opt/pakfire/etc/.gnupg" gpg --batch --yes --delete-keys 179740DC4D8C47DC63C099C74BDE364C64D96617
+
 # Add new 2022 Pakfire key to GPG keyring
 GNUPGHOME="/opt/pakfire/etc/.gnupg" gpg --import /opt/pakfire/pakfire-2022.key