summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* expat: upgrade to 2.7.3Ross Burton2025-10-011-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Security fixes: - Fix alignment of internal allocations for some non-amd64 architectures (e.g. sparc32); fixes up on the fix to CVE-2025-59375 from #1034 (of Expat 2.7.2 and related backports) - Fix a class of false positives where input should have been rejected with error XML_ERROR_ASYNC_ENTITY; regression from CVE-2024-8176 fix pull request #973 (of Expat 2.7.0 and related backports). Please check the added unit tests for example documents. Other changes: - Prove and regression-proof absence of integer overflow from function expat_realloc - Remove "harmless" cast that truncated a size_t to unsigned - Autotools: Remove "ln -s" discovery - docs: Be consistent with use of floating point around XML_SetAllocTrackerMaximumAmplification - docs: Make it explicit that XML_GetCurrentColumnNumber starts at 0 - docs: Better integrate the effect of the activation thresholds - docs: Fix an in-comment typo in expat.h - docs: Fix a typo in README.md - docs: Improve change log of release 2.7.2 - xmlwf: Resolve use of functions XML_GetErrorLineNumber and XML_GetErrorColumnNumber - Windows: Normalize .bat files to CRLF line endings - Version info bumped from 12:0:11 (libexpat*.so.1.11.0) to 12:1:11 (libexpat*.so.1.11.1); see https://verbump.de/ for what these numbers do (From OE-Core rev: 6b1833cd2eb78be55ba03da73937358fcf25d9ec) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* classes/cmake: unset LDFLAGS in toolchain-native.bbclassRoss Burton2025-10-011-0/+9
| | | | | | | | | | | | | | | | | | | | | | If a recipe is using toolchain-native.cmake to build native portion in a non-native build, the target LDFLAGS from the environment will leak into the native build. This was noticed as building a SDK with clang means that LDFLAGS contains a --dynamic-loader argument, so native binaries were trying to use the target loader. There are several variables that are set from LDFLAGS[1] so instead of setting them all, we can simply unset the environment variable in the toolchain. [1] https://cmake.org/cmake/help/latest/envvar/LDFLAGS.html (From OE-Core rev: f9fa240a6788188174c8080a78018ed9ce402f54) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqa/bblayers.py: add tests for adding new built-in fragmentsAntonin Godard2025-10-012-0/+31
| | | | | | | | | | | | | | | | | | | | | Add discussed in [1], our best option for customizing built-in fragments is to pass them from a layer configuration. In short, the reason is that our statement must be parsed before the addfragments call is parsed.We also have to use the :append override as using += would override the original definition of OE_FRAGMENTS_BUILTIN (since it uses a ?= assignment). Provide a test case for customizing built-in fragments with meta-selftest. [1]: https://lore.kernel.org/yocto-docs/20250925-fragments-v1-0-c9f747361fb2@bootlin.com/T/#m9f7c9f110c084eba17e0f64d8b2ac7a88af3f38e Cc: Alexander Kanavin <alex.kanavin@gmail.com> (From OE-Core rev: 38cbf4c0ce5173dc3080fa0fbb3ec3e7926c8137) Signed-off-by: Antonin Godard <antonin.godard@bootlin.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* tiff: ignore CVE-2025-8851Peter Marko2025-10-011-0/+1
| | | | | | | | | | | This is fixed in v4.7.0, however cve_check cannot match it as NVD says "Up to (excluding) 2024-08-11". (From OE-Core rev: 66349865ac048ae8e5a81b29c50c68503053f74e) Signed-off-by: Peter Marko <peter.marko@siemens.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* tiff: upgrade 4.7.0 -> 4.7.1Peter Marko2025-10-019-380/+3
| | | | | | | | | | | | | | Removed patches included in this new release License-Update: BSD license added based on [1] [1] https://gitlab.com/libtiff/libtiff/-/commit/a0b623c7809ea2aa4978d5d7b7bd10e519294c78 (From OE-Core rev: 9161c31aa37341f758fd8f3d095177e8b6de1448) Signed-off-by: Peter Marko <peter.marko@siemens.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* patchtest: Use raw strings for regex patternsPaul Barker2025-10-012-12/+12
| | | | | | | | | | | | This fixes several 'SyntaxWarning: invalid escape sequence' messages printed when running patchtest. Cc: Trevor Gamblin <tgamblin@baylibre.com> (From OE-Core rev: c585977a6b55db93b7f432280ae4251aa9bc6b6c) Signed-off-by: Paul Barker <paul@pbarker.dev> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake-layers/create: Improve help message for layerid argumentPaul Barker2025-10-011-1/+1
| | | | | | | | | | | | | | | 'Layer ID' isn't a commonly used term in our help messages or documentation, so clarify that this is the identifier used for the new layer in BBFILE_COLLECTIONS. Also clarify that the default is the basename of the layerdir argument if a layer ID is not separately provided. (From OE-Core rev: bb8bd71b1aba31aeb0c1d2fbcae36da26865dc57) Signed-off-by: Paul Barker <paul@pbarker.dev> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* unzip: remove invalid UPSTREAM_CHECK_REGEXChangqing Li2025-10-011-3/+0
| | | | | | | | | | | After SRC_URI is changed to sourceforge, this UPSTREAM_CHECK_REGEX become invalid, just remove it. (From OE-Core rev: b5aec20d6139fb45501b383cd5cc2ef944cc6dd4) Signed-off-by: Changqing Li <changqing.li@windriver.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* vim: upgrade 9.1.1652 -> 9.1.1683Divya Chellam2025-10-011-2/+2
| | | | | | | | | | | | | | Handles CVE-2025-9389 Changes between 9.1.1652 -> 9.1.1683 ==================================== https://github.com/vim/vim/compare/v9.1.1652...v9.1.1683 (From OE-Core rev: ad24eedbbef303e67acb1241ed54c253ec5ab50c) Signed-off-by: Divya Chellam <divya.chellam@windriver.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* baremetal-helloworld: set UPSTREAM_CHECK_COMMITSChangqing Li2025-10-011-1/+1
| | | | | | | | | | | | | | set UPSTREAM_CHECK_COMMITS to make new commit is reported Test result(change SRCREV to an old one): $devtool check-upgrade-status baremetal-helloworld baremetal-helloworld 0.1 new commits Alejandro Hernandez <alejandro@enedino.org> db2bf750eaef7fc0832e13ada8291343bbcc3afe (From OE-Core rev: 3d7d324ca0ea242f1455332a20ac7b0f3cdcd761) Signed-off-by: Changqing Li <changqing.li@windriver.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* cwautomacros: delete the recipeAlexander Kanavin2025-10-012-26/+0
| | | | | | | | | | | This is a long-obsolete set of custom autotools macros; 'which' was the last consumer in core or meta-oe. (From OE-Core rev: 6d1470f6d244c08e3473073d0c2d57a97d2eeb17) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* which: update 2.21 -> 2.23, build with mesonAlexander Kanavin2025-10-014-38/+113
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This (and 2.22) is a first release in many years. Rather than try to use upstream's absurdly overblown, incompatible build system (see below), I added a small-ish meson file. This means: - drop tweaks and dependency on cwautomacros as that is no longer used - drop patch as configure.ac has been rewritten, and the recipe is using meson anyway - drop --disable-iberty for the same reason In this realease, cwautomacros has been replaced by an equally custom, weird set of macros, written by 'which' maintainer: https://github.com/CarloWood/cwm4 - one effect of that is that autoreconf isn't happy with which's configure.ac and won't run; one is supposed to use a custom script instead: https://github.com/CarloWood/cwm4/blob/master/scripts/bootstrap.sh - alas, that script is not shipped in tarballs; the maintainer wants everyone to trust their 200k configure script (hello xz backdoor) - building from git (where the script exists) is not impossible, but that has no version tags All this 'special handling' for what, exactly? Five .c files to produce one single-function executable, and one manpage. Wich should all be in coreutils to begin with. GNU's attachment to autotools defies reason. (From OE-Core rev: 600545a0ef313e7df5a0f25eba17b73b0f410489) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* test-manual/yocto-project-compatible.rst: fix a typoAntonin Godard2025-09-261-1/+1
| | | | | | | | | | Fix a typo in yocto-project-compatible.rst. Reviewed-by: Quentin Schulz <quentin.schulz@cherry.de> (From yocto-docs rev: a84c234acfedfa714419006c743405e2f9acaedc) Signed-off-by: Antonin Godard <antonin.godard@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* migration-guides/release-notes-5.3: using runqemu with compressed imagesYoann Congal2025-09-261-0/+7
| | | | | | | | | | | | | | | In OE-core commits: * b5f8c3e029 (selftest: runqemu: add tests for booting zst compressed image, 2025-07-31) * e069fe2480 (runqemu: Add support for running compressed .zst rootfs images, 2025-07-31) runqemu gained the ability to run compressed image (+associated test). Add this information to the release-notes for 5.3. (From yocto-docs rev: f268c1b649227d533d02e1a6df797b784fcf80de) Signed-off-by: Yoann Congal <yoann.congal@smile.fr> Signed-off-by: Antonin Godard <antonin.godard@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* contributor-guide: submit-changes: make "Crediting contributors" part of ↵Quentin Schulz2025-09-261-25/+29
| | | | | | | | | | | | | | | | | | | | | "Commit your changes" There's no need to differentiate crediting contributors from committing your changes, so let's simply make it the last step of "Commit your changes" section. This simply indents the text so it's now part of "Commit your changes" list instead of the main list in the "Implement and commit changes" section. Because of this reorganisation, the instruction to use "git commit --amend" to add the contributors is moved to a note, and the first few sentences are reworded to better match the wording of other items in the "Commit your changes" list of instructions. (From yocto-docs rev: eff4d14e28d323ebfdaeb0c5c805b5f1e2ad153d) Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de> Signed-off-by: Antonin Godard <antonin.godard@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* contributor-guide: submit-changes: number instruction list in commit your ↵Quentin Schulz2025-09-261-76/+76
| | | | | | | | | | | | | changes ... so that it's clear that you need to read and follow each and every instruction in this list. (From yocto-docs rev: c628a489f081925fabaabb5acac6752251150269) Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de> Signed-off-by: Antonin Godard <antonin.godard@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* contributor-guide: submit-changes: reword commit message instructionsQuentin Schulz2025-09-261-9/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | This should hopefully make it clearer what is expected from the contributor. This follows my understanding of git-commit(1)[1] where the following is a git commit message: """ git commit title git commit description """ I'm putting the "Fixes [YOCTO" line in "body of the commit message" so it's understood as being different from the git commit description so that the note admonition allowing us to have an empty commit description doesn't apply to the "Fixes [YOCTO" line. [1] https://www.man7.org/linux/man-pages/man1/git-commit.1.html#DISCUSSION (From yocto-docs rev: b84903a760350bd118c56ea9ce4e98039edf6e55) Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de> Signed-off-by: Antonin Godard <antonin.godard@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* contributor-guide: submit-changes: make the Cc tag follow kernel guidelinesQuentin Schulz2025-09-261-1/+1
| | | | | | | | | | | | | The kernel docs specifies[1] a Cc: tag and not CC: tag, so let's align with that. [1] https://www.kernel.org/doc/html/latest/process/submitting-patches.html#when-to-use-acked-by-cc-and-co-developed-by (From yocto-docs rev: f800fef4e9e2c1d3584ac49be8324638d2923b17) Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de> Signed-off-by: Antonin Godard <antonin.godard@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* contributor-guide: submit-changes: align CC tag descriptionQuentin Schulz2025-09-261-1/+1
| | | | | | | | | | | | The other tag descriptions have the double colon outside of the highlight, and start the sentence with a lowercase word, so let's align the CC tag with those. (From yocto-docs rev: f116e93fb335e9d0f85891c4cb501bcf55b18ccf) Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de> Signed-off-by: Antonin Godard <antonin.godard@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* contributor-guide: submit-changes: clarify example with Yocto bug IDQuentin Schulz2025-09-261-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | The example could be understood as the content of the commit message once the editor (git config core.editor) opens, where the first line is the actual commit title and not the commit description. This example would make the Fixes line the commit title, which is not what we want. In short, according to my understanding of git-commit(1): The following is a git commit message: """ git commit title git commit description """ Reported-by: Barne Carstensen <barne.carstensen@danfoss.com> (From yocto-docs rev: a5862406bf3230befe9db9f2539bbbc86c02015d) Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de> Signed-off-by: Antonin Godard <antonin.godard@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* contributor-guide: submit-changes: fix improper bold stringQuentin Schulz2025-09-261-1/+1
| | | | | | | | | | | | | I don't know what was the initial intent but this doesn't seem right, so let's remove the bold formatting. Fixes: 4abe87cb20d3 ("contributor-guide: submit-changes: detail commit and patch creation") Cc: Michael Opdenacker <michael.opdenacker@rootcommit.com> (From yocto-docs rev: 6c499b3796a578a0fe4c319c9547b4321b0d41df) Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de> Signed-off-by: Antonin Godard <antonin.godard@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual/structure.rst: extend PERSISTENT_DIR descriptionAntonin Godard2025-09-261-0/+11
| | | | | | | | | | | | | | Extend the description of PERSISTENT_DIR to mention that it should not be shared between builds. Add a note on sharing the hash equivalence database by setting up a server and not sharing the file in this directory. [YOCTO #15727] (From yocto-docs rev: 0ff0233770b77f9e74f4241dfb555dac2741d8b9) Signed-off-by: Antonin Godard <antonin.godard@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* migration-5.3.rst: Correct info about the removed libsoup-2.4 recipePeter Kjellerstedt2025-09-261-3/+3
| | | | | | | | | | | | It is the libsoup-2.4 recipe that has been removed, not libsoup. Also add that it has been moved to meta-oe. (From yocto-docs rev: ac2896c89df7e5dfa91b18a5e1681019f17182d3) Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com> Signed-off-by: Antonin Godard <antonin.godard@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* migration-5.3.rst: Correct a typoPeter Kjellerstedt2025-09-261-1/+1
| | | | | | | | (From yocto-docs rev: a87be4bc3c518fe92c5fc849975fcd233fdc51db) Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com> Signed-off-by: Antonin Godard <antonin.godard@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* test-manual: update runtime-testing Exporting Tests sectionBarne Carstensen2025-09-261-7/+12
| | | | | | | | | | | | | This has changed since commit ed4238487c81 ("testexport: Fix to work as an image class") in OE-Core. [Antonin Godard: mention oecore commit in commit body] (From yocto-docs rev: 2caa8e581feaf3640bea68108f9a02583b17b21b) Signed-off-by: Barne Carstensen <barne.carstensen@danfoss.com> Signed-off-by: Antonin Godard <antonin.godard@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* piglit: rename virtual/opencl-icd to virtual/libopencl1Ryan Eatmon2025-09-251-1/+1
| | | | | | | | | | | | A change in meta-openembedded that provided virtual/opencl-icd [1] changed the name to virtual/libopencl1. [1] https://git.openembedded.org/meta-openembedded/commit/?id=87b44d29b6942427bfb1fab02a4564e41dcc01a0 (From OE-Core rev: 07747aa7390e98bf2853154e5fd473e4984a1d3d) Signed-off-by: Ryan Eatmon <reatmon@ti.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meta/lib/oe/recipeutils.py: Handle multi-repo recipes for upgrade checkUwe Kleine-König2025-09-251-1/+1
| | | | | | | | | | | | | | | For a recipe that uses more than one git repo there isn't a single SRCREV variable. For example for linux-yocto there is SRCREV_machine and SRCREV_meta and rd.getVar("SRCREV") yields "INVALID". Luckily bb.fetch2 already handles all the details and exposes the currently used revision in ud. So just use that. (From OE-Core rev: ddf00d6aee955878c070327ee8d751fdb6099444) Signed-off-by: Uwe Kleine-König <u.kleine-koenig@baylibre.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* rust: Upgrade 1.89.0 -> 1.90.0Yash Shinde2025-09-2516-152/+193
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | https://blog.rust-lang.org/2025/09/18/Rust-1.90.0/ * Recent changes in rustc require 'target-c-int-width' to be an integer, not a string. This fixes type consistency when generating target specs. https://github.com/rust-lang/rust/pull/142352. * Rebase existing patches with v1.90.0. * Drop merged patches with rust v1.90.0. - backport-fix-test-string-merging.patch https://github.com/rust-lang/rust/commit/2d51acd2fbcbadb6f30709c5dd305494d413d388 * The "remote-test-server" bin is now generated in stage1-tools-bin dir rather than stage2. Update the test suite accordingly. The tests/{assembly/codegen} dirs are renamed to tests/{assembly,codegen}-llvm. Update the test suite and patches accordingly. https://github.com/rust-lang/rust/pull/144249/commits * Use "//@ ignore-riscv64" tag for tests failing on riscv-64 instead of previous "only-<target_arch>" tags. Test results summary: rust v1.90.0 +-----------+--------+---------+ | Machine | Passed | Ignored | +-----------+--------+---------+ | arm-32 | 29,517 | 1,529 | | arm-64 | 29,608 | 1,471 | | x86-32 | 29,508 | 1,507 | | x86-64 | 29,903 | 1,275 | | riscv-64 | 29,584 | 1,494 | +-----------+--------+---------+ Test results difference (1.90 - 1.89): +-----------+--------+---------+ | Machine | Passed | Ignored | +-----------+--------+---------+ | arm-32 | +278 | +61 | | arm-64 | +279 | +59 | | x86-32 | +277 | +58 | | x86-64 | +419 | +50 | | riscv-64 | +280 | +58 | +-----------+--------+---------+ (From OE-Core rev: 86d09ec9cdbcea6e076ebac6e1243f9e20fb4378) Signed-off-by: Yash Shinde <Yash.Shinde@windriver.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* apt: fix reproducibility issueHongxu Jia2025-09-251-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In oe-selftest of reproducibility, recipe apt has reproducibility issue: ... 2025-09-20 17:09:18,986 - oe-selftest - INFO - ====================================================================== 2025-09-20 17:09:18,986 - oe-selftest - INFO - FAIL: test_reproducible_builds (reproducible.ReproducibleTests) 2025-09-20 17:09:18,986 - oe-selftest - INFO - ---------------------------------------------------------------------- 2025-09-20 17:09:18,986 - oe-selftest - INFO - Traceback (most recent call last): File "/buildarea5/hjia/contrib/openembedded-core-contrib/meta/lib/oeqa/selftest/cases/reproducible.py", line 406, in test_reproducible_builds self.fail('\n'.join(fails)) AssertionError: The following deb packages are different and not in exclusion list: build-st/reproducibleB-extended/tmp/deploy/deb/./x86-64-v3/apt-dbg_3.0.3-r0_amd64.deb build-st/reproducibleB-extended/tmp/deploy/deb/./x86-64-v3/apt_3.0.3-r0_amd64.deb The following ipk packages are different and not in exclusion list: build-st/reproducibleB-extended/tmp/deploy/ipk/./x86-64-v3/apt-dbg_3.0.3-r0_x86-64-v3.ipk build-st/reproducibleB-extended/tmp/deploy/ipk/./x86-64-v3/apt_3.0.3-r0_x86-64-v3.ipk The following rpm packages are different and not in exclusion list: build-st/reproducibleB-extended/tmp/deploy/rpm/./x86_64_v3/apt-3.0.3-r0.x86_64_v3.rpm build-st/reproducibleB-extended/tmp/deploy/rpm/./x86_64_v3/apt-dbg-3.0.3-r0.x86_64_v3.rpm ... Due to upstream apt commit [1], it calls `id -gn root' in cmake to set ROOT_GROUP if not define. The output of `id -gn root' may differ in the compared builds which caused reproducibility issue ... |build-st/reproducibleB-extended/tmp/work/x86-64-v3-oe-linux/apt/ 3.0.3/temp/log.do_configure:124:-- Found root group: wheel ... |build-st/reproducibleA/tmp/work/x86-64-v3-oe-linux/apt/3.0.3/ temp/log.do_configure:124:-- Found root group: root ... Explicitly set ROOT_GROUP = "root" for cmake other than call `id -gn root' to support reproducibility [1] https://salsa.debian.org/apt-team/apt/-/commit/6f1f3c9afdb6ade6a7be110b90c8fc9e603254cf (From OE-Core rev: 5b3d5ae626b0d28535973be2a8a1cf48d314ba12) Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qemuriscv: Use RVA23S64 profile for cpuKhem Raj2025-09-251-1/+1
| | | | | | | | | | | | | Enables RVV extensions uniformly across gcc and clang as it is mandatory in RVA23 spec. https://github.com/riscv/riscv-profiles/blob/main/src/rva23-profile.adoc (From OE-Core rev: 119d63b2e277ca98af593a3fd8add31ca34361af) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libwpe: upgrade 1.16.2 -> 1.16.3Moritz Haase2025-09-252-40/+1
| | | | | | | | | | | | | Release notes are available at [0]. The new release contains a CMake-related patch that we can now drop. [0]: https://github.com/WebPlatformForEmbedded/libwpe/releases/tag/1.16.3 (From OE-Core rev: 40bc1667e4137da70453af3def94ec02d0e6c37d) 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>
* systemd: use if..then in prerm scriptletDaniel McGregor2025-09-251-1/+2
| | | | | | | | | | | | | Using the [ test ] && foo construct in the prerm scriptlet causes the prerm scriptlet to fail if the final test condition fails, which with rpm prevents the removal of the package. Switch to using if;then;fi instead, since it doesn't cause the scriptlet to fail. (From OE-Core rev: a5327fc16b76db28dd1da37463a046e69713dbac) Signed-off-by: Daniel McGregor <daniel.mcgregor@vecima.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-dbusmock: upgrade 0.33.0 -> 0.37.0Trevor Gamblin2025-09-251-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Upstream notably removed the setup.cfg/setup.py files in this period and updated pyproject.toml. It still uses setuptools as the build backend, and should be compatible with recent versions. Changelog (https://github.com/martinpitt/python-dbusmock/releases): 0.37.0: - templates: Drop iio-sensors-proxy (See #241) - DBusTestCase: Drop obsolete {start,stop}_dbus() methods - Fix dbus-daemon startup race condition (Debian#1109272) 0.36.0: - mockobject: Fix _wrap_in_dbus_variant for Struct and Dict types (thanks Sebastian Wick) - Drop setup.{cfg,py} and RHEL 9 support, move to pybuild (rhbz#2377609) - Drop iio-sensor-proxy tests, the template is broken (see #241) 0.35.0: - modemmanager: Add operator code (thanks Guido Günther) - modemmanager: Allow to set CellBroadcast channel list (thanks Guido Günther) 0.34.3: - tests: Relax libnotify expected format for libnotify 0.8.4 0.34.2: - spec: Adjust %autosetup to PEP-625 tarball top-level directory 0.34.1: - spec: Adjust Source URL to PEP-625 tarball name 0.34.0: - modemmanager: Add cell broadcast messages (thanks Guido Günther) - Move release builds to pybuild for PEP-625 compatibility (From OE-Core rev: 523001d3131eb5839162d44d296b65cbf0f6fd56) Signed-off-by: Trevor Gamblin <tgamblin@baylibre.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-pyparsing: upgrade 3.2.3 -> 3.2.4Trevor Gamblin2025-09-251-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Release notes (https://github.com/pyparsing/pyparsing/releases): - Barring any catastrophic bugs in this release, this will be the last release in the 3.2.x line. The next release, 3.3.0, will begin emitting DeprecationWarnings when the pre-PEP8 methods are used (see header notes above for more information, including available automation for converting any existing code using pyparsing with the old names). - Fixed bug when using a copy of a Word expression (either by using the explicit copy() method, or attaching a results name), and setting a new expression name, a raised ParseException still used the original expression name. Also affected Regex expressions with as_match or as_group_list = True. Reported by Waqas Ilyas, in Issue #612 - good catch! - Fixed type annotation for replace_with, to accept Any type. Fixes Issue #602, reported by esquonk. - Added locking around potential race condition in ParserElement.reset_cache, as well as other cache-related methods. Fixes Issue #604, reported by CarlosDescalziIM. - Substantial update to docstrings and doc generation in preparation for 3.3.0, great effort by FeRD, thanks! - Notable addition by FeRD to convert docstring examples to work with doctest! This was long overdue, thanks so much! (From OE-Core rev: f8e8ddcddf108f66203af28d5db08171b60499d3) Signed-off-by: Trevor Gamblin <tgamblin@baylibre.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-hypothesis: upgrade 6.138.15 -> 6.139.2Trevor Gamblin2025-09-251-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Changelog: (https://hypothesis.readthedocs.io/en/latest/changelog.html#changelog): 6.139.2: - Internal refactoring for new lint rules. 6.139.1: - Fixed another typo in error message around function-scoped fixtures. 6.139.0: - Add get_current_profile_name(), which returns the name of the current settings profile. 6.138.17: - Fixed typo in error message around function-scoped fixtures. 6.138.16: - Improved error message for DeadlineExceeded. Reproducibility OK. ptests look OK: |============================================================================ |Testsuite summary |# TOTAL: 5 |# PASS: 5 |# SKIP: 0 |# XFAIL: 0 |# FAIL: 0 |# XPASS: 0 |# ERROR: 0 |DURATION: 1 |END: /usr/lib/python3-hypothesis/ptest |2025-09-19T15:53 |STOP: ptest-runner |TOTAL: 1 FAIL: 0 (From OE-Core rev: 4f7daa9268353ee7f00d5d3e90996f069ea798c4) Signed-off-by: Trevor Gamblin <tgamblin@baylibre.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-trove-classifiers: upgrade 2025.9.8.13 -> 2025.9.11.17Trevor Gamblin2025-09-251-1/+1
| | | | | | | | | | | | | | | | | | | | | | Release notes (https://github.com/pypa/trove-classifiers/releases): 2025.9.11.17: - Add support for Odoo 19.0 in classifiers (#225) 2025.9.9.12: - Add classifier: Framework InvenTree (#223) * Add classifier: Framework InvenTree * fix style issue (From OE-Core rev: 6db42ac0427548e1a5ed5a47a4d1931bb36cce2f) Signed-off-by: Trevor Gamblin <tgamblin@baylibre.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-numpy: upgrade 2.3.2 -> 2.3.3Trevor Gamblin2025-09-251-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Release notes (https://github.com/numpy/numpy/releases/tag/v2.3.3): The NumPy 2.3.3 release is a patch release split between a number of maintenance updates and bug fixes. This release supports Python versions 3.11-3.14. Note that the 3.14.0 final is currently expected in Oct, 2025. This release is based on 3.14.0rc2. Reproducibility seems OK. ptests look OK: |============================================================================ |Testsuite summary |# TOTAL: 48954 |# PASS: 46490 |# SKIP: 2426 |# XFAIL: 33 |# FAIL: 0 |# XPASS: 5 |# ERROR: 0 |DURATION: 169 |END: /usr/lib/python3-numpy/ptest |2025-09-19T15:20 |STOP: ptest-runner |TOTAL: 1 FAIL: 0 (From OE-Core rev: d92db41f718a79ffd3ed173a46c5567fa002e7a7) Signed-off-by: Trevor Gamblin <tgamblin@baylibre.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* maintainers.inc: add self for python recipesTrevor Gamblin2025-09-251-6/+6
| | | | | | | | | | | Add myself as maintainer for some newly-unassigned Python recipes. That'll allow them to be picked up on my upgrade checker. (From OE-Core rev: ae51541d86230414cbbb080d73fb611f7793c4cc) Signed-off-by: Trevor Gamblin <tgamblin@baylibre.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* cmake: upgrade 4.1.0 -> 4.1.1Moritz Haase2025-09-253-1/+1
| | | | | | | | | | | | Release notes are available at [0]. [0]: https://cmake.org/cmake/help/v4.1/release/4.1.html#id1 (From OE-Core rev: 86c0044eb72605e68cc6288f82d615305e94641e) 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>
* libdnf: remove obsolete path patchRoss Burton2025-09-252-37/+0
| | | | | | | | | | | | | | We needed to remove the build path from the source tree because it was embedded into libdnf/dnf-repo.cpp. However, this was replaced with an environment variable in 0.67.0 onwards[1]. [1] libdnf 04d7fba0 ("Use environment variable in unittest instead of ugly hack in libdnf") (From OE-Core rev: 948e92562e3a565f97c5eed2992c1d7ecfcc6305) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libdnf: remove non-functional gtk-doc supportRoss Burton2025-09-252-33/+6
| | | | | | | | | | | | | | | | | The gtk-doc integration doesn't actually work, as it isn't built by default and the targets need to be triggered manually. As clearly nobody was using it, and upstream appears to prefer doxygen for API documentation, remove the gtk-doc support. This also means adding gettext to the dependencies, as this was being pulled in via gtk-doc before but is actually needed for the translations. (From OE-Core rev: cd8987a4d044955950dc000a5757175982dcd2f3) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libdnf: remove obsolete gobject-introspection supportRoss Burton2025-09-251-5/+1
| | | | | | | | | | | | | | The intention to remove G-I support was stated in [1] and the last few pieces removed in [2], which were part of 0.15.0. [1] libdnf a4abd42a ("Move libcheck dependency to tests/") [2] libdnf e2f2862b ("[swdb]: C++ implementation with SWIG bindings.") (From OE-Core rev: 6f37e3293c27d06b7aab845370dd3ea63c564fe9) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libdnf: don't depend on libcheckRoss Burton2025-09-252-2/+54
| | | | | | | | | | | Apply a patch to make libcheck optional, so we don't need to depend on it as we don't install the tests. (From OE-Core rev: 31b95e3c242654f8a7949e8d06df20101668b5a7) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* clang: no need to install tblgen binaries in nativesdk-clangRoss Burton2025-09-251-4/+2
| | | | | | | | | | | These are only needed if cross-compiling clang, and if someone is cross-compiling clang in a SDK they should build their own binaries as these ones might not match the version of clang they're building. (From OE-Core rev: c79837a11ccf0f3e5a8ccab4ffb379cdefe482e8) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* clang: tell cross-builds of clang how to build nativelyRoss Burton2025-09-251-6/+3
| | | | | | | | | | | | | | | | | | | If we pass CROSS_TOOLCHAIN_FLAGS_NATIVE to all the builds, instead of just nativesdk, then clang can correctly build its own native tools as needed. This means we can stop manually installing clang-tidy-confusable-chars-gen as clang-tidy will build it. We (currently) still build the tblgen binaries once as they're used in several recipes so there's likely value in building those once. Also consolidate the LLVM_TABLEGEN variables as they're not specific to a particular class. (From OE-Core rev: 36b42975b975b4a5e3904e555e5ee00aba9c2f2b) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* clang: improve tablegen installationRoss Burton2025-09-253-5/+33
| | | | | | | | | | | | | | Backport a patch from upstream to install lldb-tblgen, and change the llvm-tblgen-native recipe to use `cmake --install` instead of copying the binaries. This ensures that CMake does any post-install steps that are needed, and we don't install binaries that have eg RPATHs pointing at the build tree. (From OE-Core rev: 93051e8730263cfc23e1230015a4789dac4914de) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* clang: remove obsolete install stepsRoss Burton2025-09-251-6/+0
| | | | | | | | | | | | | clang-pseudo and clang-rename have both been removed from upstream, so don't try to install them anymore: llvm 40c45b6b4318 ("Remove clang-rename (#108988)") llvm ed8f78827895 ("Remove clang-pseudo (#109154)") (From OE-Core rev: ac2a625c9a28a692b87a073aca95197e9d08842b) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* clang: add option for llvm-exegesisRoss Burton2025-09-251-0/+1
| | | | | | | | | | | | | | | | Quoting from the README: llvm-exegesis is a benchmarking tool that accepts or generates snippets and can measure characteristics of those snippets by executing it while keeping track of performance counters. Potentially useful but not essential. This reduces the size of llvm-bin by ~30MB and llvm-dbg by ~1100MB. (From OE-Core rev: ed688027468237f4dd258089d4c3ee5f8a9159bb) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* clang: disable all test targetsRoss Burton2025-09-251-0/+1
| | | | | | | | | | | We don't install the tests, or run them in the build tree, so tell cmake not to generate the targets at all. This removes internal dependencies which means we can turn off more components that we don't want. (From OE-Core rev: ba358a03c97cb904248b743c483a7b3f4b9159a9) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* clang: improve opt-viewer PACKAGECONFIGRoss Burton2025-09-253-72/+1
| | | | | | | | | | Instead of patching the python module detection, we can use the hidden option LLVM_TOOL_OPT_VIEWER_BUILD. (From OE-Core rev: ddbbd49c15bad1b2a550188581ffebd752b9b20e) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2026-07-24 20:08:34 +0000