linux/poky.git/scripts, branch jethro-14.0.1

yocto-bsp: Set SRCREV meta/machine revisions to AUTOREV

2016-02-04T23:20:18+00:00

By default, checkout to latest revision from the machine branch specified by the user. (From meta-yocto rev: f79a43406b5b323587415380ecffc87527c64653) (From meta-yocto rev: 311e084bb321701624785ce56a1ad23d7b20b396) Signed-off-by: Leonardo Sandoval Signed-off-by: Richard Purdie (cherry picked from commit a35f79ddd8afe54835ad927b21b8f7cfbd86202a) Signed-off-by: Leonardo Sandoval Signed-off-by: Saul Wold Signed-off-by: Richard Purdie

yocto-bsp: Set KTYPE to user selected base branch

2016-02-04T23:20:18+00:00

Fixes the hardcode branch name set to KTYPE, where its value is used as a base branch when user decides to create a new branch. Tested on x86_64 architecture. [YOCTO #8630] (From meta-yocto rev: ab895be90a0cae7dfa77a8aab3b19e5571e7e7bc) (From meta-yocto rev: bc5aec2348b2c314953806734a8fbabf798d142c) Signed-off-by: Leonardo Sandoval Signed-off-by: Richard Purdie (cherry picked from commit 9d585b5025187f059f75ffbdc01bda72d17e8a86) Signed-off-by: Leonardo Sandoval Signed-off-by: Saul Wold Signed-off-by: Richard Purdie

yocto-bsp: Avoid duplication of user patches ({{=machine}}-user-patches.scc)

2016-02-04T23:20:18+00:00

On linux-yocto-dev or linux-yocto_X.YY bbappend files, the SRC_URI includes {{=machine}}-standard.scc, which in turn includes {{=machine}}-user-parches.scc, thus there is no need to include it again on the corresponding bbappend file. [YOCTO #8486] (From meta-yocto rev: 11c93b5dd8c651df478d4810e1b6ff6ad9fa57e8) (From meta-yocto rev: c1105ff0e65a24f344e5fab17402b1b4fcb1d728) Signed-off-by: Leonardo Sandoval Signed-off-by: Richard Purdie (cherry picked from commit f674ffa528b06e22d2c70c12f2e17cf308e26173) Signed-off-by: Leonardo Sandoval Signed-off-by: Saul Wold Signed-off-by: Richard Purdie

yocto-bsp: Default kernel version to 4.1 on x86_64

2016-02-04T23:20:18+00:00

On the 3.19 to 4.1 migration, the target x86_64 was not taken into account (no reason, just missing the correspoding update on the kernel-list.noinstall file), so moving it to 4.1 to be align with the rest. (From meta-yocto rev: 283665d9295c3c10f964496dc0110137e358daa6) (From meta-yocto rev: d58d3c5e65294bd6f4f3f780d746e1c3f8678c2b) Signed-off-by: Leonardo Sandoval Signed-off-by: Ross Burton Signed-off-by: Richard Purdie (cherry picked from commit 9cc221dcb6af71ae8a4faa3297269ae80c7e35dd) Signed-off-by: Leonardo Sandoval Signed-off-by: Saul Wold Signed-off-by: Richard Purdie

gen-lockedsig-cache: fix bad destination path joining

2016-02-04T23:20:17+00:00

When copying the sstate-cache into the extensible SDK, if the source path had a trailing / and the destination path did not, there would be a missing / between the path and the subdirectory name, and you'd end up with subdirectories like "sstate-cacheCentOS-6.7". There are functions in os.path for this sort of thing so let's just use them and avoid the problem. (From OE-Core rev: 2ed6adfea5ba16aeda7b5d908bea4303202d3774) Signed-off-by: Paul Eggleton Signed-off-by: Ross Burton (cherry picked from commit 5eb8f15c48b5f39a10eb2b63b026cf1ebfd05533) Signed-off-by: Saul Wold Signed-off-by: Richard Purdie

devtool: reset: do clean for multiple recipes at once with -a

2016-01-15T15:51:41+00:00

We need to run the clean for all recipes that are being reset before we start deleting things from the workspace; if we don't, recipes providing dependencies may be missing when we come to clean a recipe later (since we don't and couldn't practically reset them in dependency order). This also improves performance since we have the startup startup time for the clean just once rather than for every recipe. (From OE-Core master rev: c10a2de75a99410eb5338dd6da0e0b0e32bae6f5) (From OE-Core rev: d64a5794098e9ca715a70daa704f571ba97e9912) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie

devtool: sdk-update: fix error checking

2016-01-15T15:51:41+00:00

Running "raise" with no arguments here is invalid, we're not in exception handling context. Rather than also adding code to catch the exception I just moved the check out to the parent function from which we can just exit. (From OE-Core master rev: 0164dc66467739b357ab22bf9b8c0845f3eff4a4) (From OE-Core rev: d9c5653f994e0f366c9154a2a988175a9f8e3130) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie

devtool: sdk-update: fix metadata update step

2016-01-15T15:51:41+00:00

* Clone the correct path - we need .git on the end * Pull from the specified path instead of expecting a remote to be set * up in the repo already (it isn't by default) (From OE-Core master rev: 1a60ee8bd21e156022c928f12bb296ab5caaa766) (From OE-Core rev: a0e1ff92b189681df5cf106dc924e76bb05caf31) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie

devtool: sdk-update: fix not using updateserver config file option

2016-01-15T15:51:41+00:00

We read the updateserver setting from the config file but we never actually used that value - the code then went on to use only the value supplied on the command line. Fix courtesy of Dmitry Rozhkov (From OE-Core master rev: 1c85237803038fba539d5b03bf4de39d99380684) (From OE-Core rev: 3940fe87f944bd2067a96b1b6a8c1dc646569690) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie

scripts/oe-publish-sdk: add missing call to git update-server-info

2016-01-15T15:51:40+00:00

We need to call git update-server-info here on the created repository or we can't share it over plain http as we need to be able to for the update process to function as currently implemented. (From OE-Core master rev: 3ab40bf9d5f19d91e45f7bae77f037b2544e889b) (From OE-Core rev: 2b3c7c6fc52a0fb66e31796ca7daacd19afbf75f) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie