psmisc: Set ALTERNATIVE for pstree to resolve conflict with busybox
PATCH 1/1 psmisc: Set ALTERNATIVE for pstree to resolve conflict with busybox
From: Frieder Schrempf <[email protected]>
If pstree in busybox is enabled there is a conflict with pstree from psmisc resulting in:
do_rootfs: Postinstall scriptlets of ['busybox'] have failed. If the intention is to defer them to first boot, then please place them into pkg_postinst_ontarget:${PN} ().
Deferring to first boot via 'exit 1' is no longer supported.
And more detailed in do_rootfs.log:
update-alternatives: Error: not linking [...]/rootfs/usr/bin/pstree to /bin/busybox.nosuid since [...]/rootfs/usr/bin/pstree exists and is not a link
On order to fix this set ALTERNATIVE:pstree accordingly.
--- meta/recipes-extended/psmisc/psmisc.inc | 2 ++ vscode-bitbake-build/executeBitBakeCmd.sh | 3 +++ 2 files changed, 5 insertions(+) create mode 100755 vscode-bitbake-build/executeBitBakeCmd.sh
meta/recipes-extended/psmisc/psmisc.inc +2 -0
@@ -55,3 +55,5 @@ ALTERNATIVE_PRIORITY = "90" ALTERNATIVE:killall = "killall" ALTERNATIVE:fuser = "fuser" + +ALTERNATIVE:pstree = "pstree"
vscode-bitbake-build/executeBitBakeCmd.sh new file +3 -0
@@ -0,0 +1,3 @@ +#!/bin/bash +. ./oe-init-build-env vscode-bitbake-build > /dev/null +bitbake-layers show-layers
Signature · 1 line
2.40.1
vscode-bitbake-build/executeBitBakeCmd.sh line 3
Quoted 12 lines · Frieder Schrempf via lists.openembedded.org
vscode-bitbake-build/executeBitBakeCmd.sh new file +3
-0@@ -0,0 +1,3 @@ +#!/bin/bash +. ./oe-init-build-env vscode-bitbake-build > /dev/null +bitbake-layers show-layers
Pretty certain you didn’t want this in your commit.
(you might want to add vscode-bitbake-build to your global git ignore)
Ross
Quoted 15 lines · Ross Burton
vscode-bitbake-build/executeBitBakeCmd.sh line 3
Quoted 12 lines · Frieder Schrempf via lists.openembedded.org
vscode-bitbake-build/executeBitBakeCmd.sh new file +3
-0@@ -0,0 +1,3 @@ +#!/bin/bash +. ./oe-init-build-env vscode-bitbake-build > /dev/null +bitbake-layers show-layersPretty certain you didn’t want this in your commit.
Quoted 1 line
(you might want to add vscode-bitbake-build to your global git ignore)
Yeah, stupid mistake and not properly checking the patch before sending it. But that's why I sent a v2 just few minutes after this. Sorry for the noise.