summaryrefslogtreecommitdiffstats
path: root/meta
Commit message (Collapse)AuthorAgeFilesLines
...
* pinentry: drop -unknown suffix from version numberYi Zhao2025-07-031-0/+2
| | | | | | | | | | | | | | | | | | Include drop-unknown-suffix.inc to remove unknown suffix in runtime version. Befor the fix: $ pinentry --version pinentry-curses (pinentry) 1.3.1-unknown After the fix: $ pinentry --version pinentry-curses (pinentry) 1.3.1 (From OE-Core rev: 752b55a9eb631eb48e3dd87062ee0728e67d41a6) Signed-off-by: Yi Zhao <yi.zhao@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libgpg-error:: drop -unknown suffix from version numberYi Zhao2025-07-031-0/+2
| | | | | | | | | | | | | | | | | | Include drop-unknown-suffix.inc to remove unknown suffix in runtime version. Befor the fix: $ gpg-error --version gpg-error (libgpg-error) 1.55-unknown After the fix: $ gpg-error --version gpg-error (libgpg-error) 1.55 (From OE-Core rev: 8477ce3bbd1abf6d7c88ea33696503b5454e5d93) Signed-off-by: Yi Zhao <yi.zhao@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gnupg: drop -unknown suffix from version numberYi Zhao2025-07-033-32/+31
| | | | | | | | | | | | | | | | | | | | | | | | | | | For gnupg and related packages, if autogen.sh is run outside of a git repo, the find-version function always assumes that the package is a beta version and adds the suffix '-unknown' to the version number. Add drop-unknow-suffix.inc file that can be included by gnupg and other recipes. This file is used to modify autogen.sh: 1. Replace beta=yes with beta=no. 2. Replace tmp="-unknown" with tmp="" Also remove 0004-autogen.sh-fix-find-version-for-beta-checking.patch as it is no longer needed. Befor the fix: $ gpg --version gpg (GnuPG) 2.5.5-unknown After the fix: $ gpg --version gpg (GnuPG) 2.5.5 (From OE-Core rev: f6efe56a8c73ae9f58cb70f1469c617ff0647b49) Signed-off-by: Yi Zhao <yi.zhao@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* psmisc: fix runtime version when using git shallow tarballYi Zhao2025-07-031-1/+1
| | | | | | | | | | | | | | | | | | Add tag to SRC_URI to fix runtime version when using git shallow tarball. Before the fix: root@intel-x86-64:~# pslog -V pslog (PSmisc) UNKNOWN After the fix: root@intel-x86-64:~# pslog -V pslog (PSmisc) 23.7 (From OE-Core rev: f149a9541789286299c1afb84f61df0484d0f72e) Signed-off-by: Yi Zhao <yi.zhao@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* procps: fix runtime version when using git shallow tarballYi Zhao2025-07-031-1/+1
| | | | | | | | | | | | | | | | | | | | | | Add tag to SRC_URI to fix runtime version when using git shallow tarball. Before the fix: root@intel-x86-64:~# ps -V ps from procps-ng UNKNOWN root@intel-x86-64:~# sysctl -V sysctl from procps-ng UNKNOWN After the fix: root@intel-x86-64:~# ps -V ps from procps-ng 4.0.5 root@intel-x86-64:~# sysctl -V sysctl from procps-ng 4.0.5 (From OE-Core rev: 02f944088430c7cc023366d7cb5f92d7dcb62dfb) Signed-off-by: Yi Zhao <yi.zhao@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sanity: Reference gcc/g++ directlyRichard Purdie2025-07-031-6/+6
| | | | | | | | | | | | | BUILD_CC and BUILD_CXX can be overridden on a per recipe context now so these tests don't make sense in this form any more. They assume gcc/g++ so lets just use those directly. This fixes things to work with toolchain selection for the native case. (From OE-Core rev: cc93781667cf4f6971bcb9319ab8ab21320852de) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sanity/utils: Directly use gcc, not BUILD_CCRichard Purdie2025-07-032-17/+9
| | | | | | | | | The test/helper is written assuming gcc, so just call that and stop accessing BUILD_CC which may be set to clang. (From OE-Core rev: 0a165a93693a293f08cb0d7e2dfa1016803a917a) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* uninative/utils: Drop workarounds for gcc 4.8/4.9Richard Purdie2025-07-035-42/+3
| | | | | | | | | We require at least gcc 8.0 in sanity.bbclass so drop the 4.8/4.9 special case handling in uninative. (From OE-Core rev: 552e037bf598ac523f35b69d2dafc99e5ba59c5f) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sanity: Require minimum of bitbake 2.15.1Richard Purdie2025-07-011-1/+1
| | | | | | | | This is needed for tinfoil and umask helper function changes. (From OE-Core rev: d1c39b29f21719b349072c51a761fa19770a49ea) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* base: Use OE_SHARED_UMASK for do_fetchRichard Purdie2025-07-011-0/+1
| | | | | | | | | The intent has always been to share DL_DIR, so set the umask accordingly to the new OE_SHARED_UMASK variable and match expectations. (From OE-Core rev: 00e9bfbd29f3959adfc2c64ec78285a11ff83821) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf/sstate: Introduce OE_SHARED_UMASK to standarise shared area umaskRichard Purdie2025-07-012-5/+9
| | | | | | | | | | Currently, the "shared" directory permissions of sstate are hardcoded. Since multiple areas of the code reference this, separate it out to a variable to allow the behaviour to be configurable. Initially this applies to SSTATE_DIR. (From OE-Core rev: ce32daa9843bcb5f6daf3560c64ca9e5144adcb0) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-wheel: upgrade 0.45.1 -> 0.46.1; add ptestTim Orling2025-07-012-2/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Add python3-packaging to RDEPENDS * Enable ptest: - Add to ptest-packagelists.inc PTESTS_FAST - inherit ptest-python-pytest - Add python3-setuptools to ptest RDEPENDS - One test is skipped, but it requires the "full" python3-flit, not just python3-flit-core. Comparing changes since 0.45.1: https://github.com/pypa/wheel/compare/0.45.1...0.46.1 Release notes [1]: 0.46.1 (2025-04-08) * Temporarily restored the wheel.macosx_libfile module (#659) 0.46.0 (2025-04-03) * Dropped support for Python 3.8 * Removed the bdist_wheel setuptools command implementation and entry point. The wheel.bdist_wheel module is now just an alias to setuptools.command.bdist_wheel, emitting a deprecation warning on import. * Removed vendored packaging in favor of a run-time dependency on it * Made the wheel.metadata module private (with a deprecation warning if it’s imported * Made the wheel.cli package private (no deprecation warning) * Fixed an exception when calling the convert command with an empty description field [1] https://wheel.readthedocs.io/en/stable/news.html (From OE-Core rev: 610ca66283b6a440a1cde4c26945392ed15ac3e0) Signed-off-by: Tim Orling <tim.orling@konsulko.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* json-c: Remove icecc specific commentMoritz Haase2025-07-011-2/+1
| | | | | | | | | | | | | | | | | | 6481e8b209b ("json-c: fix icecc compilation") disabled '-Werror' unconditionally for all compilers. We want to keep it disabled to reduce efforts when updating or adding support for new toolchains (see [0]), but since support for icecc has been removed via ba4fd5229893 ("classes/recipes-devtools: Drop icecc from OE-Core") recently, we can drop the comment referencing it. [0]: https://lists.openembedded.org/g/openembedded-core/message/219364 (From OE-Core rev: 8b5466701979931506bb179812a0a66ed9b43c1c) Signed-off-by: Moritz Haase <Moritz.Haase@bmw.de> CC: quentin.schulz@cherry.de CC: m.felsch@pengutronix.de CC: ross.burton@arm.com Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ninja: upgrade 1.12.1 -> 1.13.0Randy MacLeod2025-07-011-3/+7
| | | | | | | | | | | | | | | | | | | | | | Changelog: ========== - Ninja now automatically joins a GNU Make jobserver as a client (version 4.4 on non-Windows systems required for "fifo" style) #1139 - Print exit code of failed subcommands #1507 - ninja -t compdb accepts a target #1544 - Support for ANSI (color) escape codes in NINJA_STATUS #713 See: https://github.com/ninja-build/ninja/milestone/8?closed=1 for a complete list of changes. Add tag to SRC_URI as is now required. Also line-wrap the DESCRIPTION. (From OE-Core rev: 79f1b70dacfcd841aa8252fba77df5f6b11e3c96) Signed-off-by: Randy MacLeod <Randy.MacLeod@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqa/sdk: Simplify test specification and discoveryThune Tran2025-07-0111-20/+29
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Simplify how tests are specified and discovered for different SDK configurations to allow per-layer customization. * Introduce `TESTSDK_CASE_DIRS` variable to specify test directory types, replacing the need to modify the default_cases class member * Discover tests from configured layers using a common discovery pattern (`<LAYER_DIR>/lib/oeqa/<dirname>/cases`) where `<dirname>` is specified in `TESTSDK_CASE_DIRS` * The buildtools directories were renamed to follow the common discovery pattern (`<LAYER_DIR>/lib/oeqa/<dirname>/cases`) for consistency across all SDK configurations. meta/lib/oeqa/ ├── sdk/cases/ # Standard SDK: dirname="sdk" ├── buildtools/cases/ # Buildtools: dirname="buildtools" └── buildtools-docs/cases/ # Buildtools-docs: dirname="buildtools-docs" meta-mingw/lib/oeqa/ └── sdkmingw/cases/ # MinGW: dirname="sdkmingw" meta-foo/lib/oeqa/ └── sdk/cases/ # Standard SDK: dirname="sdk" Tested by: 1. Adding new tests using the default discovery pattern `<LAYER_DIR>/lib/oeqa/sdk/cases` and verifying they are discovered and executed. 2. Verifying existing SDK configuration tests work (requires -c populate_sdk first): * Standard SDK: `bitbake core-image-minimal -c testsdk` * Buildtools tarball: `bitbake buildtools-tarball -c testsdk` * Buildtools docs tarball: `bitbake buildtools-docs-tarball -c testsdk` * Mingw SDK: (SDKMACHINE = "x86_64-mingw32") `bitbake core-image-minimal -c testsdk` (From OE-Core rev: bde94c128c0b4e7e1ebea40f582b4dd6dcc965ff) Signed-off-by: Thune Tran <thune.a.tran@boeing.com> Signed-off-by: Chuck Wolber <chuck.wolber@boeing.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqa/selftest/devtool: update create_go test to match the new behaviourRoss Burton2025-07-011-23/+10
| | | | | | | | | Update the test now that the recipe uses go-mod-update-modules. (From OE-Core rev: 1030223a43aa4500c0d4ebd9dfacf60b44239481) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqa/sefltest/devtool: improve assignment matching in _test_recipe_contentsRoss Burton2025-07-011-1/+1
| | | | | | | | | | | | | This function assumed that all assignments are done with just "=". However, being able to check += or ?= is also useful, so use a regex to split the line and be more flexible about what an assignment operator looks like. (From OE-Core rev: bee528f38d39ed1f91319201e8a99c0b65c9f975) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* recipetool/create_go: proxy module fetching to go-mod-update-modulesRoss Burton2025-07-011-2/+2
| | | | | | | | | | Now that the go-mod-update-modules class exists, this Go handler can create a stub recipe and then proxy the module handling to the class. (From OE-Core rev: 0aa406d0582d32399c48dfa78f24adc75696112c) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* classes/go-mod-update-modules: add class to generate module listRoss Burton2025-07-011-0/+152
| | | | | | | | | | | | | | | Almost entirely based on the create_go.py module for recipetool by Christian Lindeberg <christian.lindeberg@axis.com>, this instead has the logic inside a class that can be used to update the list of Go modules that are used, both SRC_URI and LICENSE. Integration with devtool upgrade will come shortly, but it needs a bit more work. (From OE-Core rev: 34bb889ffaae15f89c5627610826b498697c51f2) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oe/licenses: move tidy_licenses from recipetoolRoss Burton2025-07-011-0/+15
| | | | | | | | | | This function, to tidy a license string, is useful outside of recipetool so move it to oe.license. (From OE-Core rev: 9d57b53169bc60b281510c49e54123941a17a8f5) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* go-mod.bbclass: Calculate GO_MOD_CACHE_DIR relative to ${UNPACKDIR}Peter Kjellerstedt2025-07-011-1/+1
| | | | | | | | | Adapt to the recent move of S from ${WORKDIR} to ${UNPACKDIR}. (From OE-Core rev: 5f8218c62637208259a94979fe9a8a9b672e4ea4) Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* dosfstools: Use standard fsck exit codesRicardo Simoes2025-07-013-3/+264
| | | | | | | | | | | | | | | | | | | | | | | | | This commit brings in `dosfstools` patches to make `fsck.vfat` exit codes adhere to the standard exit codes defined by `fsck`. See [1]. These will fix the interaction of `fsck.vfat` with other tools like `systemd-fsck` which expect the exit codes to be in line with the standard [2]. However, as of today the dosfstools maintainer(s) are invisible for over a year [3]. Thus, if upstream ever becomes active again, these patches should be reassessed. [1] https://github.com/dosfstools/dosfstools/issues/89 [2] https://man7.org/linux/man-pages/man8/systemd-fsck@.service.8.html [3] https://github.com/dosfstools/dosfstools/issues/210 (From OE-Core rev: d344a9d806b0a3ec1d14fe810c37592775075e9b) Signed-off-by: Ricardo Simoes <ricardo.simoes@pt.bosch.com> Signed-off-by: Mark Jonas <mark.jonas@de.bosch.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* buildtools-docs-tarball: add sphinx-argparse and sphinx-copybuttonAntonin Godard2025-07-011-0/+2
| | | | | | | | | | Include these sphinx extensions in the buildtools tarball to make them available when building the documentation. (From OE-Core rev: 2221a66a9d8d13a2d6040ab55f066ca39b1a6ea4) Signed-off-by: Antonin Godard <antonin.godard@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-sphinx-copybutton: add recipeAntonin Godard2025-07-012-0/+11
| | | | | | | | | | The sphinx-copybutton extension can be used to add a copy button to code blocks in the documentation. (From OE-Core rev: ebf14a6dc1a5fd041f4df4fd8c6f28da9d15c8f6) Signed-off-by: Antonin Godard <antonin.godard@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-sphinx-argparse: add recipeAntonin Godard2025-07-012-0/+14
| | | | | | | | | | | | This Sphinx extension can be used to autogenerate documentation for any python module returning an argument parser from argparse. It can used in places of the documentation where the --help output is currently hardcoded, and generate formatted documentation instead. (From OE-Core rev: 84d1a347195a3cd702468b01a71e787c3e007488) Signed-off-by: Antonin Godard <antonin.godard@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-urllib3: upgrade 2.4.0 -> 2.5.0Yogita Urade2025-07-011-1/+1
| | | | | | | | | | | | | | Includes fix for CVE-2025-50181 and CVE-2025-50182 Changelog: https://urllib3.readthedocs.io/en/stable/changelog.html#id1 https://github.com/urllib3/urllib3/blob/main/CHANGES.rst#250-2025-06-18 (From OE-Core rev: 4bd2fbd3f0e44f42b0abc6e32348aa915d98b87b) Signed-off-by: Yogita Urade <yogita.urade@windriver.com> Signed-off-by: Antonin Godard <antonin.godard@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* mtools: upgrade 4.0.48 -> 4.0.49Jinfeng Wang2025-07-011-1/+1
| | | | | | | | | | | | New version includes check for overlong file names, see [1]. [1] https://lists.gnu.org/archive/html/info-mtools/2025-06/msg00005.html (From OE-Core rev: 044c2bceefcc12262cb2421e8f1da5f6c2ed9f72) Signed-off-by: Jinfeng Wang <jinfeng.wang.cn@windriver.com> Signed-off-by: Antonin Godard <antonin.godard@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* create-spdx-2.2: support to override the version of a package in SPDX 2Hongxu Jia2025-07-011-3/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | By default, still use ${PV} as the the version of a package in SPDX 2 $ echo 'INHERIT:remove = "create-spdx"' >> conf/local.conf $ echo 'INHERIT += "create-spdx-2.2"' >> conf/local.conf $ bitbake acl $ jq . tmp/deploy/spdx/2.2/core2-64/recipes/recipe-acl.spdx.json ... "name": "acl", "summary": "Utilities for managing POSIX Access Control Lists", "supplier": "Organization: OpenEmbedded ()", "versionInfo": "2.3.2" }, ... Support to override it by setting SPDX_PACKAGE_VERSION, such as set SPDX_PACKAGE_VERSION = "${EXTENDPKGV}" in local.conf to append PR to versionInfo in SBOM 2 $ echo 'SPDX_PACKAGE_VERSION = "${EXTENDPKGV}"' >> conf/local.conf $ bitbake acl $ jq . tmp/deploy/spdx/2.2/core2-64/recipes/recipe-acl.spdx.json ... "name": "acl", "summary": "Utilities for managing POSIX Access Control Lists", "supplier": "Organization: OpenEmbedded ()", "versionInfo": "2.3.2-r0" }, ... (From OE-Core rev: 0bd069f526ee0d535477b75a4aa825b4cb589423) Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com> Signed-off-by: Antonin Godard <antonin.godard@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* tcf-agent: Add $@ to RANLIBKhem Raj2025-07-011-0/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | tcf-agent calls RANLIB ( if defined ) after calling AR to create the archive [1], when RANLIB is set to gcc-ranlib this goes unnoticed, since calling gcc-ranlib without any arguments silenlty does nothing and exits with return code 0, however, calling binutils ranlib or llvm-ranlib does demand library name as commandline option and since it is not there it exits with code 1 aarch64-poky-linux-musl-llvm-ranlib OVERVIEW: LLVM ranlib Generate an index for archives USAGE: aarch64-poky-linux-musl-llvm-ranlib archive... OPTIONS: -h --help - Display available options -V --version - Display the version of this program -D - Use zero for timestamps and uids/gids (default) -U - Use actual timestamps and uids/gids -X{32|64|32_64|any} - Specify which archive symbol tables should be generated if they do not already exist (AIX OS only) aarch64-poky-linux-musl-llvm-ranlib: error: an archive name must be specified make: *** [Makefile:53: obj/GNU/Linux/a64/Debug/libtcf.a] Error 1 When we add $@, to RANLIB then it becomes the make variable, $@ - An automatic Makefile variable that expands to the target name (the file being built) so the makefile target now rightly adds the .a filename to RANLIB call. Sent a patch upstream to add RANLIB for linux [2] [1] https://gitlab.eclipse.org/eclipse/tcf/tcf.agent/-/blob/master/agent/Makefile?ref_type=heads#L53 [2] https://gitlab.eclipse.org/eclipse/tcf/tcf.agent/-/merge_requests/7 (From OE-Core rev: ee2df4554804cc08906cf7b5c734b234c7913c5f) 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>
* systemd: Refresh patch to remove patch fuzz on muslKhem Raj2025-06-291-9/+2
| | | | | | | (From OE-Core rev: 1f40f932309a1d3f8ac316016f2ba1e3b6b4b92a) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* spdx30_tasks: Change recipe license to declaredJoshua Watt2025-06-261-1/+1
| | | | | | | | | | | Per discussion with the SPDX licensing group, recipe LICENSE statements classify as a declared license, not a concluded license. (From OE-Core rev: 561447c7cc1485366dbf41cfbf8dcc1cbf29d043) Signed-off-by: Joshua Watt <JPEWhacker@gmail.com> Signed-off-by: Antonin Godard <antonin.godard@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* clang: multilib-header fix for llvm/Config/llvm-config.h and ↵Liu Yiding2025-06-261-1/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | clang/Config/config.h Error: Transaction test error: file /usr/include/clang/Config/config.h conflicts between attempted installs of lib32-clang-dev-20.1.4-r0.core2_32 and clang-dev-20.1.4-r0.core2_64 file /usr/include/llvm/Config/llvm-config.h conflicts between attempted installs of lib32-clang-dev-20.1.4-r0.core2_32 and clang-dev-20.1.4-r0.core2_64 reproduce steps: 1. Add in local.conf the following lines: MACHINE ?= "qemux86-64" require conf/multilib.conf MULTILIBS ?= "multilib:lib32" DEFAULTTUNE:virtclass-multilib-lib32 ?= "core2-32" 2. add lib32-llvm-dev llvm-dev to core-image-minimal.bb IMAGE_INSTALL = "packagegroup-core-boot ${CORE_IMAGE_EXTRA_INSTALL} lib32-clang-dev clang-dev" 3. $ bitbake core-image-minimal (From OE-Core rev: e2631fd1b47ed2d2b877426c4f253e6edea24ece) Signed-off-by: Liu Yiding <liuyd.fnst@fujitsu.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* selftest: move pokybleeding selftest from meta to meta-pokyAlexander Kanavin2025-06-261-32/+0
| | | | | | | | | | meta/ is 'owned' by oe-core and meta-yocto repo should not be putting files in it. (From meta-yocto rev: 83be7b1c70a7f90f611ad33284d0b8f963552eae) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* nfsrootfs: disable warning message if bootargs root parameter have not been ↵Jimmy Ho2025-06-261-1/+1
| | | | | | | | | | | | | | defined we have case that don't define root in bootargs, if [ ${bootparam_root} != "/dev/nfs" ] will output warning "/init.d/85-nfsrootfs: line 4: [: !=: unary operator expected" let variable expension result become string to solve this problem (From OE-Core rev: d50e12e5ae6a72535cacd0f767b1be1f89278f79) Signed-off-by: Jimmy Ho <jimmy.ho@sifive.com> Signed-off-by: Antonin Godard <antonin.godard@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* image-live.bbclass: support disable isohybrid for EFI-only bootHongxu Jia2025-06-261-1/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | While NO PCBIOS and EFI only for ISO 9660 image, burn the image to SandDisk USB stick, plug it into laptop, then boot laptop and enter UEFI mode, there are two boot options in UEFI system. Here is the steps: $ echo 'MACHINE = "genericx86-64"' >> conf/local.conf $ echo 'MACHINE_FEATURES:remove = "pcbios"' >> conf/local.conf $ echo 'IMAGE_FSTYPES:pn-core-image-minimal = " live"' >> conf/local.conf $ bitbake core-image-minimal $ sudo dd if=tmp/deploy/images/genericx86-64/core-image-minimal-genericx86-64.rootfs.iso of=/dev/sda Boot laptop and entery UEFI mode ... Boot mode is set to: UEFI UEFI BOOT: UEFI: SanDisk UEFI: SanDisk 2 ... In this case, PCBIOS is not used, calling isohybrid for ISO 9660 image is not necessary, and do not call isohybrid for ISO 9660 image could remove duplicated boot option in UEFI mode. According to [1][2], use `[ "${PCBIOS}" != "1" ] && [ "${EFI}" = "1" ]' as the EFI-only condition, the revert condition is `[ "${PCBIOS}" = "1" ] || [ "${EFI}" != "1" ]' [1] https://git.openembedded.org/openembedded-core/commit/?id=be3fc8c07e84c654f55c5d09934dfbdc7ff7e2b6 [2] https://git.openembedded.org/openembedded-core/commit/?id=be95f54495bf9e03062f86b929c66cab6e385a03 (From OE-Core rev: 4ea24276ad3b6cf3d63a839f3c5fbe697ccd28cd) Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com> Signed-off-by: Antonin Godard <antonin.godard@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* util-linux: replace submitted patches with a merged oneChen Qi2025-06-263-59/+10
| | | | | | | | | | The original PR, https://github.com/util-linux/util-linux/pull/3605, was updated. Use the merged patch to avoid any confusion. (From OE-Core rev: ae5a6fe3bb1bb5f42eb653aeccb2d76ab142d6fe) Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqq/runtime/ethernet_ip_connman: remove test_set_virtual_ip referenceMikko Rapeli2025-06-261-1/+0
| | | | | | | | | | | | | | It was removed. Fixes test loading after testexport.bbclass has exported the tests: oeqa.core.exception.OEQADependency: TestCase ethernet_ip_connman.Ethernet_Test.test_get_ip_from_dhcp depends on ethe rnet_ip_connman.Ethernet_Test.test_set_virtual_ip and isn't available, cases available odict_keys(['apt.AptRepoTest. test_apt_install_from_repo', 'boot.BootTest.test_reboot', 'buildcpio.BuildCpioTest.test_cpio', ... (From OE-Core rev: 6112eb97e20c1fb38acb9e78e89876c4302f65b8) Signed-off-by: Mikko Rapeli <mikko.rapeli@linaro.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* yocto-uninative: Update to 4.8 for GCC 15.1Michael Halstead2025-06-261-4/+4
| | | | | | | (From OE-Core rev: f3bff45196bb8228d0133b6cd4444e5ddc68dbc2) Signed-off-by: Michael Halstead <mhalstead@linuxfoundation.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-smartypants: upgrade 2.0.0 -> 2.0.2Trevor Gamblin2025-06-262-11/+17
| | | | | | | | | | | | | | | | | | | | | | | | Changelog (https://github.com/justinmayer/smartypants.py/blob/main/CHANGES.rst#releases-20-and-greater): Release 2.0.2 (2025-06-17) - Fix double closing quotes after an HTML block - Fix regular expressions and tests for Python 3.12+ - Move documentation to ReadTheDocs Release 2.0.1 (2017-12-20) - use re.match instead of re.search to improve performance on large strings The patch '0001-Change-hash-bang-to-python3.patch' needed a refresh to apply on the latest version. License-Update: Update and granularize copyright years (From OE-Core rev: ebb83ce10fecd1a4378a238191f1e012f0c849b7) Signed-off-by: Trevor Gamblin <tgamblin@baylibre.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-pytest-subtests: upgrade 0.14.1 -> 0.14.2Tim Orling2025-06-261-1/+1
| | | | | | | | | | | | | | | | | | | | Highlights from commit logs: * Bump pypa/gh-action-pypi-publish from 1.12.2 to 1.12.3 (#177) * Bump hynek/build-and-inspect-python-package from 2.10 to 2.11 (#178) * Consistently use raw strings for line-matching regexes (#180) * Ensure advertised pytest 7.4 compatibility (#182) * Bump pypa/gh-action-pypi-publish from 1.12.3 to 1.12.4 (#185) * Bump hynek/build-and-inspect-python-package from 2.11 to 2.12 (#186) * Print output "dots" for successful unittest subtests (#164) (#190) * Improve reporting in case of xfail (#194) Comparing changes from 0.14.1 -> 0.14.2: https://github.com/pytest-dev/pytest-subtests/compare/v0.14.1...v0.14.2 (From OE-Core rev: 91eaaf0672c5e811fa51d6c4181bd5faf10c2201) Signed-off-by: Tim Orling <tim.orling@konsulko.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-certifi: upgrade 2025.4.26 -> 2025.6.15Tim Orling2025-06-261-2/+2
| | | | | | | | | | | | | | | | * Switch to PEP-517 backend with inherit python_setuptools_build_meta Commit log highlights: * Declare setuptools as the build backend in pyproject.toml (#350) * remove code that's no longer required that 3.7 is our minimum (#351) Comparing changes from 2025.4.26 -> 2025.6.15: https://github.com/certifi/python-certifi/compare/2025.04.26...2025.06.15 (From OE-Core rev: fa38fa24ad26f8bf68fd139b5e8496144987326b) Signed-off-by: Tim Orling <tim.orling@konsulko.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-cryptography{-vectors}: upgrade 45.0.3 -> 45.0.4Tim Orling2025-06-264-5/+5
| | | | | | | | | | | | | https://cryptography.io/en/latest/changelog/#v45-0-4 45.0.4 - 2025-06-09 Fixed decrypting PKCS#8 files encrypted with SHA1-RC4. (This is not considered secure, and is supported only for backwards compatibility.) (From OE-Core rev: fbed96588a48c8d9bb9fe617d9d71168cef01e5c) Signed-off-by: Tim Orling <tim.orling@konsulko.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-maturin: upgrade 1.8.7 -> 1.9.0Tim Orling2025-06-262-11/+13
| | | | | | | | | | | | | | | | | | | * Update crates 1.9.0 * Add full PEP 639 support for project.license and project.license-files in #2647. * Add --compatiblity pypi to only build wheels with platform tags that can also be uploaded to PyPI. This blocks e.g. building for riscv64, which is supported by manylinux, but not by PyPI. Comparing changes from v1.8.7 -> v1.9.0: https://github.com/pyo3/maturin/compare/v1.8.7...v1.9.0 (From OE-Core rev: 4b8a23ed81ef08de8542da59027c929ad623e804) Signed-off-by: Tim Orling <tim.orling@konsulko.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-maturin: upgrade 1.8.6 -> 1.8.7Tim Orling2025-06-263-121/+25
| | | | | | | | | | | | | | | | | | | | * Drop riscv32 patch as it has been fixed upstream https://github.com/PyO3/maturin/commit/90b30a4e94e58e8d77d5d663cd2e0bbaab933f33 * Update crates https://www.maturin.rs/changelog.html 1.8.7 Allow specifying compression method and level, in both build and develop modes, in #2625. Fix Windows free-threaded builds on Python 3.14 in #2632 Comparing changes from v1.8.6 to v1.8.7: https://github.com/PyO3/maturin/compare/v1.8.6...v1.8.7 (From OE-Core rev: 61d2e2f67c387f976a3c6a165243c74bca66b3f4) Signed-off-by: Tim Orling <tim.orling@konsulko.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqa/sstatetests: Improve/fix sstate creation testsRichard Purdie2025-06-261-48/+30
| | | | | | | | | | | | | | | | | | | | | | There are multiple problems with the sstate creation tests. They currently both execute twice, once to check one set of files, then another. We can do this together in one test which makes the code easier to follow. The common test function also has parameters which were always the same value, so those can be simplified. We can use the umask context manager from bb.utils to simplfy the umask code. The badperms test was actually broken, it was detecting bad permissions, then ignoring them. This patch fixes that regression too and allows the check to operate (relying on a separate fix to sstate umask handling). The result should be an easier to understand couple of test cases which should also function correctly and be more reliable. (From OE-Core rev: 5b9263040013199c5cb480125d5ca349f5d6dc55) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqa/sstatetests: Fix NATIVELSBSTRING handlingRichard Purdie2025-06-261-7/+12
| | | | | | | | | | | | | | The NATIVELSBSTRING variable changes value once a BuildStarted event occurs in a build directory. This meant running some of the tests directly in a fresh build directory would fail but they'd pass when run as a group of tests. This is clearly suboptimal. Move the NATIVELSBSTRING handling to a location where the value is consistent and a comment about the interesting behaviour of the variable so it hopefully doesn't catch out others in future. (From OE-Core rev: e1c46fdb44fed18909d9ff4b43b4e445c5a22d33) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstate: apply proper umask when fetching from SSTATE_MIRRORRasmus Villemoes2025-06-261-10/+12
| | | | | | | | | | | | | | | | Currently, files and directories created under ${SSTATE_DIR} when fetching from an sstate mirror are not created with group write, unlike when the sstate artifacts are generated locally. That's inconsistent, and problematic when the local sstate dir is shared among multiple users. Wrap the fetching in a bb.utils.umask() context manager, and for simplicity move the mkdir of SSTATE_DIR inside that. (From OE-Core rev: a6038553aaef3b88b834a09018c524c4fa41e625) Signed-off-by: Rasmus Villemoes <ravi@prevas.dk> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* cargo-c-native: Update 0.10.5 -> 0.10.13Yash Shinde2025-06-263-446/+505
| | | | | | | | | | | | | cargo-c native version updated to stable version 0.10.13+cargo-0.88.0. https://crates.io/crates/cargo-c Drop the merged patch defining ioctl codes for riscv32 after the verion upgrade. (From OE-Core rev: 56abe99a953873853c726ee5a6458c4a65298a9c) Signed-off-by: Yash Shinde <Yash.Shinde@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* rust: Upgrade 1.86.0 -> 1.87.0Yash Shinde2025-06-2614-131/+186
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Rust stable version updated to 1.87.0. https://blog.rust-lang.org/2025/05/15/Rust-1.87.0/ * Update LLVM data-layout for arm64. LLVM requires matching data layouts and the aarch64 llvm data-layout was updated to to allow using 32-bit signed/unsigned pointers when building 64-bit targets using 270, 271 and 272 address spaces. https://github.com/rust-lang/rust/commit/e9853961452b56997cc127b51308879b9cd09482 https://github.com/llvm/llvm-project/commit/c9f27275c1330a325661bdf14fb3bc444a5e3648 * Rebase existing patches with v1.87.0. * Two tests from the `ui` and `codegen` modules now fail only on riscv64. Enable them on arm32/64 and x86-32/64 targets, while restricting them on riscv64 via `only-<target_arch>` tags. Test Results Summary: +-----------+--------+---------+ | Machine | Passed | Ignored | +-----------+--------+---------+ | arm-32 | 28,320 | 901 | | arm-64 | 28,400 | 849 | | x86-32 | 28,285 | 885 | | x86-64 | 28,518 | 676 | | riscv-64 | 27,845 | 868 | +-----------+--------+---------+ * Backport triagebot.patch to skip tidy linkcheck when triagebot.toml is not present. Distribution tarballs won't include triagebot.toml, which causes tidy checks to fail. This backport ensures tidy checks can still run successfully even when the file is missing. https://github.com/rust-lang/rust/pull/142666/commits * During rust installation, some binaries were installed from 'stage2-tools' built path to '${D}${bindir}'. However, from v1.87 the stage2-tools are no longer built by default. Update logic to install from `stage1-tools` instead. (From OE-Core rev: 16ce25e6970b4a50f6433606a0c87d22ec74ea5a) Signed-off-by: Yash Shinde <Yash.Shinde@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* rust: Drop obsolete rust-lld and extended tools dependenciesYash Shinde2025-06-261-8/+3
| | | | | | | | | | | | | | | | Some dependencies introduced during the v1.86 upgrade were needed only for rust-lld and certain LLVM extended tools, not for the Rust compiler itself. Since rust-lld and the extended tools are now disabled, these dependencies have become obsolete. Additionally, related tasks such as packaging zsh files and removing cargo binaries are no longer relevant. They can be re-enabled later if needed. (From OE-Core rev: 42141da566c9512b338900967e7e81e9e8b49150) Signed-off-by: Yash Shinde <Yash.Shinde@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2025-08-07 15:01:42 +0000