linux/poky.git/meta/classes, branch yocto-3.1.16

metadata_scm.bbclass: Use immediate expansion for the METADATA_* variables

2022-04-21T20:26:01+00:00

Define METADATA_BRANCH and METADATA_REVISION using immediate expansion. This avoids running `git rev-parse HEAD` multiple times during recipe parsing. (From OE-Core rev: f76fc325520386c0d25c6d6b422c85e9fb87e663) Signed-off-by: Peter Kjellerstedt Signed-off-by: Richard Purdie (cherry picked from commit 34e1841ec14c545c73fbe03a9f946d43d65ab326) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

license_image.bbclass: close package.manifest file

2022-04-21T20:26:01+00:00

* fixes: NOTE: Executing write_package_manifest ... DEBUG: Executing python function write_package_manifest /OE/build/oe-core/openembedded-core/meta/classes/license_image.bbclass:23: ResourceWarning: unclosed file <_io.TextIOWrapper name='/OE/build/oe-core/tmp-glibc/deploy/licenses/core-image-minimal-qemux86-64/package.manifest' mode='w+' encoding='UTF-8'> 'w+').write(output) ResourceWarning: Enable tracemalloc to get the object allocation traceback DEBUG: Python function write_package_manifest finished [YOCTO #14772] (From OE-Core rev: 3e88c663e65fbc1b2e77a8616af4371224ed0ca5) Signed-off-by: Martin Jansa Signed-off-by: Richard Purdie (cherry picked from commit b3114d5d438b7a63a276b4e825b62f3b1ebceed6) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

mirrors: Add missing gitsm entries for yocto/oe mirrors

2022-04-09T07:27:11+00:00

The missing gitsm:// mappings looks like an oversight, add them. (From OE-Core rev: f748360a854a5c80c8008ba6ac90546865651f10) Signed-off-by: Richard Purdie (cherry picked from commit 6600b9fca7888fb41647cd000b9efb7f0762dfde) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

python3targetconfig: Use for nativesdk too

2022-03-23T23:16:12+00:00

nativesdk is a cross compiled target and therefore should use the target config, not the native one. Copy the target entries accordingly. (From OE-Core rev: e997487c0068bfe4017fc98c4fa5b51f660a1b4e) Signed-off-by: Richard Purdie (cherry picked from commit b1b5fec350b390fa7f2d26966df1411b032faf87) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

sstate: inside the threadedpool don't write to the shared localdata

2022-03-11T23:44:42+00:00

When inside the threadedpool we make a copy of the localdata to avoid some race condition, so we need to use this new localdata2 and stop write the shared localdata. (From OE-Core rev: 604146a242c3d5f5a9872bb756910f4bd1b58406) Signed-off-by: Jose Quaresma Signed-off-by: Richard Purdie (cherry picked from commit 90fe6948a9df0b43c58120a9358adb3da1ceb5b9) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

uninative: Add version to uninative tarball name

2022-03-09T17:30:49+00:00

uninative works via hashes and doesn't need the version in the tarball name but it does make things easier to inspect in DL_DIR. There were reasons such as ease of publication of the build tarballs but we can handle those differently now and the signature issues from the early code aren't an issue now. From 3.4 onwards we can use a version'd name. [YOCTO #12970] (From OE-Core rev: 0ec0e49d0d2a7478efbf20bc3554f0ffba40afa0) Signed-off-by: Richard Purdie (cherry picked from commit dadba70d6a24d8ebb5576598efffa973151c7218) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

buildhistory.bbclass: create the buildhistory directory when needed

2022-03-09T17:30:49+00:00

When the BUILDHISTORY_RESET is enabled we need to move the content from BUILDHISTORY_DIR to BUILDHISTORY_OLD_DIR but when we start a clean build in the first run we don't have the BUILDHISTORY_DIR so the move of files will fail. | ERROR: Command execution failed: Traceback (most recent call last): | File "/xxx/poky/bitbake/lib/bb/command.py", line 110, in runAsyncCommand | commandmethod(self.cmds_async, self, options) | File "/xxx/poky/bitbake/lib/bb/command.py", line 564, in buildTargets | command.cooker.buildTargets(pkgs_to_build, task) | File "/xxx/poky/bitbake/lib/bb/cooker.py", line 1481, in buildTargets | bb.event.fire(bb.event.BuildStarted(buildname, ntargets), self.databuilder.mcdata[mc]) | File "/xxx/home/builder/src/base/poky/bitbake/lib/bb/event.py", line 214, in fire | fire_class_handlers(event, d) | File "/xxx/poky/bitbake/lib/bb/event.py", line 121, in fire_class_handlers | execute_handler(name, handler, event, d) | File "/xxx/poky/bitbake/lib/bb/event.py", line 93, in execute_handler | ret = handler(event) | File "/xxx/poky/meta/classes/buildhistory.bbclass", line 919, in buildhistory_eventhandler | entries = [ x for x in os.listdir(rootdir) if not x.startswith('.') ] | FileNotFoundError: [Errno 2] No such file or directory: '/xxx/buildhistory' (From OE-Core rev: de89dc125758f828a7886012bd9b1c8a1017ef48) Signed-off-by: Jose Quaresma Signed-off-by: Richard Purdie (cherry picked from commit 97bc2168da7dbacdfbf79cd70db674363ab84f6b) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

cml1.bbclass: Handle ncurses-native being available via pkg-config

2022-03-09T17:30:49+00:00

The linux kernel will by default use pkg-config to get ncurses(w) paths, falling back to absolute path checks otherwise. If the build host does not have ncurses installed this will fail as pkg-config will not search the native sysroot for ncurses. To more all kernel/kconfig sources, inject the equivalent native pkg-config variables similar to what is done by the pkg-config-native script. This only affects the menuconfig python task itself and the oe_terminal call inside it. (cherry picked from commit abb95c421bb67d452691819e3f63dabd02e2ba37) (From OE-Core rev: dc6b20475a69c9fbab9a97a93119aeedf54deb23) Signed-off-by: Nathan Rossi Signed-off-by: Richard Purdie Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

Revert "cve-check: add lockfile to task"

2022-03-09T17:30:48+00:00

Now that all of the functions in cve-check open the database read-only, we can remove this lockfile. This means cve-check can run in parallal again, improving runtimes massively. This reverts commit d55fbf4779483d2cfd71df78d0f733b599fef739. (From OE-Core rev: 1a30a8513ca47890470ee9d19a5ea36437e664bf) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie (cherry picked from commit e60d149b41d14d177df20dbecaef943696df1586) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

cve-check: get_cve_info should open the database read-only

2022-03-09T17:30:48+00:00

All of the function in cve-check should open the database read-only, as the only writer is the fetch task in cve-update-db. However, get_cve_info() was failing to do this, which might be causing locking issues with sqlite. (From OE-Core rev: 2b3d13a451e99db669977d4d1172653b736ae6e1) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie (cherry picked from commit 8de517238f1f418d9af1ce312d99de04ce2e26fc) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie