linux/poky.git/meta, branch 2.8_M3

build-appliance-image: Update to master head revision

2019-09-19T19:32:53+00:00

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

layer.conf: Remove weston-conf from SIGGEN_EXCLUDE_SAFE_RECIPE_DEPS

2019-09-19T19:31:17+00:00

This recipe is gone (From OE-Core rev: 3a8e60bb36631ba2b32213c234ec7b4e1e2544d5) Signed-off-by: Khem Raj Signed-off-by: Richard Purdie

tzdata: Correct the packaging of /etc/localtime and /etc/timezone

2019-09-19T19:30:35+00:00

During restructuring of the packaging in 2af4d6eb (tzdata: Install everything by default), these two files remained in the tzdata package, which is supposed to be empty. Move them to tzdata-core where they belong. Also simplify the definition of CONFFILES_tzdata-core. As its value only takes effect for files that actually exist, there is no need to complicate its definition by checking if a file is created before adding it to the list of configuration files. (From OE-Core rev: 3d2d31fed64169f08c0ecfce4c07b8c7ebd052d2) Signed-off-by: Peter Kjellerstedt Signed-off-by: Richard Purdie

package_rpm.bbclass: Remove a misleading bb.note()

2019-09-19T19:30:35+00:00

It should have been removed in 3db9d865 (classes/package_rpm.bbclass: Enhance diagnostic messages) when it was split in two new notes. Also change the casing of two other notes to align them with the other notes. (From OE-Core rev: b40e245795cd19c7d36df096fa1f30c75490ce46) Signed-off-by: Peter Kjellerstedt Signed-off-by: Richard Purdie

meson.bbclass: Handle microblaze* mapping to cpu family

2019-09-19T19:30:35+00:00

(From OE-Core rev: 01692856b8294109ac553c5c0cc23dbb5f1a8970) Signed-off-by: Nathan Rossi Signed-off-by: Richard Purdie

oeqa/concurrenttest: Use ionice to delete build directories

2019-09-19T19:30:35+00:00

Autobuilder type infrastructure can benefit from deletion of certain files as background IO due to the way Linux filesystem priority works. We have problems where build directories as part of oe-selftest being delete starves the running tasks of IO to the point builds take much longer to compelte. Having this option of running the deletion at "idle" helps a lot with that. Use the new option added to bb.utils.prunedir(). (From OE-Core rev: d41e7018be56902b7a1be4590e468cd15e02a3b5) Signed-off-by: Richard Purdie

externalsrc: stop rebuilds of 2+ externalsrc recipes sharing the same git repo

2019-09-19T19:30:35+00:00

externalsrc do_configure task watches oe-devtool-tree-sha1 file and its checksum. That file basically contains the result of `git add -A ${EXTERNALSRC} && git write-tree` which is the hash of temporary "commit" of the non committed changes. This file is stored in the .git directory of the git repo of the externalsrc recipe. do_configure then depends on the checksum of oe-devtool-tree-sha1 file. If 2+ recipes with different externalsrc paths but same git repo (e.g. one recipe at /some/path and the other at /some/path/subdir) are parsed, this oe-devtool-tree-sha1 will be overwritten by those recipes at parsing time since .git is shared between those recipes. If there is one non committed git change in /some/path but not in /some/path/subdir, the oe-devtool-tree-sha1 of both recipes will be different. What will happen is that recipe1 will watch over the oe-devtool-tree-sha1 with a specific checksum, fill in file-checksums for do_configure correctly, then recipe2 will watch over the identically named file with different content also fill in the file-checksums varflag. When do_configure of recipe1 will be evaluated for re-execution, oe-devtool-tree-sha1 will be of the value of what is watched over by recipe2, thus triggering a rebuild of recipe1. This behavior is not always reproducible which I'm guessing is due to a small window between recipe1 putting info into oe-devtool-tree-sha1 and calculating the checksum of that file and recipe2 putting its content into oe-devtool-tree-sha1. By appending the name of the recipe to oe-devtool-tree-sha1, we make sure that a recipe won't have its oe-devtool-tree-sha1 overwritten by another recipe sharing the same externalsrc git repo. (From OE-Core rev: 1b727dd7295a7a7fe17800f8038242efbf7fe2b7) Signed-off-by: Quentin Schulz Signed-off-by: Richard Purdie

meta-extsdk: Either an sstate task is a proper task or it isn't

2019-09-19T19:30:35+00:00

Ensure the task is properly regsistered as an sstate task as this "half way" state confuses new code in bitbake and it isn't supported. (From OE-Core rev: 53d6cd98216e3b73c0c90e42223efd1a2b649358) Signed-off-by: Richard Purdie

systemd: Handle slow to boot mips hwdb update timeouts

2019-09-19T14:27:02+00:00

This is a temporary workaround to avoid autobuilder failures until https://github.com/systemd/systemd/issues/13581 is resolved. Its being done globally even though its a mips problem for simplicity, it doesn't hurt anything else to have a longer timeout. (From OE-Core rev: 101d1ea3fe2d40ddde3139952545fa7128478f66) Signed-off-by: Richard Purdie

populate_sdk_ext: Introduce mechanism to keep nativesdk* sstate in esdk

2019-09-19T14:27:02+00:00

When doing a devtool build-sdk from within an esdk all nativesdk components would be rebuilt. This patch introduces SDK_INCLUDE_NATIVESDK flag to toggle the inclusion of nativesdk packages when creating the esdk sstate Currently locked-sigs.inc is generated during do_sdk_depends which doesn't pull in nativesdk packages. Generating another locked-sigs.inc in do_populate_sdk_ext and pruning it to only nativesdk* packages by using a modified version of the already existing function prune_locked_sigs and merging it with the current locked-sigs.inc Also adding SDK_INCLUDE_NATIVESDK tasklistfn to the logic surrounding setting tasklist file to not prune esdk sstate during creation [YOCTO #13261] (From OE-Core rev: d046afd12e1c209b29dca6ba402b9aa14680c5ce) Signed-off-by: Jaewon Lee Signed-off-by: Richard Purdie