linux/poky.git/scripts, branch mickledore

wic: bootimg-partition: Fix file name in debug message

2023-10-25T14:51:01+00:00

Debug message about using custom configuration file includes file name with incorrect extension. Correct file name to "extlinux.conf". (From OE-Core rev: bb063e8b461b8c3c0b5b6965f26a555781dc94b7) Signed-off-by: Daniel Semkowicz Signed-off-by: Richard Purdie (cherry picked from commit dd63e1520454b2d53a48b72eaae126059af9809b) Signed-off-by: Steve Sakoman

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

2023-10-18T15:25:19+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: 93e864a23e3f82edc2b2fa2207b2bc4b56c230a9) Signed-off-by: Alexander Kanavin Signed-off-by: Alexandre Belloni (cherry picked from commit 38d7a2e45b883cf999a86af05bcc0eaa875bb47c) Signed-off-by: Steve Sakoman

runqemu: check permissions of available render nodes as well as their presence

2023-10-18T15:25:19+00:00

qemu itself is not helpful when render nodes exist, but can't be opened: qemu-system-x86_64: egl: render node init failed To fix this, users likely need to * modprobe vgem (presence when physical graphic card is absent or has a driver without support for render nodes, such as many older cards found in server machines) * add their user to "render" group to write to /dev/dri/renderD* (permissions) With this change runqemu should print hints for the above as appropriate from probing the nodes. (From OE-Core rev: 12ae43abbc4e7d6184198a912487ace3a4e66e50) Signed-off-by: Alexander Kanavin Signed-off-by: Alexandre Belloni (cherry picked from commit acd85925cb197b7a31a25b60e8de762e2c3697ef) Signed-off-by: Steve Sakoman

nativesdk-intercept: Fix bad intercept chgrp/chown logic

2023-10-18T15:25:19+00:00

Running either of these ends up corrupting the os.execv args. If we run: ./scripts/nativesdk-intercept/chown -R foo:foo bar The loop here ends up missing the conversion of foo:foo to root:root because it sees sys.argv[0] and assumes that it's the user:group argument and that we should convert that. We end up a os.execv(path, args) that have the following args: ['root:root', '-R', 'foo:foo', 'bar'] As os.execv ignores args[0], we can just populate it with sys.argv[0] and then loop through sys.argv[1:]. As both chgrp and chown would have either flags and USER[:GROUP] next, this fixes the issue. (From OE-Core rev: e27982afaed33e5823962f7fefe6f709c10e9107) Signed-off-by: Eilís 'pidge' Ní Fhlannagáin Signed-off-by: Richard Purdie (cherry picked from commit 2a75f647ec7696d353f4b09099d777ba53f34d36) Signed-off-by: Steve Sakoman

oe-depends-dot: improve '-w' behavior

2023-10-04T15:21:28+00:00

The '-w' option is not giving very helpful information. For example, if we add 'spice' to IMAGE_INSTALL, bitbake -g core-image-minimal, and then run `oe-depends-dot -k nspr -w task-depends.dot', the result is: $ oe-depends-dot -k nspr -w task-depends.dot Because: core-image-minimal nss core-image-minimal -> nss -> nspr The result is not showing the full dependency chain which brings in nspr. With this patch, the result is: $ oe-depends-dot -k nspr -w task-depends.dot Because: core-image-minimal nss libcacard spice core-image-minimal -> spice -> libcacard -> nss -> nspr This patch also fixes a typo in help message: recipe-depends.dot -> task-depends.dot. (From OE-Core rev: 275410d3cc78acb66e9c7a6d529a58ac38581c8d) Signed-off-by: Chen Qi Signed-off-by: Alexandre Belloni (cherry picked from commit 222302810c472c8eb2efceaa757a253dcac5618f) Signed-off-by: Steve Sakoman

wic: fix wrong attempt to create file system in upartitioned regions

2023-09-04T14:13:25+00:00

The kickstart parser defaults fstype to "vfat". This leads to an attempt to create an empty file system even for regions configured with "--no-table" if used without fstype when no --sourceparams given. The fix tests for fstype "none" or no_table in Partition prepare method. This will omit the file system creation an the potential error for small region with --no-table option. (From OE-Core rev: 47b395fe2dc393e82d0a42cfab96d134c1397a43) Signed-off-by: Markus Niebel Signed-off-by: Alexandre Belloni Signed-off-by: Richard Purdie (cherry picked from commit db771a4cd36bf291a8b68edfd905e03243f2c8b3) Signed-off-by: Steve Sakoman

resulttool/report: Avoid divide by zero

2023-08-30T14:52:36+00:00

Avoid a divide by zero traceback if unfortunate test counts are encountered. (From OE-Core rev: a46782c9f54bcb0389ea1016e37b6939aae79bfb) Signed-off-by: Richard Purdie (cherry picked from commit c5aeea53dfacb53dedb8445cb3523dc3a8cb6dca) Signed-off-by: Steve Sakoman

scripts/create-pull-request: update URLs to git repositories

2023-08-30T14:52:36+00:00

Also remove the git.pokylinux.org URL, no longer used. (From OE-Core rev: ec2bed2e82eb65b3278a6740b54973b78fe236c8) Signed-off-by: Michael Opdenacker Signed-off-by: Alexandre Belloni Signed-off-by: Richard Purdie (cherry picked from commit 47b88d143c2fc61ce0e03b7eb3a9dbcffadbf5b1) Signed-off-by: Steve Sakoman

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

2023-08-18T13:57:05+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: 814672f886b5859524dcc0c285d916a1ccca6605) Signed-off-by: Alexander Kanavin Signed-off-by: Alexandre Belloni Signed-off-by: Richard Purdie (cherry picked from commit b25e922b271794906b22450c7e6cc18fcab51ff8) Signed-off-by: Steve Sakoman

scripts/resulttool: add mention about new detected tests

2023-08-15T16:18:49+00:00

Some regression reports show a lot of "PASSED->None" transitions. When such big lot of identical transitions are observed, it could be that tests are now failing, but it could also be that some tests has been renamed. To detect such case, add a log in regression report to report the number of new tests (i.e: tests that are present in target results but not in base result). This new log also allows to know about newly added tests bases (From OE-Core rev: 7e393ea6e46060daf3242f2f7721f7f968945122) Signed-off-by: Alexis Lothoré Signed-off-by: Alexandre Belloni (cherry picked from commit 01b5cefd07e01c7407bc663842b8a8d502358a6d) Signed-off-by: Steve Sakoman