From b3f4b641ce63e35de56ea5a50b042560ce24cc3c Mon Sep 17 00:00:00 2001 From: Kai Lueke Date: Mon, 14 Mar 2022 18:55:07 +0100 Subject: [PATCH] sys-apps/baselayout: force link creation in tmpfile rule The /lib symlink does not point to /usr/lib but instead points to /usr/lib64 on current releases which have a single /usr/lib64 folder and a symlink from /usr/lib to it. This means that when they update to a release with a split lib vs. lib64 setup, the kernel modules are not found because /lib/modules does not exist (because /lib still points to /usr/lib64 instead of /usr/lib). Force link recreation to match the new layout. The system will still be able to rollback because the link to /usr/lib is still valid because /usr/lib is itself a link that forwards to /usr/lib64. --- .../coreos-overlay/sys-apps/baselayout/baselayout-9999.ebuild | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sdk_container/src/third_party/coreos-overlay/sys-apps/baselayout/baselayout-9999.ebuild b/sdk_container/src/third_party/coreos-overlay/sys-apps/baselayout/baselayout-9999.ebuild index ff50a0d91e..70574b6e64 100644 --- a/sdk_container/src/third_party/coreos-overlay/sys-apps/baselayout/baselayout-9999.ebuild +++ b/sdk_container/src/third_party/coreos-overlay/sys-apps/baselayout/baselayout-9999.ebuild @@ -102,7 +102,7 @@ src_compile() { local tmpfiles="${T}/baselayout-usr.conf" echo -n > ${tmpfiles} || die for sym in "${!USR_SYMS[@]}" ; do - echo "L ${sym} - - - - ${USR_SYMS[$sym]}" >> ${tmpfiles} + echo "L+ ${sym} - - - - ${USR_SYMS[$sym]}" >> ${tmpfiles} done fi }