[OE-core] kbd: avoid vlock conflict with busybox
Richard Leitner
richard.leitner at skidata.com
Thu Dec 12 11:00:50 UTC 2019
On 07/12/2019 08:22, Khem Raj wrote:
> busybox as well as vlock utility from meta-oe provides vlock utility
> which can conflict when with kbd if pam is a enabled distro_feature
>
> Fixes image build errors
>
> update-alternatives: Error: not linking <rootfs>/usr/bin/vlock to /bin/busybox.suid since <rootfs>/usr/bin/vlock exists and is not a link
>
> ERROR: yoe-qt5-wayland-image-1.0-r0 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.
>
> Signed-off-by: Khem Raj <raj.khem at gmail.com>
Tested-by: Richard Leitner <richard.leitner at skidata.com>
More information about the Openembedded-core
mailing list