From 490e86f4034489e1da7a83b4505d04d646e4cc2a Mon Sep 17 00:00:00 2001 From: =?utf8?q?Peter=20M=C3=BCller?= Date: Fri, 8 Apr 2022 15:59:25 +0000 Subject: [PATCH] Core Update 167: Update linker config before calling GPG MIME-Version: 1.0 Content-Type: text/plain; charset=utf8 Content-Transfer-Encoding: 8bit This avoids log messages like: ldconfig: /lib/ld-linux-x86-64.so.2 is not a symbolic link Signed-off-by: Peter Müller --- config/rootfiles/core/167/update.sh | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/config/rootfiles/core/167/update.sh b/config/rootfiles/core/167/update.sh index cd518cfb97..44b50f82d2 100644 --- 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 -- 2.47.3