linux/poky.git/bitbake/lib/bb/fetch2/git.py, branch 3.3_M1

bitbake: fetch2/git: Document that we won't support passwords in git urls

2020-11-03T08:21:10+00:00

This keeps coming up, document why we don't do this and the alternatives. (Bitbake rev: aded964eed4ce5a725ed1ab477efabc86b1aa481) 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: bitbake: fetch/git: add support for SRC_URI containing spaces in url

2020-09-23T19:55:53+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: eb38b6f0935763f7ba19e5618f376fcae1dac41a) Signed-off-by: Charlie Davies Signed-off-by: Richard Purdie

bitbake: fetch2: Change git fetcher not to destroy old references

2020-07-12T10:53:00+00:00

It looks like we're about to see a lot of changes in branch names in repos. If we have the prune option here, those old names are lost, the changes propagate to our source mirrors and our old releases break. We have the force option so any replaced references should be replaced, its only orphaned branches which will now be preserved. I believe this behaviour will cause us fewer problems given the changes that look likely to happen. (Bitbake rev: 820ab886e79eea516560c0c008e4cf059c6e11a3) Signed-off-by: Richard Purdie

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

2020-06-04T12:28:16+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: 4fa67c2af830035a1ddedc14592ee25a15ebff22) Signed-off-by: Mauro Queiros Signed-off-by: Richard Purdie

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

2020-06-04T12:28:16+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: 45028dfda5a29a34ab408cb3f11d72ae17963340) Signed-off-by: Mauro Queiros Signed-off-by: Richard Purdie

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

2020-06-04T12:28:16+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: 646d86df7de774255246a3d7051c308e43eb257d) Signed-off-by: Mauro Queiros Signed-off-by: Richard Purdie

bitbake: fetch2/git: _revision_key: collapse adjacent slashes

2020-01-19T13:31:05+00:00

>From a SRCREV caching point of view, there is no reason to treat the following upstreams as different: SRC_URI = "git://github.com/file/file.git" SRC_URI = "git://github.com//file/file.git" (Bitbake rev: 425e21c14955dd38868c6e97637df3bbe0f89fac) Signed-off-by: Chris Laplante Signed-off-by: Richard Purdie

bitbake: lib: amend code to use proper singleton comparisons where possible

2020-01-19T13:31:05+00:00

amend the code to handle singleton comparisons properly so it only checks if they only refer to the same object or not, and not bother comparing the values. (Bitbake rev: b809a6812aa15a8a9af97bc382cc4b19571e6bfc) Signed-off-by: Frazer Clews Signed-off-by: Richard Purdie

bitbake: fetch2/git: fetch shallow revs when needed

2019-10-28T05:31:53+00:00

When bitbake determines if a git clone needs updating, it only checks for the needed srcrevs, not the revs listed in BB_GIT_SHALLOW_REVS, which will fail if using shallow and the needed rev was added to the upstream git repo after a previous fetch. Ensure that we also check for shallow revs. [YOCTO #13586] (Bitbake rev: 93b65e3c6ca64f644946953980595c44fbbcc748) Signed-off-by: Christopher Larson Signed-off-by: Richard Purdie