linux/poky.git/scripts, branch hardknott-3.3.3

wic: don't forcibly pass -T default

2021-08-26T07:32:14+00:00

This reverts part of oe-core eecbe62555, which was a previous attempt to solve the Y2038 problem. This is now solved centrally in e2fsprogs, so doesn't need to be dealt with in wic. We don't revert the commit entirely, to retain the warning if a filesystem has small inodes. (From OE-Core rev: c727397e2544dffe3cccb8be3c87cf49227560f6) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie (cherry picked from commit 7e8017208bed98b6c90735cb641fc9d7aedf9140) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie

runqemu: Fix typo in error message

2021-08-14T11:01:44+00:00

(From OE-Core rev: f2f9eb53515c7f1890365aa6441f556fb862e429) Signed-off-by: Matthias Klein Signed-off-by: Richard Purdie (cherry picked from commit 5cc0051d50974e198313f9513b24fd7ae9a96dd4) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie

devtool: print a warning on upgrades if PREFERRED_VERSION is set

2021-08-14T11:01:43+00:00

(From OE-Core rev: 5fb2fb70d14b0e9f6235e5b940e9a3e1145750bb) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie (cherry picked from commit 0b0f53eed0aadbf45d9eead96ebf7725cc7447e6) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie

oe-setup-builddir: update YP docs and OE URLs

2021-08-06T08:59:15+00:00

This updates the link to the YP docs and proposes to access the OE website through https (From OE-Core rev: 2fd915eda136e20ab52baea6bb908d08ef8f5cbc) Signed-off-by: Michael Opdenacker Signed-off-by: Richard Purdie (cherry picked from commit 87686233aeffc639c3f412fd5c4898b32b15013b) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie

yocto-check-layer: ensure that all layer dependencies are tested too

2021-08-06T08:59:15+00:00

In order to be compliant with the YP compatible status, a layer also needs to ensure that all its dependencies are compatible too. Currently yocto-check-layer only checks the requested layer, without testing any dependencies. With this change, all dependencies are also checked by default, so the summary printed at the end will give a clear picture whether all dependencies pass the script or not. Using --no-auto-dependency can be used to skip that. (From OE-Core rev: 4a5bcd5fe81f0b6d1b8fac700eb19f1651809109) Signed-off-by: Nicolas Dechesne Signed-off-by: Alexandre Belloni Signed-off-by: Richard Purdie (cherry picked from commit 45d59b774b95c91193a8376b83c05291d555e5c8) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie

checklayer: rename _find_layer_depends

2021-08-06T08:59:15+00:00

What this function does is really to find a layer, not a 'depends'. We are using this function to find a dependent layer, but the name is confusing. (From OE-Core rev: fa52d417ed578194274003c12e14cf93bdb8f7fb) Signed-off-by: Nicolas Dechesne Signed-off-by: Alexandre Belloni Signed-off-by: Richard Purdie (cherry picked from commit e9b7690ab30d0e7c07471034f6cb89ccc3168a11) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie

checklayer: new function get_layer_dependencies()

2021-08-06T08:59:15+00:00

Split add_layer_dependencies() into 2 parts. First search for layer dependencies, and then add them to the config. That allows us to call get_layer_dependencies() independently. (From OE-Core rev: a3d5e108b6982771c99a75abf09a8210788c5be1) Signed-off-by: Nicolas Dechesne Signed-off-by: Alexandre Belloni Signed-off-by: Richard Purdie (cherry picked from commit 08edf928aac3f2daaa0c256d4c21e56e2db72bff) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie

yocto-check-layer: improve missed dependencies

2021-08-06T08:59:14+00:00

The first 2 calls to add_layer_dependencies() are here to add all dependencies for the 'layer under test' and the additional layers provided by the users. In both cases, we use misssing_dependencies boolean to indicate if any dependency is missing. But we then never really use missing_dependencies. Instead the script is calling add_layer_dependencies() again (for both the layer under test, and the additional layers) to detect if there are any missing dependency. As a result, we are trying to add again all dependencies, and we can see that from the traces: INFO: Detected layers: INFO: meta-aws: LayerType.SOFTWARE, /work/oe/sources/meta-aws INFO: checklayer: Doesn't have conf/layer.conf file, so ignoring INFO: INFO: Setting up for meta-aws(LayerType.SOFTWARE), /work/oe/sources/meta-aws INFO: Adding layer meta-python INFO: Adding layer meta-oe INFO: Adding layer meta-networking --> INFO: Adding layer meta-python INFO: meta-python is already in /work/oe/poky/master/build-checklayer/conf/bblayers.conf INFO: Adding layer meta-oe INFO: meta-oe is already in /work/oe/poky/master/build-checklayer/conf/bblayers.conf INFO: Adding layer meta-networking INFO: meta-networking is already in /work/oe/poky/master/build-checklayer/conf/bblayers.conf <-- INFO: Getting initial bitbake variables ... The code appears more complex than it should, and we can simply replace the complex if statement by using missing_dependencies, and avoid duplicating the call to add_layer_dependencies(). (From OE-Core rev: 073637cbc99c0e6c05138f248856181154f33b70) Signed-off-by: Nicolas Dechesne Signed-off-by: Alexandre Belloni Signed-off-by: Richard Purdie (cherry picked from commit fceb84f7bc472731b8f96ee1ebf0f4485943226c) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie

devtool: correctly handle non-standard source tree locations in upgrades

2021-08-06T08:59:14+00:00

When S is set to a sub-directory of upstream source, the license checks and the bbappend writing (specifically, setting EXTERNALSRC) need to operate on that sub-directory. 'devtool modify' already has similar logic, and it was copied from there and adjusted. (From OE-Core rev: ddf5a7f3b644915d360f725eca8322187226f171) Signed-off-by: Alexander Kanavin Signed-off-by: Alexandre Belloni Signed-off-by: Richard Purdie (cherry picked from commit fd77e356d4507405fde352c8bba7d3842518bbdd) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie

runqemu: Remove potential lock races around tap device handling

2021-07-20T18:05:45+00:00

The qemu tap device handling is potentially race ridden. We pass the fd to the main qemu subprocess which is good as it means the lock is held as long as the qemu process exists. This means we shouldn't unlock it ourselves though, only close the file. We also can't delete the file as we have no idea if qemu is still using it. We could try and obtain an exclusive new lock, then the file would be safe to unlink but it doesn't seem worth it. Also fix the same issue in the port lock code. (From OE-Core rev: 61682a1a8bfe5f7be6e271a4143fa4a02ca5dca9) Signed-off-by: Richard Purdie (cherry picked from commit 2a87bddabf816d09ec801e33972879e6983627eb) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie