linux/poky.git/meta, branch 2.2_M1

build-appliance-image: Update to master head revision

2016-06-21T13:02:39+00:00

(From OE-Core rev: 9431698a88430f0fa892d9b270c0849c4d3d2486) Signed-off-by: Richard Purdie

e2fsprogs: Manually bump PR due to PV change (work around sstate confusion)

2016-06-21T13:02:34+00:00

(From OE-Core rev: cef26f5246db0806eec160c1a3bf77789e0ef1a2) Signed-off-by: Richard Purdie

e2fsprogs: remove the extra dot from the recipe filename

2016-06-21T12:00:17+00:00

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

build-appliance-image: Update to master head revision

2016-06-21T11:58:47+00:00

(From OE-Core rev: b4ccfdfeece9665d9ef8967495fdb1a1d5f494b4) Signed-off-by: Richard Purdie

package_manager: Fix multilib package arch ordering issues

2016-06-21T11:58:40+00:00

Order is not preserved in dict() and this code depends on the order of these lists of package architectures used when multilibs are enabled. This caused 'random' breakage where sometimes the correct order was present and sometimes it wasn't. Use collections.OrderedDict() to avoid this problem. Kudos to Bill Randle and Alejandro Hernandez who did most of the work debugging this, I simply took the problem they identified and wrote a patch to fix it. This unblocks the M1 build but this code needs auditing as there are clearly other ordering issues (e.g. the set() usage). [YOCTO #9717] (From OE-Core rev: 61a33582dfc964d612d20d34734a787d873e312c) Signed-off-by: Richard Purdie

rootfs_rpm: Increase rootfs size

2016-06-20T11:07:49+00:00

This doubles the amount of extra space that is provided for SMART and RPM, as they consume more disk space during qa testing via testimage [YOCTO #9800] (From OE-Core rev: 2d636068d9d3a1ea2db3ace49462be13ba9ef125) Signed-off-by: Saul Wold Signed-off-by: Richard Purdie

Revert "cmake.bbclass: set the modules directory correctly"

2016-06-20T07:40:21+00:00

This reverts commit 642bd49964690259328f506df41a1764c5ac6226. This broke "bitbake cmake": | CMake Error at /home/jku/src/poky/build/tmp/work/core2-64-poky-linux/cmake/3.5.2-r0/toolchain.cmake:34 (list): | Syntax error in cmake code at | | /home/jku/src/poky/build/tmp/work/core2-64-poky-linux/cmake/3.5.2-r0/toolchain.cmake:34 | | when parsing string | | /home/jku/src/poky/build/tmp/sysroots/qemux86-64/usr/share/cmake-\3.5.${CMAKE_MINOR_VERSION}/Modules/ | | Invalid character escape '\3'. | Call Stack (most recent call first): | /home/jku/src/poky/build/tmp/sysroots/x86_64-linux/usr/share/cmake-3.5/Modules/CMakeDetermineSystem.cmake:98 (include) | CMakeLists.txt:19 (project) https://autobuilder.yoctoproject.org/main/builders/nightly-world/builds/832 https://autobuilder.yoctoproject.org/main/builders/nightly-world-lsb/builds/550 Signed-off-by: Richard Purdie

cmake.bbclass: set the modules directory correctly

2016-06-17T16:14:55+00:00

The CMake recipes contain a mismatch between the environmental variable which defines where the Modules are installed and the location where they actually are. This patch fixes the environmental variable to point to the proper folder defined according to the cmake version. (From OE-Core rev: 642bd49964690259328f506df41a1764c5ac6226) Signed-off-by: Jose Pardeiro Signed-off-by: Richard Purdie

pseudo: remove rpath from libpseudo.so

2016-06-17T16:14:55+00:00

Setting rpath causes clash of host and sdk libc and makes pseudo to crash with relocation error: libpthread.so.0: symbol __libc_vfork, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference Removing rpath fixes this as it makes pseudo to use only host pthread and libc. [YOCTO #9761] (From OE-Core rev: be5c943e82a21d3ef2dfaaa5b41b6a2814f2fb19) Signed-off-by: Ed Bartosh Signed-off-by: Richard Purdie

useradd-staticids.bbclass: Allow missing UIDs/GIDs to generate warnings

2016-06-17T16:14:55+00:00

Previously when USERADD_ERROR_DYNAMIC was set to "1", an exception was raised if no numeric UID/GID could be determined for a user/group. Now it is possible to set it to either "error", which results in the old behavior, or "warn" in which case a warning is issued instead. For backwards compatibility reasons, it is still possible to set USERADD_ERROR_DYNAMIC to "1" and get an exception in case of failure. (From OE-Core rev: 58c82f79efee8e68fa63b96a32f54660afb15769) Signed-off-by: Peter Kjellerstedt Signed-off-by: Richard Purdie