Hongxu Jia c26566e44b kbd: avoid vlock conflict with busybox ...

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.

(From OE-Core rev: 08636708f6ca677a6ee6c88fa2999c7b70b7d474)

Signed-off-by: Khem Raj <raj.khem@gmail.com>

The vlock doesn't exist if PAM isn't enabled.

Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

2019-12-15 09:10:46 +00:00

..

kbd

kbd: update to 2.2.0

2019-12-09 12:00:42 +00:00

kbd_2.2.0.bb

kbd: avoid vlock conflict with busybox

2019-12-15 09:10:46 +00:00