summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
...
* documentation: Fix typo in standards.mdSimon A. Eugster2025-02-071-1/+1
| | | | | | | | (From yocto-docs rev: 9007d7eb63b296aae832028924d89f83dc159992) Signed-off-by: "Simon A. Eugster" <simon.eu@gmail.com> Signed-off-by: Antonin Godard <antonin.godard@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Revert "selftest/sstatetests: run CDN mirror check only once"Richard Purdie2025-02-061-0/+2
| | | | | | | | | | | This reverts commit 0d3901b768272abc2e27ba2ab807dad24917e0cf. We've still having CDN issues so go back to the double attempt to see if this improves things. (From OE-Core rev: 136f0edb75d9601a0ae56e025419d3cddfb90219) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* b4-config: Add basic support for b4 contribution workflowQuentin Schulz2025-02-061-0/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | b4[1] is a very nice tool for mail-based contribution. A config[2] file exists to set up a few defaults. We can use it to provide the Cc and To recipient list for the series. This uses the b4-wrapper-poky.py script for checking that each patch in the series is only for one project. Indeed, poky is actually a "collection" of multiple repositories, namely BitBake, OpenEmbedded-Core and the Yocto Docs. One patch should therefore not make changes in multiple of those projects otherwise it cannot be merged. Additionally, a check is added to make sure that a series only touches files from one project to avoid having to figure out which patch is to be merged by which maintainer in which project repo. Moreover, it is not uncommon to have people develop patches for those projects from within poky. This wrapper figures out which mailing lists to send patches to based on the files that are modified in the series. Considering that patches to the bitbake/doc/ directory need to be sent to both the bitbake and yocto-docs mailing list (To recipient for the former, Cc recipient for the latter) this wrapper handles that. A limitation of the script (lsdiff actually) is that it doesn't know how to handle empty files, but those should be of rather rare occurrences. Note that this script requires hardcoding of paths that are handled by different projects to map files to projects. Anything not mapped is assumed part of OE-Core. [1] https://pypi.org/project/b4/ [2] https://b4.docs.kernel.org/en/latest/config.html Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* scripts: add b4-wrapper for pokyQuentin Schulz2025-02-061-0/+178
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | poky is a combo-layer containing BitBake, OpenEmbedded-Core and Yocto Documentation source code into one big repo. It is not uncommon to have people develop patches for either of those projects from a poky git repo. However, it is unlikely those patches are to be sent to the poky mailing list as very few files contained in the poky git repo actually are poky-specific. So we need a way to identify to which mailing list a patch is destined to be sent. Additionally, because the source code in openembedded-core is merged/imported at the root of the git repo of poky, its .b4-config introduced in the previous commit will be used if not overridden (which will be done in a separate commit specific to the poky git repo). We need to provide a different .b4-config in poky. Therefore, this wrapper is used to identify automatically which mailing list a patch series needs to be sent to (via b4 prep --auto-to-cc) and does some additional checks (via b4 prep --check) such as making sure a patch doesn't modify two different projects at the same time or that multiple projects are modified by different patches in the same patch series. This wrapper script is meant to be used by poky's .b4-config. Ideally the b4 prep --check part could be offloaded to `patchtest` once it supports running on source different from OE-Core. Note that b4 makes sure that an address doesn't appear twice in the recipient list. There's also no priority in the type of recipient list, so if the address appears first in Cc and then in To, only the Cc will be added. The opposite is true as well. (From OE-Core rev: a1d629a0823cf724bda607ef8d88ee4f722c3a08) Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: b4-config: Add basic support for b4 contribution workflowQuentin Schulz2025-02-062-0/+44
| | | | | | | | | | | | | | | | | | | | | | | | | b4[1] is a very nice tool for mail-based contribution. A config[2] file exists to set up a few defaults. We can use it to set the To recipients to always add, in our case the mailing list. This also adds a wrapper script that is called by b4 to figure out which addresses to put as Cc recipients. Considering that patches to the doc/ directory also need to be sent to the yocto-docs mailing list, this wrapper handles that. A limitation of the script (lsdiff actually) is that it doesn't know how to handle empty files, but those should be of rather rare occurrences. Because we currently do not have anything to check for patch validity, remove requirement for b4 prep --check to be run before sending a patch series, via disable-needs-checking in prep-pre-flight-checks. [1] https://pypi.org/project/b4/ [2] https://b4.docs.kernel.org/en/latest/config.html (Bitbake rev: 8843860010c97cc10ff69205d209634639b6c5cd) Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* perl: fix do_install failed for nativesdk-perlhongxu2025-02-061-1/+1
| | | | | | | | | | | | | | | While set 'baselib = "lib64"' for nativesdk, perl do_install failed: | rm: cannot remove 'tmp/work/x86_64-nativesdk-pokysdk-linux/nativesdk-perl/ 5.40.0/image//usr/local/oe-sdk-hardcoded-buildpath/sysroots/x86_64-pokysdk-linux/ usr/lib64/perl5/5.40.0/*/CORE/libperl.so': No such file or directory Refer perl class-target do_configure, explicitly pass option '--libdir=${libdir}' to nativesdk do_configure (From OE-Core rev: 68b368c77198c8f6e5f59e7b8a568645240ae426) Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3: Fix typo in create_manifest3.pyOmri Sarig2025-02-051-1/+1
| | | | | | | | | | Fixed a misspelled "posible" to "possible". (From OE-Core rev: 7e2d743e4809d6cbaa8e441dc42624eb65daad63) Signed-off-by: Omri Sarig <omri.sarig13@gmail.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3: Fix typo in python3-manifest.jsonOmri Sarig2025-02-051-1/+1
| | | | | | | | | | Fix a wrong "the" to be the intended "that". (From OE-Core rev: fe55f05a7068ba7b277a253058fdcc8964222bc1) Signed-off-by: Omri Sarig <omri.sarig13@gmail.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meta: Enable '-o pipefail' for the SDK installerMoritz Haase2025-02-051-0/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | When testing a Yocto SDK installer on Alpine 3.21, we recently ended up with a broken SDK. One of the commands the relocation script calls in a piped multi-command chain failed (see [0]), but the installer did not realize that - since it doesn't use 'set -o pipefail'. Thus, the error was never reported to the user and the installer claimed to have set up the SDK correctly - which wasn't the case. Given that the SDK installer is a POSIX-compliant shell script and that the 'pipefail' option used to be missing from the standard, it's not surprising that it isn't used. Thankfully however, in June of 2024, a new version of POSIX (POSIX.1-2024) was released - and that one finally includes the 'pipefail' option (see [1]). A number of shells already support it, so let's enable it if available to make the SDK installer more robust. The change has been tested locally using SDK installers for internal projects, based on both Kirkstone and Scarthgap. [0]: https://gitlab.alpinelinux.org/alpine/aports/-/issues/16797 [1]: https://pubs.opengroup.org/onlinepubs/9799919799.2024edition/utilities/V3_chap02.html#set (From OE-Core rev: 1cb4b41c7faf77fcc347b1276d86d4288968c926) Signed-off-by: Moritz Haase <Moritz.Haase@bmw.de> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libseccomp: Upgrade 2.5.5 -> 2.6Simone Weiß2025-02-051-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Changelog: - Update the syscall table for Linux v6.13 - Add support for new arches: SuperH little and big endian, LoongArch, and 32-bit Motorola 68000 - Add multiplexed syscall support for more arches: MIPS, SuperH, and PPC - Consolidate and simplify handling of multiplexed syscalls - Add support for the SECCOMP_FILTER_FLAG_WAIT_KILLABLE_RECV flag - Add support for transactions with the seccomp_transaction_start(), seccomp_transaction_commit(), and seccomp_transaction_reject() APIs - Add a seccomp_precompute() API to generate the seccomp BPF filter prior to seccomp_load() or seccomp_export_bpf_mem() - Add support for binary tree filters without syscalls - Add support for the kernel’s implementation change of SECCOMP_IOCTL_NOTIF_ID_VALID - Add Python binding support for retrieving the notification file descriptor - Improved tooling to help track syscall table updates in the Linux kernel - Handle EINVAL error from the kernel when the WAIT_KILLABLE_RECV flag is erroneously provided to the kernel - Fix a seccomp userspace notification issue where the file descriptor was being requested more than once - Fix a bug where the internal filter state could be corrupted when a filter rule addition fails - Fix potential memory leak in the internal management of filter snapshots - Utilize Cython rather than distutils in the Python bindings, due to distutils’ deprecation - Many test and CI improvements and fixes - Many documentation improvements and updates (From OE-Core rev: 549a477660bd6ccda842b4ed34814b53470d08d8) Signed-off-by: Simone Weiß <simone.p.weiss@posteo.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* rust: restore parallel builds, disable lto only for rustdocAlexander Kanavin2025-02-054-28/+47
| | | | | | | | | | | | | | | | | | | | | | | | | | The original reproducibility fix was problematic for a couple reasons: - disabling both lto and parallel builds had an unfortunate effect of nearly doubling rust-native and rust build times (which are slow to begin with). Disabling lto hurts runtime performance too. - both of these things were done for the *entire build*, while the only problematic item is the librustdoc crate. - lto=off option in config.toml has an effect only on building rustc (the compiler itself), and doesn't help with rustdoc reproducibility. Actual fix is the codegen-units setting, which indirectly disables lto via giving llvm only one unit to work with at a time. After some digging, here's a more targeted fix for the problem. Why librustdoc is non-reproducible, but not anything else remains a mystery, hidden deep in rust-llvm's lto optimization code. (From OE-Core rev: a1977407a88a2004c3a6d2dba1d5bfe1aa1664b2) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* rust/README-rust.md: fix markdown style issuesIgor Opaniuk2025-02-051-11/+13
| | | | | | | | | | | | | | | | | | | | Fix markdown style issues using markdownlint tool [1]: $ cat ./meta/recipes-devtools/rust/README-rust.md | mdl (stdin):1: MD002 First header should be a top level header (stdin):25: MD006 Consider starting bulleted lists at the beginning of the line (stdin):3: MD009 Trailing spaces (stdin):11: MD009 Trailing spaces (stdin):26: MD009 Trailing spaces (stdin):39: MD012 Multiple consecutive blank lines (stdin):32: MD032 Lists should be surrounded by blank lines (stdin):36: MD032 Lists should be surrounded by blank lines [1] https://github.com/markdownlint/markdownlint (From OE-Core rev: 62bade83dd6e021f11e9599a2699a1b202324f0f) Signed-off-by: Igor Opaniuk <igor.opaniuk@foundries.io> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* patchtest/README.md: fix markdown style issuesIgor Opaniuk2025-02-051-4/+4
| | | | | | | | | | | | | | | | Fix markdown style issues using markdownlint tool [1]: $ cat ./meta/lib/patchtest/README.md | mdl (stdin):4: MD034 Bare URL used (stdin):8: MD034 Bare URL used (stdin):9: MD034 Bare URL used (stdin):20: MD034 Bare URL used [1] https://github.com/markdownlint/markdownlint (From OE-Core rev: 623cd2ffa8815a60ef630974393b17a1489ebf41) Signed-off-by: Igor Opaniuk <igor.opaniuk@foundries.io> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* SECURITY.md: fix markdown style issuesIgor Opaniuk2025-02-051-8/+8
| | | | | | | | | | | | | | | | | | | Fix markdown style issues using markdownlint tool [1]: $ cat SECURITY.md | mdl (stdin):16: MD013 Line length (stdin):19: MD013 Line length (stdin):20: MD013 Line length (stdin):1: MD026 Trailing punctuation in header (stdin):6: MD034 Bare URL used (stdin):16: MD034 Bare URL used (stdin):19: MD034 Bare URL used [1] https://github.com/markdownlint/markdownlint (From OE-Core rev: 5339f5988afce79e9ff56788f715671579fd7cd1) Signed-off-by: Igor Opaniuk <igor.opaniuk@foundries.io> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* README.qemu.md: fix markdown style issuesIgor Opaniuk2025-02-051-4/+4
| | | | | | | | | | | | | Fix markdown style issues using markdownlint tool [1]: $ cat README.qemu.md | mdl (stdin):8: MD006 Consider starting bulleted lists at the beginning of the line [1] https://github.com/markdownlint/markdownlint (From OE-Core rev: cf5f8f9ae809f3cc6a0d53bdfb28e6d913f2fecc) Signed-off-by: Igor Opaniuk <igor.opaniuk@foundries.io> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* MAINTAINERS.md: fix markdown style issuesIgor Opaniuk2025-02-051-2/+0
| | | | | | | | | | | | | Fix markdown style issues using markdownlint tool [1]: $ cat MAINTAINERS.md | mdl (stdin):71: MD012 Multiple consecutive blank lines (stdin):72: MD012 Multiple consecutive blank lines [1] https://github.com/markdownlint/markdownlint (From OE-Core rev: 7338fb12cfa0491b451f74fd640919501a71ed4e) Signed-off-by: Igor Opaniuk <igor.opaniuk@foundries.io> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* README.OE-Core.md: fix markdown style issuesIgor Opaniuk2025-02-051-9/+8
| | | | | | | | | | | | | | | | | | | Fix markdown style issues using markdownlint tool [1]: $ cat README.OE-Core.md | mdl (stdin):15: MD012 Multiple consecutive blank lines (stdin):9: MD034 Bare URL used (stdin):13: MD034 Bare URL used (stdin):19: MD034 Bare URL used (stdin):25: MD046 Code block style (stdin):29: MD046 Code block style (stdin):33: MD046 Code block style [1] https://github.com/markdownlint/markdownlint (From OE-Core rev: 64281b59e8bbae75a1706052ff6fba191d86d0d7) Signed-off-by: Igor Opaniuk <igor.opaniuk@foundries.io> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* selftest/reproducible: Add a method to test a single recipeYoann Congal2025-02-051-2/+8
| | | | | | | | | | | | | | | Introduce a new variable "OEQA_REPRODUCIBLE_TEST_LEAF_TARGETS". It can be used like OEQA_REPRODUCIBLE_TEST_TARGET but will try to use sstate for the dependencies. This can be used to "quickly" test the reproducibility of a single recipe. [YOCTO #15701] (From OE-Core rev: e2440618bd12d7288a7f3f7cfb92d377ae61a3b4) Signed-off-by: Yoann Congal <yoann.congal@smile.fr> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* selftest/reproducible: Move a comment to follow the line it concernsYoann Congal2025-02-051-1/+1
| | | | | | | | | | The code line was moved in commit 5a9a5ad6a7be ("reproducibility: continue testing in case of build failure") (From OE-Core rev: b4b60941153ebeb5019b26eeed593d0a1cdb4012) Signed-off-by: Yoann Congal <yoann.congal@smile.fr> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* glibc: Upgrade to 2.41 releaseKhem Raj2025-02-0534-152/+83
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | License-Update: Added license for e_gammaf_r.c [1] added url of CORE-MATH project [2] * Testing support with different compilers (series) * Remove XXX math functions from installed math.h (patch) * Remove "%n" from assert (commit) * Improve executable stack handling * Compile glibc tests with Clang (series 1, series 2) * asprintf should write NULL on failure * Revert TCB layout changes * Fix ld.so crashes with golang test suite * Fixes after GET_ADDR_ARGS removal * Extend Rseq Support, plus x32 fixup * sh4: ensure FPSCR.PR==0 when executing FRCHG [BZ #27543] * affinity-inheritance test: overallocate CPU sets * rseq-related aarch64 test failures * arc4random test failure under load * benchtests: Add dummy in put files cospi, cospif, sinpi, sinpif, tanpi, tanpif * pthread condvar missing signal, bug 25847 * aarch64: Add support for Guarded Control Stack extension * testsuite: Make stdio-common/tst-printf-format-*-mem UNSUPPORTED if the mtrace output does not exist Further Release Notes [3] [4] [1] https://sourceware.org/git/?p=glibc.git;a=commit;h=2843e78b30da0aa743fdfb0ac61435c925182c04 [2] https://sourceware.org/git/?p=glibc.git;a=commit;h=d421d36582281a62e05f96a1bfb085db9d85f40b [3] https://sourceware.org/glibc/wiki/Release/2.41 [4] https://sourceware.org/pipermail/libc-announce/2025/000045.html (From OE-Core rev: 73b34ff50c8e5b05eca8f9a236bd1b155bd14324) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ptest-packagelists: remove valgrindRandy MacLeod2025-02-051-7/+4
| | | | | | | | | | The valgrind-3.24 and glibc-2.41 update result in lots of valgrind ptests failing. Remove all valgrind ptests until that can be fixed. (From OE-Core rev: 98d5a6a68e9e7df671e40480faed48ab2114dd7f) Signed-off-by: Randy MacLeod <Randy.MacLeod@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* valgrind: disable ptestsRandy MacLeod2025-02-053-227/+1
| | | | | | | | | | | | | | | | | The valgrind test runner, vg_regtest, changed in the 3.24 update and there are some additional valgrind ptest regressions happening with glibc-2.41. Disable the ptests for now. Some of the remaining patches can likely be dropped but I'd rather carry them so that re-enabling the ptests is simpler. Also the patch series have some dependencies and unwinding that would block the glibc-2.41 unnecessarily. This builds for glibc, musl for qemux86-64, runs: -> valgrind [--leak-check=full] /bin/ls /tmp (From OE-Core rev: 8fc31fb235af12530475ec5055f6c00ccfafadfa) Signed-off-by: Randy MacLeod <Randy.MacLeod@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* valgrind: update 3.23.0 -> 3.24.0 (ptest fails, vg_regtest needs rebase)Alexander Kanavin2025-02-0519-360/+81
| | | | | | | (From OE-Core rev: 6bf1cd3353c36e12000159e67f3d9212b0cbaf1f) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qemuriscv: Enable Sv39 memory address scheme by defaultYash Shinde2025-02-051-0/+1
| | | | | | | | | | | | | | | | | | | | Currently, GCC Asan supports only Sv39 on RISC-V 64 due to custom allocator configurations optimized for large allocations. These configurations are incompatible with larger address spaces like Sv48/Sv57. This fix enables RISC-V 64 configuration for RVA22S64 profile(which has sv39 mode and other extensions) by default when running `runqemu nographic`, eliminating the need for manual configuration via command line flags (`qemuparams="-cpu rv64, sv39=true"`). Fixes [YOCTO #15691] https://bugzilla.yoctoproject.org/show_bug.cgi?id=15691 Reference: https://github.com/qemu/qemu/commit/af651969eb23ecf018bcaa8e0761b58425de550c https://git.openembedded.org/openembedded-core/commit/?id=4b4450ff695ef73bf7a2437e142d2e0730d6a547 (From OE-Core rev: 5e749a2576698e390392b5d522a2dc5fdc9556cd) Signed-off-by: Yash Shinde <Yash.Shinde@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gdb: Upgrade to 16.2 releseKhem Raj2025-02-054-1/+1
| | | | | | | | | | | | | | | | | | | GDB 16.2 brings the following fixes and enhancements over GDB 16.1: * PR build/32578 (cannot build GDB 16.1 out of tree when calling the configure script with a relative path) * PR tui/32592 ([gdb/tui] internal error in tui-winsource.c:340:refresh_window) * PR remote/32593 (Incompatibilities between GDB's and LLDB's 'x' packet implementation) * PR build/32610 (Missing #include file in darwin_nat.c) (From OE-Core rev: 11362b3ae521a0fba85c034de5ba8d4271574be3) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* binutils: Upgrade to 2.44 releaseKhem Raj2025-02-0523-600/+492
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Drop the CVE-2024-53589 patch, its included in 2.44 * Package newly rename gp-* to gprofng-* binaries and remove old gp-* symlinks * Gold linker is now deprecated and will be removed in future release its already deleted in tarball releases * Support for the Nios II target has been removed. * Assembler: - Support for new architecture extensions for AArch64, Risc-V and x86. * Linker: The default maximum page size was changed from 16KiB to 64KiB for LoongArch. This now supports mixed LTO and non-LTO object files in relocatable output. The ELF forms of the linker support a --image-base=<ADDR> option for compatibility with LLD. The --build-id= option now accepts an argument of "xx" which enables the use of the xxhash library. This produces a 128-bit hash and is 2-4x faster than md5 or sha1. The ELF linker option --package-metadata supports percent-encoded and %[string] encoded JSON payloads. * Disassembler: The RISC-V disassembler now supports -M,max option like QEMU to dump instruction without checking architecture support as usual. * GprofNG: Support added for hardware event counters for Neoverse-N1, Ampere-1, and Appliedmicro processors. Detailed release notes [1] [1] https://lists.gnu.org/archive/html/info-gnu/2025-02/msg00001.html (From OE-Core rev: df3c43e69542939a4bec3893f1e927edf2ad7179) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* xorg-minimal-fonts: dont try to install builddirMarkus Volk2025-02-051-1/+3
| | | | | | | | | | | | | | | | | | With current master branch I see an error in do_install: | DEBUG: Executing shell function do_install | install: omitting directory '/home/flk/poky/build/tmp/work/all-poky-linux/xorg-minimal-fonts/1.0/misc/xorg-minimal-fonts-1.0-build' | WARNING: /home/flk/poky/build/tmp/work/all-poky-linux/xorg-minimal-fonts/1.0/temp/run.do_install.112196:151 exit 1 from 'install -m 0644 /home/flk/poky/build/tmp/work/all-poky-linux/xorg-minimal-fonts/1.0/misc/* /home/flk/poky/build/tmp/work/all-poky-linux/xorg-minimal-fonts/1.0/image//usr/share/fonts/X11/misc/' | WARNING: Backtrace (BB generated script): | #1: do_install, /home/flk/poky/build/tmp/work/all-poky-linux/xorg-minimal-fonts/1.0/temp/run.do_install.112196, line 151 | #2: main, /home/flk/poky/build/tmp/work/all-poky-linux/xorg-minimal-fonts/1.0/temp/run.do_install.112196, line 159 ERROR: Task (/home/flk/poky/meta/recipes-graphics/xorg-font/xorg-minimal-fonts.bb:do_install) failed with exit code '1' Fix the problem by specifying more precisely what is to be installed (From OE-Core rev: a8c8731caca14bb7a71e6468877857e0e85f4ce7) Signed-off-by: Markus Volk <f_l_k@t-online.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* testimage.bbclass: fix logDetails() call on error pathMikko Rapeli2025-02-051-2/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This happens when testimage task runs and bitbake is interupted twice with ctrl-c/SIGINT: QMP Available for connection at /home/builder/src/base/repo/meta-arm/build/tmp/.xjik9srq QMP connected to QEMU at 01/31/25 10:36:19 and took 0.55 seconds QMP released QEMU at 01/31/25 10:36:19 and took 0.07 seconds from connect Keyboard Interrupt, closing down... Second Keyboard Interrupt, stopping... WARNING: Exiting due to interrupt. NOTE: Sending SIGTERM to remaining 1 tasks ERROR: core-image-base-1.0-r0 do_testimage: testimage interrupted, shutting down... Output from runqemu: runqemu - INFO - Received signal: 15 runqemu - INFO - Cleaning up runqemu - INFO - Host uptime: 6230788.40 tput: No value for $TERM and no -T specified ERROR: core-image-base-1.0-r0 do_testimage: Error executing a python function in exec_func_python() autogenerated: The stack trace of python calls that resulted in this exception/failure was: File: 'exec_func_python() autogenerated', lineno: 2, function: <module> 0001: *** 0002:do_testimage(d) 0003: File: '/home/builder/src/base/repo/meta-arm/build/../poky/meta/classes-recipe/testimage.bbclass', lineno: 122, function: do_testimage 0118: dump-guest-memory {"paging":false,"protocol":"file:%s.img"} 0119:} 0120: 0121:python do_testimage() { *** 0122: testimage_main(d) 0123:} 0124: 0125:addtask testimage 0126:do_testimage[nostamp] = "1" File: '/home/builder/src/base/repo/meta-arm/build/../poky/meta/classes-recipe/testimage.bbclass', lineno: 389, function: testimage_main 0385: 0386: # Show results (if we have them) 0387: if results: 0388: configuration = get_testimage_configuration(d, 'runtime', machine) *** 0389: results.logDetails(get_json_result_dir(d), 0390: configuration, 0391: get_testimage_result_id(configuration), 0392: dump_streams=d.getVar('TESTREPORT_FULLLOGS')) 0393: results.logSummary(pn) Exception: AttributeError: 'TestResult' object has no attribute 'logDetails' ERROR: Logfile of failure stored in: /home/builder/src/base/repo/meta-arm/build/tmp/work/qemuarm64_secureboot-poky-linux/core-image-base/1.0/temp/log.do_testimage.2771735 Summary: 1 task failed: /home/builder/src/base/repo/meta-arm/build/../poky/meta/recipes-core/images/core-image-base.bb:do_testimage (From OE-Core rev: c0d864a7007adbdf332da62e89c73630b3e01639) Signed-off-by: Mikko Rapeli <mikko.rapeli@linaro.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-rdflib: upgrade 7.1.1 -> 7.1.3Richard Purdie2025-02-051-2/+2
| | | | | | | | License-Update: copyright years updated. (From OE-Core rev: b90837274d236bf6bf7f79cbd63dd251cab7c453) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* lzip: upgrade 1.24.1 -> 1.25Richard Purdie2025-02-051-2/+2
| | | | | | | | License-Update: FSF web address added and postal address removed. (From OE-Core rev: 4270e8a6f07b9323f125da6795073f9b2fb18dd7) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libpng: upgrade 1.6.44 -> 1.6.45Richard Purdie2025-02-051-2/+2
| | | | | | | | License-Update: copyright years updated. (From OE-Core rev: 847b2d90a1be94ee85b5b606139d702dad014317) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ed: upgrade 1.20.2 -> 1.21Richard Purdie2025-02-051-4/+4
| | | | | | | | | License-Update: Copyright years updated, FSF web address added and postal address removed. (From OE-Core rev: 41c4f5563308a7349c5fb4b6a2ee35523c922280) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* llvm: upgrade 19.1.6 -> 19.1.7Richard Purdie2025-02-053-8/+7
| | | | | | (From OE-Core rev: fef54c0109b8abbaaa45c8dc5a022111309f0bd3) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* cmake: upgrade 3.31.4 -> 3.31.5Richard Purdie2025-02-056-4/+4
| | | | | | (From OE-Core rev: d7db46a126bc7c7460c99bae512eb435868e27b7) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* wayland-protocols: upgrade 1.39 -> 1.40Richard Purdie2025-02-051-1/+1
| | | | | | (From OE-Core rev: fa06e4932783bb38c266e9e106c0754862f37654) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sysklogd: upgrade 2.6.2 -> 2.7.0Richard Purdie2025-02-051-1/+1
| | | | | | (From OE-Core rev: 92a4a33ffc254b747f36691b969e97ebd5cd3461) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* stress-ng: upgrade 0.18.08 -> 0.18.09Richard Purdie2025-02-051-1/+1
| | | | | | (From OE-Core rev: 94bdad007121ee9d50cb895012da51ddb6c2e46f) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* repo: upgrade 2.50.1 -> 2.51Richard Purdie2025-02-051-1/+1
| | | | | | (From OE-Core rev: 70fdf1f415e7cfe6e66a9b0d8b6e9bc5f34ca0f4) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-websockets: upgrade 14.1 -> 14.2Richard Purdie2025-02-051-1/+1
| | | | | | (From OE-Core rev: d609b99f71eb8b3dff186f2dc832918a223a5c16) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-trove-classifiers: upgrade 2024.10.21.16 -> 2025.1.15.22Richard Purdie2025-02-051-1/+1
| | | | | | (From OE-Core rev: 6062b9326d3ff4168a0e5c5932c67c0a9f48f1e4) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-setuptools: upgrade 75.6.0 -> 75.8.0Richard Purdie2025-02-053-14/+8
| | | | | | (From OE-Core rev: 2f30a782ae5500d9b7dcc37e2cfc43312a470605) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-ruamel-yaml: upgrade 0.18.9 -> 0.18.10Richard Purdie2025-02-051-1/+1
| | | | | | (From OE-Core rev: 0f46b4fd10e6be1c48738e64c24a977a02768c9b) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-referencing: upgrade 0.35.1 -> 0.36.2Richard Purdie2025-02-051-1/+1
| | | | | | (From OE-Core rev: c996952787b26cd3f508db00e82d0bbefdf2675d) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-pytz: upgrade 2024.2 -> 2025.1Richard Purdie2025-02-051-1/+1
| | | | | | (From OE-Core rev: c8445cf5d8e3a47f7ae38d400c7d4edf7d32d3cc) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-pyopenssl: upgrade 24.3.0 -> 25.0.0Richard Purdie2025-02-051-1/+1
| | | | | | (From OE-Core rev: 98db2721ca2b1edde25cd855f102d1cb7faaa203) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-pygments: upgrade 2.19.0 -> 2.19.1Richard Purdie2025-02-051-1/+1
| | | | | | (From OE-Core rev: 2a5d9af401ff4e8802340eba6382ecd9ce204c7e) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-poetry-core: upgrade 2.0.0 -> 2.0.1Richard Purdie2025-02-051-1/+1
| | | | | | (From OE-Core rev: 911edf7506d6a9eae8ecdbe3ae586b5559f9b6a1) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-pip: upgrade 24.3.1 -> 25.0Richard Purdie2025-02-052-2/+2
| | | | | | (From OE-Core rev: 787b69e38a02c14c8851f110c61366de963bee05) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-more-itertools: upgrade 10.5.0 -> 10.6.0Richard Purdie2025-02-051-1/+1
| | | | | | (From OE-Core rev: 05a7a6dc6c40f5682b4de71f5872e842f4d51441) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-license-expression: upgrade 30.4.0 -> 30.4.1Richard Purdie2025-02-051-1/+1
| | | | | | (From OE-Core rev: 125af6707480408a2e32ba042ed7bfb4de5f6182) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>