linux/poky.git/bitbake/lib, branch gatesgarth

bitbake: tests/fetch: Handle upstream master -> main branch change

2022-04-20T16:27:13+00:00

(Bitbake rev: 38bff0badf916098732fb20210e0ed6d0dd38250) Signed-off-by: Richard Purdie

bitbake: fetch/wget: Add timeout for checkstatus calls (30s)

2021-11-11T11:04:25+00:00

We had an issue where a webserver serving sstate had filesystem issues so would accept connections but effectively not do anything with them. This causes bitbake to hang whilst processing things like sstate objects inside the checkstatus() calls. It can be replicated by setting up a server like: socat -u TCP4-LISTEN:NNN,fork OPEN:/dev/null and pointing SSTATE_MIRRORS in OE at that address. Adding a timeout to the checkstatus calls of 30s means that whilst the system will pause, it will then continue and not hang entirely. Since there isn't a large transfer here, 30s should be a reasonable response time after which we should fall back to building things ourselves. [YOCTO #13716] (Bitbake rev: 92bb53adf47b95182e763a41cd6f4f920250e7b7) Signed-off-by: Richard Purdie

bitbake: fetch/git: Handle github dropping git:// support

2021-11-03T11:31:37+00:00

github is dropping support for git protocol in Git urls. Add code to remap this to https in a way that could be used in older bitbake versions. (Bitbake rev: 44320ce7a2bfd5126de2f83a1a1102a3e4485f69) Signed-off-by: Richard Purdie

bitbake: test/fetch: Update urls to match upstream branch name changes

2021-10-19T21:28:07+00:00

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

bitbake: tests/fetch2: Use our own git server for dtc test repo

2021-09-22T21:45:34+00:00

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

bitbake: providers: replace newly added logger.warn() with logger.warning()

2021-08-02T20:34:54+00:00

Commit https://git.openembedded.org/bitbake/commit/?id=78cd63285713fde59506eb2e71a7b7ee59a594ff converted logger.info() to logger.warn(), which is deprecated and instead should use logger.warning(): https://lists.openembedded.org/g/bitbake-devel/topic/82742194#12377 (Bitbake rev: 247aaf02fa29dee3cf839dc9dcb5674c866aef7b) Signed-off-by: Denys Dmytriyenko Signed-off-by: Richard Purdie

bitbake: data_smart: Allow colon in variable expansion regex

2021-07-30T13:38:30+00:00

Now that ":" is a valid character in variable key names, it needs to be allowed by the variable expansion code too, to match. (Bitbake rev: 14ae61205111383d5f609519c02476925184f6d1) Signed-off-by: Richard Purdie

bitbake: data_smart/parse: Allow ':' characters in variable/function names

2021-07-30T13:38:30+00:00

It is becomming increasingly clear we need to find a way to show what is/is not an override in our syntax. We need to do this in a way which is clear to users, readable and in a way we can transition to. The most effective way I've found to this is to use the ":" charater to directly replace "_" where an override is being specified. This includes "append", "prepend" and "remove" which are effectively special override directives. This patch simply adds the character to the parser so bitbake accepts the value but maps it back to "_" internally so there is no behaviour change. This change is simple enough it could potentially be backported to older version of bitbake meaning layers using the new syntax/markup could work with older releases. Even if other no other changes are accepted at this time and we don't backport, it does set us on a path where at some point in future we could require a more explict syntax. I've tested this patch by converting oe-core/meta-yocto to the new syntax for overrides (9000+ changes) and then seeing that builds continue to work with this patch. (Bitbake rev: aa9f7b80cfdb1119050af469a07ebd949829026c) Signed-off-by: Richard Purdie

bitbake: BBHandler: Don't classify shell functions that names start with "python*" as python function

2021-07-30T13:38:30+00:00

If shell function name starts with 'python' or 'fakeroot' parser wrongly assumes it's python/fakeroot function. [YOCTO #14204] Use regex lookahead assertions to check if 'python' expression is followed by whitespace or '(' and if 'fakeroot' is followed by whitespace. (Bitbake rev: 9bddcd4824ed94915a2b7cf96a13d4ada01c7f9d) Signed-off-by: Tomasz Dziendzielski Signed-off-by: Richard Purdie

bitbake: bitbake: providers: selected version not available should be a warning

2021-05-13T12:11:55+00:00

If the selected version if not available, bitbake will happily attempt to build something else. This should be a loud warning not a small note. (Bitbake rev: 78cd63285713fde59506eb2e71a7b7ee59a594ff) (Bitbake rev: a1987f240cdedc6a44bf255a3a76879aa4cd1cd3) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie