linux/poky.git/bitbake/lib, branch yocto-3.1.6

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

2021-02-18T16:48:28+00:00

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

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

2021-02-05T12:18:38+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: 2351b496bb63b96920d4ae67bec816f00d510df2) Signed-off-by: Matt Hoosier Signed-off-by: Richard Purdie (cherry picked from commit 0efac66043662e7a2027192f50e92e982db2ba1c) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

bitbake: git.py: Use the correct branch to check if the repository has LFS objects.

2021-02-05T12:18:38+00:00

Function "contains_lfs" was only looking at the master branch when searching for LFS content. LFS may be configured in specific branches only, so we need to use the correct branch. (Bitbake rev: 274f790ac9161187810df3242d3570261e407b11) Signed-off-by: Mauro Queiros Signed-off-by: Richard Purdie (cherry picked from commit 4fa67c2af830035a1ddedc14592ee25a15ebff22) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

bitbake: git.py: LFS bitbake note should not be printed if need_lfs is not set.

2021-02-05T12:18:38+00:00

The message "Repository %s has LFS content but it is not being fetched" was being printed, even when Git-LFS was available and "lfs=1" was set. In those situations, we want to fetch LFS content, so that message would not make sense. (Bitbake rev: 2795c6150c0b3218716195c0d10ff2843b1ef695) Signed-off-by: Mauro Queiros Signed-off-by: Richard Purdie (cherry picked from commit 45028dfda5a29a34ab408cb3f11d72ae17963340) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

bitbake: git.py: skip smudging if lfs=0 is set

2021-02-05T12:18:38+00:00

Git-LFS objects were being fetched even when lfs=0 was not set. This patch disables LFS smudging when lfs=0. That way, only the LFS pointers are downloaded during checkout. (Bitbake rev: 3d09608cabd404733b95ea92d5b00830ded77834) Signed-off-by: Mauro Queiros Signed-off-by: Richard Purdie (cherry picked from commit 646d86df7de774255246a3d7051c308e43eb257d) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

bitbake: data_smart: Ensure hash reflects vardepvalue flags correctly

2021-01-26T15:45:14+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: 418c00c570a60845556204b4f52de047b284dd8e) Signed-off-by: Richard Purdie

bitbake: taskexp: update for GTK API changes

2020-12-01T22:05:12+00:00

The introspected API for GtkTreeModel and friends had some unexpected quirks which have now been fixed, see[1] for details. However, for example Ubuntu 20.04 has the fixed GTK but not an updated pygobject which means taskexp raises an exception on startup. Solve by manually looking at what functions are present and calling the right one. [ YOCTO #14055 ] [1] https://gitlab.gnome.org/GNOME/pygobject/-/commit/9cdbc56fbac4db2de78dc080934b8f0a7efc892a (Bitbake rev: d171188cf966852326916f726cbd3ca9627b831c) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie (cherry picked from commit ac7d1114a7e99e6efd6a37b03d170faf678513fb) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

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

2020-10-26T22:18:51+00:00

(Bitbake rev: 89fc9450abefd682266efcbfa031d1ef115ff1a7) Signed-off-by: Richard Purdie

bitbake: bitbake: tests/fetch: add unit tests for SRC_URI with spaces in url

2020-10-13T08:40:10+00:00

(Bitbake rev: d8daad57bdbceec041c4c2d288ed5d487ad8e6dc) Signed-off-by: Charlie Davies Signed-off-by: Richard Purdie (cherry picked from commit e7dab75c8d1923abcbbc7c9ac7de215d720ccf26) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

bitbake: bitbake: fetch/git: add support for SRC_URI containing spaces in url

2020-10-13T08:40:10+00:00

Microsoft's TFS VCS system allows for spaces in a git repository url. An example of a valid url is: ssh://tfs-my-company.org:22/tfs/My Projects/FooBar This commit adds support for such urls by implementing two changes. Firstly, when bitbake makes a git command line call the url is surrounded by quotes so that the url, regardless of spaces, is treated as one argument. Secondly, additional parsing of various filepath variables, which are based off of the url, are now completed with any spaces in the url replaced with underscores. (Bitbake rev: c4a51b7f4fd8a3c7d63c184675c014ec955d2606) Signed-off-by: Charlie Davies Signed-off-by: Richard Purdie (cherry picked from commit eb38b6f0935763f7ba19e5618f376fcae1dac41a) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

linux/poky.git/bitbake/lib, branch yocto-3.1.6

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

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

bitbake: git.py: Use the correct branch to check if the repository has LFS objects.

bitbake: git.py: LFS bitbake note should not be printed if need_lfs is not set.

bitbake: git.py: skip smudging if lfs=0 is set

bitbake: data_smart: Ensure hash reflects vardepvalue flags correctly

bitbake: taskexp: update for GTK API changes

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

bitbake: bitbake: tests/fetch: add unit tests for SRC_URI with spaces in url

bitbake: bitbake: fetch/git: add support for SRC_URI containing spaces in url

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