linux/poky.git/bitbake/lib/bb/fetch2, branch sumo

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

2020-09-08T13:46:17+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: 1df4fb1c9bf2fde0b274374bff1235c4b1f7ac79) Signed-off-by: Richard Purdie

bitbake: fetch: don't use shell=True when listing ar files

2019-02-25T22:27:46+00:00

(Bitbake rev: d150e50355444b0a67cad4d6a100d9bf6fadb2ae) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

bitbake: fetcher: Fixed remote removal not throwing exception.

2018-10-10T12:26:25+00:00

Before this fix it is assumed that the removal of the remote can only fail because there is not remote to remove. This is a false assumption. Example error which would be ignored: git -c core.fsyncobjectfiles=0 remote rm origin failed with exit code 1, output: Note: A branch outside the refs/remotes/ hierarchy was not removed; to delete it, use: git branch -d master error: could not lock config file config error: Could not remove config section 'remote.origin' Due to the masking of this error a stranger error will be presented to the user, because this time we do not mask the exception: git -c core.fsyncobjectfiles=0 remote add --mirror=fetch origin https://github.com/ptsneves/tl-wn722.git failed with exit code 128, output: fatal: remote origin already exists. The most likely reason that the remote cannot be removed nor modified is that the DL_DIR/git2 does not have permissions compatible with the user running bitbake. This commit fixes: https://bugzilla.yoctoproject.org/show_bug.cgi?id=12728 (Bitbake rev: 67189588a68b9bcb39421ef12103507b4c8820c3) Signed-off-by: Paulo Neves Signed-off-by: Richard Purdie

bitbake: fetch2: fix import error for Python 3.6.5

2018-07-02T10:43:52+00:00

When running bitbake command with Python 3.6.5 always result in import error causing by the change of distutils module. This patch replaces the method to search executable in PATH by "/usr/bin/env ". (Bitbake rev: eb3bdcc9e7cb273de4114367887d1d7df9f036b7) Signed-off-by: Tzu Hsiang Lin Signed-off-by: Richard Purdie

bitbake: fetch2/git: log exception if ls-remote fails

2018-03-28T11:51:52+00:00

(Bitbake rev: 8212446de11c0e370c55f88cde86334b760cd939) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

bitbake: fetch2: Handle missing donestamp file when content is valid

2018-02-14T15:26:03+00:00

In order to allow users to manually populate the download directory with valid content change the assumption that missing the donestamp file means unfetched content. This allows users to populate the download dir without needing to create dummy .done files such that a user does not need a PREMIRROR when using BB_NO_NETWORK to provide valid content files in the download directory. To ensure the correct result this change also fails first if the localpath does not exist. This prevents further parts of the function attempting to calculating the checksum on non-existent files. This also fixes some edge conditions around where if the donestamp exists but the localpath does not it returns, and did not remove the donestamp. Also added test cases to cover this use case and additional use cases where for example the fetcher does not support checksums. (Bitbake rev: a335dbbb65d5b56e71d98cf3e4fa9bfbec1dcde6) Signed-off-by: Nathan Rossi Signed-off-by: Richard Purdie

bitbake: fetch2/npm.py: Fix inverted condition to prevent infinite loop

2018-02-14T15:26:03+00:00

At least the cli-color node module has dependencies that have cyclic dependency among themselves. npm.py is prepared to deal with such a case but the condition is handled only for downloading or not a dependency again, but then it goes checking the its dependency which causes an infinite loop in _getdependencies(). Make this function simply return when a dependency is already downloaded and only download and check its dependencies when not. (Bitbake rev: 545540420112992e53f4a83104af10452df168d0) Signed-off-by: Zoltán Böszörményi Signed-off-by: Richard Purdie

bitbake: fetch/git: Use 'git-make-shallow' from bin directory

2018-02-14T15:26:03+00:00

Move the code that existed in tests/fetch.py for determining the path to 'git-make-shallow' into the git module and reference it. This ensures that 'git-make-shallow' is always available and the desired version regardless of the path variable or whether git exposes the command. (Bitbake rev: 6b508ab8fd5aa796c1c00c970e81e5e93f84d35d) Signed-off-by: Nathan Rossi Signed-off-by: Richard Purdie

bitbake: fetch/git: Add pack-refs command to mirror handling code

2018-01-29T08:50:08+00:00

We've noticed issues on our infrastucture iterating over the many tag/branch/head reference files that some git repositories may contain. By issuing the pack-refs command, we move these all to a single file which speeds up operations with the mirror repos in the downloads directory in general. (Bitbake rev: f8126aaf774186a6eaf0bd4067b89c074594886c) Signed-off-by: Richard Purdie

bitbake: fetch2/init: Disable pseudo in runfetchcmd()

2018-01-08T08:48:54+00:00

If a fetcher, e.g., git, is run when pseudo is active it will think it is running as root. If it in turn uses ssh (as git does), ssh too will think it is running as root. This will cause it to try to read root's ssh configuration from /root/.ssh which will fail. If ssh then needs to ask for credentials it will hang indefinitely as there is nowhere for it to ask the user for them (and even if there was it would not access the correct private keys). The solution to the above is to temporarily disable pseudo while executing any fetcher commands. There should be no reason for them to be executed under pseudo anyway so this should not be a problem. RP Ammendum: We finally did get more information about how to reproduce this problem, something needs to trigger bb.fetch2.get_srcrev() in a pseudo context, for example when AUTOREV is in use or the recipe doesn't have a defined SRCREV. That SRC_URI needs to be using protocol=ssh. This would trigger an ls-remote of the remote repo and if that happens under pseudo, the wrong ssh credentials may be attempted which can hang. [YOCTO #12464] (Bitbake rev: ceaca281cafa662aa2385b95641bce309dce843d) Signed-off-by: Peter Kjellerstedt Signed-off-by: Richard Purdie

linux/poky.git/bitbake/lib/bb/fetch2, branch sumo

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

bitbake: fetch: don't use shell=True when listing ar files

bitbake: fetcher: Fixed remote removal not throwing exception.

bitbake: fetch2: fix import error for Python 3.6.5

bitbake: fetch2/git: log exception if ls-remote fails

bitbake: fetch2: Handle missing donestamp file when content is valid

bitbake: fetch2/npm.py: Fix inverted condition to prevent infinite loop

bitbake: fetch/git: Use 'git-make-shallow' from bin directory

bitbake: fetch/git: Add pack-refs command to mirror handling code

bitbake: fetch2/__init__: Disable pseudo in runfetchcmd()

bitbake: fetch2/init: Disable pseudo in runfetchcmd()