linux/poky.git/meta/recipes-core/kbd, branch hardknott

meta/recipes-core: Add HOMEPAGE / DESCRIPTION

2021-02-26T15:21:21+00:00

Added HOMEPAGE and DESCRIPTION for recipes with missing decriptions or homepage [YOCTO #13471] (From OE-Core rev: be8d3d0fa6bbc2924ffbdbaa66e9ffaef2b96de6) Signed-off-by: Dorinda Bassey Signed-off-by: Richard Purdie

kbd: fix transaction conflict

2021-01-08T10:10:15+00:00

After kdb upgrades to 2.4.0, vlock.pamd will be copied to /etc/pam.d/vlock when install as [1]. And it will result in below Transaction error during do_rootfs when both vlock and kbd installed: | Transaction test error: file /etc/pam.d/vlock conflicts between attempted installs of vlock-2.2.3-r0.corei7_64 and kbd-2.4.0-r0.corei7_64 So rename vlock to vlock.kbd to fix the gap. [1] https://git.kernel.org/pub/scm/linux/kernel/git/legion/kbd.git/commit/?id=b9cbb05038e01a7c4b3899589c591734e643a281 (From OE-Core rev: 315f2453515a4cd0f1cc2d1bdddeb0c385aee2d4) Signed-off-by: Mingli Yu Signed-off-by: Richard Purdie

kbd: upgrade 2.3.0 -> 2.4.0

2020-12-30T14:01:06+00:00

(From OE-Core rev: 0bb9e942a6919990fc0f9491d754fe49b7f6aeaf) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie

kbd: update 2.2.0 -> 2.3.0

2020-08-02T13:42:08+00:00

Drop ptest support: upstream has rewritten the tests in GNU autotest, which is another m4 monstrosity entirely incompatible with the idea of installing tests to the target system. All dropped patches are either merged upstream, or made for ptest. (From OE-Core rev: 79f456da4b752f897bb5546d9ec291cdf4196ae8) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie

kbd: Fix build reproducibility issue

2020-01-27T16:48:10+00:00

Our CFLAGS were being lost which was breaking reproducibile builds due to losee of the debug prefix remapping flags. Fix this. (From OE-Core rev: 037bef5c7dfe82642d19f07b38f6ccc783958e41) Signed-off-by: Richard Purdie

kbd: make libkbdfile-test08 ptest work for multilib

2020-01-27T16:48:08+00:00

This patch fixes kbd ptest libkbdfile-test08 failure in 64-bit images. ```sh root@intel-x86-64:/usr/lib64/kbd/ptest# ./run-ptest make: Entering directory '/usr/lib64/kbd/ptest/tests' make[1]: Entering directory '/usr/lib64/kbd/ptest/tests' PASS: libkbdfile-test01 PASS: libkbdfile-test02 PASS: libkbdfile-test03 PASS: libkbdfile-test04 PASS: libkbdfile-test05 PASS: libkbdfile-test06 PASS: libkbdfile-test07 FAIL: libkbdfile-test08 PASS: libkbdfile-test09 ... ``` `DATADIR` and `ABS_DATADIR` are compile flags defined in ./kbd/tests/Makefile.am. `DATADIR` is the relative directory of kbd, i.e `./kbd/ptest/tests` whereas `ABS_DATADIR` is the full directory path, i.e `/usr/lib/kbd/ptest/tests`. The latter has a problem when building ptests for a 64-bit image, because the tests folder is located at `/usr/lib64/kbd/ptest/tests` instead. Therefore `ABS_DATADIR` is changed to `DATADIR`, also consistent with what *every other* kbd test is doing. The test searches DATADIR recursively for a file named `test0.map`, but it finds the wrong file at `/findfile/test_0/keymaps/test0.map`, while it actually needs `/findfile/test_0/keymaps/i386/qwerty/test0.map`. Thus appending `/i386` to `dirpath` so that `libkbdfile-test08.c` finds the right test file. (From OE-Core rev: bdcda2c4ff3c96f686b8bd30cd17361ff3722a0f) Signed-off-by: Matthew Zeng Signed-off-by: Richard Purdie

kbd: fix failing ptests

2020-01-10T21:18:22+00:00

Some assumptions about where data files are needs to be adjusted. (From OE-Core rev: ae39de0119ac1d21512fe64f7f7969790e396819) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie

kbd: fix ptest can NOT run issue

2019-12-30T08:47:12+00:00

After kbd updated to 2.2.0, it fails to run ptest: | make: *** No rule to make target 'libkbdfile-test01.c', needed by 'libkbdfile-test01'. Update sed expression to fix such kind of issues. And also make target dumpkeys-bkeymap and dumpkeys-bkeymap which are required by ptest. (From OE-Core rev: 2fb86f46baed43316086ce10de635c326e073c2d) Signed-off-by: Kai Kang Signed-off-by: Richard Purdie

kbd: avoid vlock conflict with busybox

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

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 /usr/bin/vlock to /bin/busybox.suid since /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 The vlock doesn't exist if PAM isn't enabled. Signed-off-by: Hongxu Jia Signed-off-by: Richard Purdie

kbd: update to 2.2.0

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

Rebase set-proper-path-of-resources.patch Add a patch to address a string format error; as it modifies a .l file, add a dependency on flex which is processing that into C source code. License-Update: file with copyright statements was replaced with original GPLv2 text (From OE-Core rev: 729ac34dce472378cec5447c366a28de2081e7de) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie