linux/poky.git/bitbake, branch langdale

bitbake: fetch/git: Fix local clone url to make it work with repo

2023-04-14T16:51:44+00:00

The "git clone /path/to/git/objects_symlink" couldn't work after the following change: https://github.com/git/git/commit/6f054f9fb3a501c35b55c65e547a244f14c38d56 But repo command manages the git repo as symlinks, so check whether the objects is an symlink to fix the problem: * Nothing is changed if git/objects is not a symlink * Use "git clone file://" when git/objects is a symlink (Bitbake rev: 5b105e76dd7de3b9a25b17b397f2c12c80048894) Signed-off-by: Robert Yang Signed-off-by: Richard Purdie (cherry picked from commit a0d8108eba8d542707740d00c66c1c5f5b963f18) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie Signed-off-by: Steve Sakoman

bitbake: toaster: Add refreshed oe-core and poky fixtures

2023-03-15T23:15:31+00:00

After updating gen_fixtures.py, run ./gen_fixtures.py --all This includes the latest stable/supported releases. (Bitbake rev: 88a9cc0318c6ef01976d8b09dfc1a92cf0a1e498) Signed-off-by: Tim Orling Signed-off-by: Richard Purdie

bitbake: toaster: fixtures/gen_fixtures.py: update branches

2023-03-15T23:15:31+00:00

Re-introduce Dunfell since it is supported until April 2024 Drop Honister and Hardknott as they are both EOL Add Langdale as it is the latest stable release (Bitbake rev: 2dda597de3fcf6911e4022a8c279ae00413ec747) Signed-off-by: Tim Orling Signed-off-by: Richard Purdie

bitbake: toaster: fixtures/README: django 1.8 -> 3.2

2023-03-15T23:15:31+00:00

We should reference the docs for the current LTS version we are using. (Bitbake rev: add4569195f8f64000555679e282b0b12d1ca3f8) Signed-off-by: Tim Orling Signed-off-by: Richard Purdie

bitbake: cookerdata: Drop dubious exception handling code

2023-03-14T15:25:03+00:00

This code appears to be dangerous, it swallows exceptions, turning them into "handled" versions which then show no errors to the user. This is a pretty poor user experience and I can't see why this code should be swallowing such things. Drop the worst bits of code. (Bitbake rev: 2b239555f76e4e98ca704e7ef60e796d0f19463c) Signed-off-by: Richard Purdie Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

bitbake: cookerdata: Improve early exception handling

2023-03-14T15:25:03+00:00

Martin Jansa reported that if you put a syntax error into an imported module such as qa.py in OE, no error is shown. Part of the issue appears to be that the catch_parse_error() decorator only catches certain exceptions and SyntaxError isn't one of them. As far as I can tell we should remove all the special cases and use the more advanced code in all cases, not just expansion errors. I confirmed this now prints a proper error message for a qa.py syntax error. (Bitbake rev: 4b922345a40f7cc803eb46c4906269691d408940) Signed-off-by: Richard Purdie Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

bitbake: cookerdata: Remove incorrect SystemExit usage

2023-03-14T15:25:03+00:00

Calling SystemExit doesn't work well with server/client usage since the string isn't printed to the right place. Use bb.fatal() instead which prints the right log output and raises and handled exception which then shows correctly on the UI. (Bitbake rev: 8001c9b5d3a3111f1134557f221325fe2593c2d9) Signed-off-by: Richard Purdie Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

bitbake: utils: Allow to_boolean to support int values

2023-03-14T15:25:03+00:00

Some variables may be set as: X = 1 as well the more usual X = "1" so add support to to_boolean to handle this case. (Bitbake rev: 3cc9fe911f764e4553078dbeed9497f6f08336ce) Signed-off-by: Richard Purdie Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

bitbake: bin/utils: Ensure locale en_US.UTF-8 is available on the system

2023-03-14T15:25:03+00:00

Get rid of the duplicate code and add extra check that the locale en_US.UTF-8 is available on the system. This new helper method is now located right above the method filter_environment() which sets LC_ALL environment variable to 'en_US.UTF-8'. [YOCTO #10165] (Bitbake rev: 2fe0c90da89b0a4e2e133f8ffa7a93d71097bb32) Signed-off-by: Frank de Brabander Signed-off-by: Richard Purdie (cherry picked from commit a4ce040a6fd540a1cac52f808f909f9fcf8c961c) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

bitbake: siggen: Fix inefficient string concatenation

2023-02-17T15:05:12+00:00

As discussed in https://stackoverflow.com/a/4435752/1710392 , CPython has an optimization for statements in the form "a = a + b" or "a += b". It seems that this line does not get optimized, because it has a form a = a + b + c: data = data + "./" + f.split("/./")[1] For that reason, it does a copy of data for each iteration, potentially copying megabytes of data for each iteration. Changing this line causes SignatureGeneratorBasic::get_taskhash to take 0.06 seconds instead of 45 seconds on my test setup where SRC_URI points to a big directory. Note that PEP8 recommends explicitely not to use this optimization which is specific to CPython: "do not rely on CPython’s efficient implementation of in-place string concatenation for statements in the form a += b or a = a + b" However, the PEP8 recommended form using "join()" also does not avoid the copy and takes 45 seconds in my test setup: data = ''.join((data, "./", f.split("/./")[1])) I have changed the other lines to also use += for consistency only, however those were in the form a = a + b and were optimized already. Co-authored-by: JJ Robertson (Bitbake rev: 592ee222a1c6da42925fb56801f226884b6724ec) Signed-off-by: Etienne Cordonnier Signed-off-by: Richard Purdie (cherry picked from commit 195750f2ca355e29d51219c58ecb2c1d83692717) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie