linux/poky.git/scripts/lib/devtool, branch nanbield

devtool: deploy: provide max_process to strip_execs

2024-01-31T14:10:24+00:00

Use oe.utils.get_bb_number_threads to get max_process (From OE-Core rev: 162607e3f7fd490c4b01775a9516a1bcf643eae6) Signed-off-by: Clay Chang Signed-off-by: Alexandre Belloni Signed-off-by: Richard Purdie (cherry picked from commit f0056dca0a44c374f1f0c5fccbf66ae88e0b1850) Signed-off-by: Steve Sakoman

devtool: modify: Handle recipes with a menuconfig task correctly

2024-01-27T18:09:47+00:00

This avoids the following error when running `devtool modify` on a recipe that has a menuconfig task, but does not have KCONFIG_CONFIG_ENABLE_MENUCONFIG set. .../temp/run.do_configure.4163366: line 152: ${@ oe.types.boolean('${KCONFIG_CONFIG_ENABLE_MENUCONFIG}') }: bad substitution WARNING: .../temp/run.do_configure.4163366:152 exit 1 from '[ ${@ oe.types.boolean('${KCONFIG_CONFIG_ENABLE_MENUCONFIG}') } = True ]' (From OE-Core rev: 91192e861f0f764799f0ae9943cf387b18c70820) Signed-off-by: Peter Kjellerstedt Signed-off-by: Richard Purdie (cherry picked from commit e87e6fa84a0c4b5ac8e736dc62f6e08390ba2436) Signed-off-by: Steve Sakoman

devtool: finish/update-recipe: restrict mode srcrev to recipes fetched from SCM

2024-01-04T14:09:44+00:00

When specifying --mode / -m srcrev with devtool finish/update-recipe on recipes that are not fetched from a SCM repository we get the following error: Traceback (most recent call last): [..] File "<...>/poky/meta/lib/oe/patch.py", line 49, in runcmd raise CmdError(cmd, exitstatus >> 8, "stdout: %s\nstderr: %s" % (stdout, stderr)) oe.patch.CmdError: Command Error: 'sh -c 'git format-patch --no-signature --no-numbered INVALID -o /tmp/oepatchbj7pfmzj -- .'' exited with 0 Output: stdout: stderr: fatal: bad revision 'INVALID' Fix this by adding a check and abort with a proper error message. (From OE-Core rev: 9254b08fbfba3734d5bc717a382d909595833db1) Signed-off-by: Julien Stephan Signed-off-by: Alexandre Belloni Signed-off-by: Richard Purdie (cherry picked from commit 5b77f60e85d07921ae5e808daa1fd7d8c3dc40ea) Signed-off-by: Steve Sakoman

devtool: fix update-recipe dry-run mode

2024-01-04T14:09:44+00:00

When running devtool update-recipe with --mode=srcrev AND --append switch in dry-run, we get the following error: Traceback (most recent call last): [...] Exception: destpath should be set here Fix this by removing a misplaced else statement in _update_recipe_srcrev (From OE-Core rev: edfa2aac5c39e12e1149134a6241ad4e5b2ebc46) Signed-off-by: Julien Stephan Signed-off-by: Alexandre Belloni (cherry picked from commit 85ba125703d5b442133fd7c470b915460ee68ac9) Signed-off-by: Steve Sakoman

devtool/upgrade: check all git config locations

2023-10-08T12:05:25+00:00

Fixes [YOCTO #15222] In some situations its more practical to keep git configuration at `/etc/gitconfig` instead of `$HOME/.gitconfig` (e.g., when mounting git configuration into a docker container). This change makes `devtool upgrade` consider any available git configuration instead of only checking `--global`. (From OE-Core rev: 30a9f7de45050c8bac49d4b37419cc2e067a75fa) Signed-off-by: Marcus Flyckt Signed-off-by: Alexandre Belloni Signed-off-by: Richard Purdie

recipetool/devtool: Ensure server knows about changed files

2023-09-18T10:35:38+00:00

Bitbake has changed to require notification when metadata changes in the middle of tinfoil sessions. Add the required function calls at the places metadata is changed. (From OE-Core rev: e5574163ab49a8f51b2b34fd37acfd1cad9b7595) Signed-off-by: Richard Purdie

devtool/build_sdk: Drop unused imports

2023-09-18T07:53:10+00:00

Drop some unused imports. (From OE-Core rev: 432446ef402ff42fe0c90172b77376fa5981524a) Signed-off-by: Richard Purdie

build-sysroots: target or native sysroot population need to be selected explicitly

2023-09-09T11:04:55+00:00

Running them in parallel is prone to races as postinsts from target sysroots rely on executables from native sysroots which may or may not be fully prepared yet. This was observed for example here: https://autobuilder.yoctoproject.org/typhoon/#/builders/146/builds/468/steps/12/logs/stdio https://autobuilder.yoctoproject.org/typhoon/#/builders/147/builds/467/steps/12/logs/stdio (From OE-Core rev: 38d7a2e45b883cf999a86af05bcc0eaa875bb47c) Signed-off-by: Alexander Kanavin Signed-off-by: Alexandre Belloni Signed-off-by: Richard Purdie

devtool/upgrade: raise an error if extracting source produces more than one directory

2023-08-04T10:44:28+00:00

This can happen if running unpack task produces unrelated files and directories (e.g. if recipe_qa or other tasks run); in this case it's better to stop, rather than allow devtool to continue and error out much later with a message that has nothing to do with where the problem originated. The idea here was to handle tarballs that don't contain a top level directory and thus the source tree is one level up; this basically never happens, and if it does we should find a less brittle way to handle such tarballs. (From OE-Core rev: b25e922b271794906b22450c7e6cc18fcab51ff8) Signed-off-by: Alexander Kanavin Signed-off-by: Alexandre Belloni Signed-off-by: Richard Purdie

devtool: do not run recipe_qa task when extracting source

2023-07-30T08:16:52+00:00

The immediate reason is that the task is sstate enabled, and due to the way devtool sets up source extraction this causes bogus values to appear in tmp/sstate-control/index-* files. Also, recipe_qa may contain hard failures in the future, and it would be counterproductive for the failures to prevent devtool workflows (which may perhaps be about fixing the failure). An alternative would have been to not insert recipe_qa task before fetch task, but that would greatly delay the checks in larger bitbake builds, and it's better to run them as early as possible. (From OE-Core rev: 6f9db3f8de3dca9b0c87382561c70857d5b39e0f) Signed-off-by: Alexander Kanavin Signed-off-by: Alexandre Belloni Signed-off-by: Richard Purdie