linux/poky.git/bitbake/lib/bb, branch gatesgarth-24.0.2

bitbake: lib/bb/fetch2/init.py: drop _PYTHON_SYSCONFIGDATA_NAME unsetting

2021-02-11T17:49:22+00:00

With introduction of python3targetconfig class in core this is no longer needed. (Bitbake rev: 0a3bf681530bd63fc0036ca81ef868ab53fde56c) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie (cherry picked from commit 47b64cfacd7c498ef9ed5486d117f2d69a39f225) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie

bitbake: fetch/git: download LFS content too during do_fetch

2021-02-02T15:51:56+00:00

Insert an explicit pass to fetch all blobs needed by Git LFS, during the fetch() function. This avoids the default behavior of Git LFS to wait until 'git checkout' to begin downloading the blobs pointed to by LFS records. Network access is not allowed at that point in the recipe's lifecycle. [YOCTO #14191] (Bitbake rev: c73f8f2f4a6491c6bea54839630af6994c27ad24) Signed-off-by: Matt Hoosier Signed-off-by: Richard Purdie (cherry picked from commit 0efac66043662e7a2027192f50e92e982db2ba1c) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie

bitbake: data_smart: Ensure hash reflects vardepvalue flags correctly

2021-01-26T15:45:09+00:00

The get_hash() function is used to decide if the base configuration has changed and hence whether a reparse is required. The vardepvalue flag's value was not expanded but it is often used in contexts like: METADATA_REVISION = "${@base_detect_revision(d)}" METADATA_REVISION[vardepvalue] = "${METADATA_REVISION}" which in it's unexpanded form means reparsing doesn't happen when it should as the data appears unchanged. Update get_hash to expand the values of vardepvalue so reparsing works as expected. This avoids basehash mismatch errors such as the one recently caused by using METADATA_REVISION in poky.conf's DISTRO_VERSION variable. The issue there could be exposed by a recipe using DISTRO_VERSION with the sequence: bitbake os-release bitbake os-release -C install which was caused because METADATA_REVISION changed but the metadata didn't reparse. (Bitbake rev: cb7277e7bb3a440968fdb918d56fe8fa17bca2e6) Signed-off-by: Richard Purdie

bitbake: main: Handle cooker daemon startup error

2020-10-26T22:12:42+00:00

On startup, bitbake spawns a cooker daemon and waits for it's acknowledgement signal. If the acknowledgement doesn't happen in time,the bitbake object will fail to initialize and exit. The error that occurs in this case isn't handled by the existing try - catch block because SystemExit inherits from a different base Exception class. This commit adds SystemExit to the list of expected bitbake server startup errors. [YOCTO #13993] (Bitbake rev: fec2b85689bba1d26ad6f376bc11cc29bb27cbe5) Signed-off-by: Stacy Gaikovaia Signed-off-by: Richard Purdie

bitbake: tests/fetch: Update upstream master->main branchname transition

2020-10-26T22:06:37+00:00

(Bitbake rev: 8b9471e02528320f6ef8d35840b5618883e85447) Signed-off-by: Richard Purdie

bitbake: bitbake: Bump version to 1.48.0 ready for the new release

2020-10-19T22:43:09+00:00

(Bitbake rev: f421de9effc2ba40145373881d20b8e823cf23f8) Signed-off-by: Richard Purdie

bitbake: ui/toasterui: Fix startup faults from incorrect event sequencing

2020-10-17T11:36:14+00:00

Toaster has been failing to start correctly when in interactive mode. The issue is due to setEventMask being called (which triggers parsing) before the environment has been sent from the UI over to the server. This means PATH isn't setup, which causes the sanity checks on HOSTTOOLS to fail in base.bbclass. The fix is to ensure the environment is sent to the server before other commands are run. The pain in debugging this highlights other improvements to the logging are needed. [YOCTO #14079] Reviewed-by: Tim Orling Tested-by: Tim Orling (Bitbake rev: a8efff5c83cd5a25f4b6720e6414a7aa35d04bc7) Signed-off-by: Richard Purdie

bitbake: lib/bb/ui/knotty: fix typo in parseprogress

2020-10-17T11:36:14+00:00

After parseprogress.finish() it was intended to set parseprogress to None, but a typo means this is not happening. (Bitbake rev: f504d6f6598f62aa20fbf69c30fea95569858edb) Signed-off-by: Tim Orling Signed-off-by: Richard Purdie

bitbake: bitbake: fetch/git: use shlex.quote() to support spaces in SRC_URI url

2020-10-17T11:36:14+00:00

This commit replaces the instances where escaped double quotes are used to support SRC_URI url containing spaces with the more pythonic shlex.quote(). (Bitbake rev: 4f9ba9c794de55bea0343267467bddea99844374) Signed-off-by: Charlie Davies Signed-off-by: Richard Purdie

bitbake: process: Show command exceptions in the server log as well

2020-10-11T12:44:26+00:00

There are autobuilder logs where the server commands are failing but we have no debug info in the server log. Improve this to try and understand what is failing. (Bitbake rev: 04d3a79226c9ea448b22f4efbab33876a72c9bdb) Signed-off-by: Richard Purdie

linux/poky.git/bitbake/lib/bb, branch gatesgarth-24.0.2

bitbake: lib/bb/fetch2/__init__.py: drop _PYTHON_SYSCONFIGDATA_NAME unsetting

bitbake: fetch/git: download LFS content too during do_fetch

bitbake: data_smart: Ensure hash reflects vardepvalue flags correctly

bitbake: main: Handle cooker daemon startup error

bitbake: tests/fetch: Update upstream master->main branchname transition

bitbake: bitbake: Bump version to 1.48.0 ready for the new release

bitbake: ui/toasterui: Fix startup faults from incorrect event sequencing

bitbake: lib/bb/ui/knotty: fix typo in parseprogress

bitbake: bitbake: fetch/git: use shlex.quote() to support spaces in SRC_URI url

bitbake: process: Show command exceptions in the server log as well

bitbake: lib/bb/fetch2/init.py: drop _PYTHON_SYSCONFIGDATA_NAME unsetting