summaryrefslogtreecommitdiffstats
path: root/meta
Commit message (Collapse)AuthorAgeFilesLines
* lttng-modules: Upgrade 2.13.15 -> 2.13.16Richard Purdie2024-12-173-231/+1
| | | | | | | | Drop two patches merged upstream. (From OE-Core rev: 1bc656bac3bccbedde407a52969dfdca7f5a3c2b) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qemu: Upgrade 9.1.1 -> 9.2.0Richard Purdie2024-12-177-399/+2
| | | | | | | | Drop two patches merged upstream. (From OE-Core rev: 540ba2ce2f6d138b386d0d7545c197fd7f54edc8) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* subversion: Upgrade 1.14.4 -> 1.14.5Richard Purdie2024-12-171-1/+1
| | | | | | (From OE-Core rev: ca4efd307a1b06e58da8cf7617a94521d61c1e70) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-*: Update recipes to correctly check the upstream packagesDerek Straka2024-12-1740-31/+29
| | | | | | | | | | | | | | With the upstream check migrated to the simple repo API, a number of the recipes required updates to: 1. Remove outdated UPSTREAM_CHECK_REGEX checks 2. Add recipe specific UPSTREAM_CHECK_PYPI_PACKAGE definitions for packages that use '_', CamelCase, or other deviations from PEP625 in the source archive (From OE-Core rev: efbb98977664cd5392ec00d97d0eaf5374a32573) Signed-off-by: Derek Straka <derek@asterius.io> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* classes/pypi: update the default UPSTREAM_CHECK_URI to use the simple repo APIDerek Straka2024-12-171-3/+17
| | | | | | | | | | | | | | Update the UPSTREAM_CHECK_URI to leverage the simple repo API. The project URLs require javascript which breaks the version checking fetch and subsequent logic. The simple repo API provides similar functionality with a well defined spec which is used by tools such as pip. Also update the UPSTREAM_CHECK_REGEX to be compatible with the information retrieved via the API (From OE-Core rev: 10febb0e8193d15aec8bbf80b849ae6732da3c22) Signed-off-by: Derek Straka <derek@asterius.io> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* systemd: set CVE_PRODUCTMikko Rapeli2024-12-171-0/+2
| | | | | | | | | | | | | | | | systemd.inc is used by systemd, systemd-boot and systemd-tools-native recipes so make sure all match to "systemd" product in CVE database. The split between systemd, systemd-boot and systemd-tools-native is specific to oe-core and upstream just refers to systemd. Not limiting to "systemd_project" vendor since multiple vendor names have been used in the past. (From OE-Core rev: eb46ad379170f0a80ac2d061fa02c118f5ed1d31) Signed-off-by: Mikko Rapeli <mikko.rapeli@linaro.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* systemd: split networkd into its own packageAdrian Freihofer2024-12-171-3/+25
| | | | | | | | | | | | | | | | Support of images with different network management implementations without having to recompile systemd and other components. Fedora does this as well since systemd version 246.6-2: https://src.fedoraproject.org/rpms/systemd/blob/rawhide/f/systemd.spec#_578 This proves that it is technically possible and officially supported by systemd. (From OE-Core rev: 3664d14ef97281961d166f16e7d47996370e405d) Signed-off-by: Adrian Freihofer <adrian.freihofer@siemens.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* systemd.bbclass: do not automatically add Also servicesAdrian Freihofer2024-12-171-7/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Starting a systemd service “Also” does not mean that both services must be in the same package. However, the systemd.bbclass enforces this. Example: a.service: [Install] Also=b.service If a.service is packed in package A, b.service is automatically packed into package A as well. This happens even if b.service is explicitly added to package B using FILES and SYSTEMD_SERVICE variables. The automatic packing of socket files with the corresponding service files is probably a widely used feature of systemd.bbclass. This bahavior does not change. Adding regular service files to a package just because it is another service in the same package that "Also" uses the service is a bug that this commit fixes. (From OE-Core rev: f836d80eb48a2a2f9b1e66980021755cf0ca2a26) Signed-off-by: Adrian Freihofer <adrian.freihofer@siemens.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* systemd.bbclass: refactor adding filesAdrian Freihofer2024-12-171-16/+12
| | | | | | | | | | | | | | | The keys variable was intended as an array of keys. But it looks like this has not been used for more than 10 years now. Adding files automatically to packages needs probably anyway very specific code rather than a generic loop. Lets simplify this a bit. Using python code should also not be slower for these usually small files. (From OE-Core rev: 0eda7131bf743719d6586ccd36d99cbe11c88262) Signed-off-by: Adrian Freihofer <adrian.freihofer@siemens.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* dropbear: add dropbearkey.service to FILESAdrian Freihofer2024-12-171-0/+2
| | | | | | | | | | | | | | | dropbear.socket file contains: Also=dropbearkey.service That's why dropbearkey.service got automatically added to FILES. Since this incorrect auto adding feature gets dropped from systemd.bbclass this needs to be added explicitly. (From OE-Core rev: 4455e207a1ced3fb1d92b2f5e9335632bea08d15) Signed-off-by: Adrian Freihofer <adrian.freihofer@siemens.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* busybox: add klogd service to FILESAdrian Freihofer2024-12-171-1/+8
| | | | | | | | | | | | | | | busybox syslog.service file contains: Also=busybox-klogd.service That's why busybox-klog.service got automatically added to FILES:busybox-syslog. Since this incorrect auto adding feature gets dropped from systemd.bbclass this needs to be added explicitly. (From OE-Core rev: 60f1a82e25bd422fb1c380cd5b397718ab6dae13) Signed-off-by: Adrian Freihofer <adrian.freihofer@siemens.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* perf: Fix a minor typoLeon Anavi2024-12-161-1/+1
| | | | | | | | | Fix a minor typo in a comment by replacing "nsures" with ensures. (From OE-Core rev: c1f2df5616e9a14d1d6f2c993de8cc6204aea41f) Signed-off-by: Leon Anavi <leon.anavi@konsulko.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* build-appliance-image: Update to master head revision5.2_M1Richard Purdie2024-12-151-1/+1
| | | | | | (From OE-Core rev: e345b34703d4fa5e0bc9a82ac33b7c1fd84f99fe) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* systemd: upgrade 256.8 -> 256.9Wang Mingyu2024-12-154-1/+1
| | | | | | | (From OE-Core rev: 454cd1073bd5df167c284a34d6d1259263a859bb) Signed-off-by: Wang Mingyu <wangmy@cn.fujitsu.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* binutils: Fix CVE-2024-53589Yash Shinde2024-12-132-0/+93
| | | | | | | | | | | | | | | | | A buffer overflow vulnerability exists in GNU Binutils’ objdump utility when processing tekhex format files. The vulnerability occurs in the Binary File Descriptor (BFD) library’s tekhex parser during format identification. Specifically, the issue manifests when attempting to read 8 bytes at an address that precedes the global variable ‘_bfd_std_section’, resulting in an out-of-bounds read. Backport a patch from upstream to fix CVE-2024-53589. Upstream-Status: Backport [https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=e0323071916878e0634a6e24d8250e4faff67e88] (From OE-Core rev: 7c9a9020d1e9204ba875ac10b20ab7ccabce82bc) 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>
* barebox: upgrade 2024.10.0 -> 2024.12.0Wang Mingyu2024-12-132-4/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 0001-lib-lz4-use-lz4-instead-of-lz4c.patch removed since it's included in 2024.12.0 Changelog: =========== * ARM: omap: fix NS16550 UART setup in omap_debug_ll_init * Documentation: imd: update information on barebox_update * partitions: efi: Check GPT header size against minimum limit * checkpatch: fix detection of barebox root directory * ARM: omap: add two smaller MLO defconfigs for AM335x * crc: crc-itu-t: generate lookup table on first use * of: fdt: fix possible overflow during parsing of fdt * remoteproc: use I/O memory variants of memcpy/memset * dlmalloc: Fix integer overflow in request2size() * remoteproc: imx: add support for loading ELF data sections into DRAM * remoteproc: elf_loader: skip segment with memsz as zero * of: fdt: fix overflow caused by fdt_prop extending beyond fdt * usb: typec: fix freeing uninitialized memory Ahmad Fatoum * startup: do not bring up networking if console input disabled * sandbox: noshell_defconfig: set CONFIG_CONSOLE_DISABLE_INPUT=y * ARM: dts: i.MX8MP: disable NPU node if hardware is missing * clk: clk-composite: fix callback guard in clk_composite_round_rate * partitions: efi: fix overflow issues while allocating gpt entries * lib: lz4: use lz4 instead of lz4c * clk: rockchip: make it compile again * ARM: i.MX: ele: fix forward_lifecycle * ARM: i.MX9: tqma93xx: workaround warning in variant detection * partitions: efi: fix GPT header size exceeding allocation size * video: Rockchip: add missing dma_alloc_coherent a device parameter * dma: give dma_alloc_coherent a device parameter * common: buffer access out-of-bounds * include: Include <linux/math.h> to resolve implicit declaration of do_div() * i2c: lpi2c: fix potential read of uninitialized variable (From OE-Core rev: b8c26b320abce65862632f0e832d93ba37c6dc41) Signed-off-by: Wang Mingyu <wangmy@cn.fujitsu.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* curl: upgrade 8.11.0 -> 8.11.1Peter Marko2024-12-132-41/+1
| | | | | | | | | | | | | | Bugfix release for 8.11.0 regressions. Solves CVE-2024-11053 Drop patch which was done differently upstream. (From OE-Core rev: 57731284008c18eee566df3412eaf6d13a59d498) 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>
* curl: upgrade 8.10.1 -> 8.11.0Peter Marko2024-12-133-4/+46
| | | | | | | | | | | | | | | | | | | | | Solves CVE-2024-9681 * refresh patch * add patch for buildpaths issue * add new options for ipfs and websockets, keep them configure as they were previously configures * drop notexists.pl from ptest install as it was removed and code was integrated into the test framework in [1] * add ptest dependency on perl-module-i18n-langinfo due to [2] [1] https://github.com/curl/curl/commit/56183c1d6f7f4d0c18d9065cf870c4cd3fc329eb [2] https://github.com/curl/curl/commit/0b70b23ef4d007031bc2ae4fc63d5ed9136bc2b5 (From OE-Core rev: 86dd3aca63248e1982c2d8c9dc68ae34a358cf8b) 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>
* gcc: Fix c++: tweak for Wrange-loop-constructSunil Dora2024-12-132-0/+115
| | | | | | | | | | | | | | | | | | | | | This commit updates the warning to use a check for "trivially constructible" instead of "trivially copyable." The original check was incorrect, as "trivially copyable" only applies to types that can be copied trivially, whereas "trivially constructible" is the correct check for types that can be trivially default-constructed. This change ensures the warning is more accurate and aligns with the proper type traits. LLVM accepted a similar fix: https://github.com/llvm/llvm-project/issues/47355 PR c++/116731 [https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116731] (From OE-Core rev: 7c9402953d1e4eed4bd4427171e96761812f7478) Signed-off-by: Marek Polacek <polacek@redhat.com> Signed-off-by: Sunil Dora <sunilkumar.dora@windriver.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* icecc: don't use KERNEL_CC during set_icecc_envMarco Felsch2024-12-131-1/+1
| | | | | | | | | | | | | | | | | | | | | | The KERNEL_CC variable usage was introduced by commit d2fcaeb153fd ("icecc: Don't generate recipe-sysroot symlinks at recipe-parsing time, 2018-12-20") and is set once a recipe pulls the kernel-arch.bbclass. There are a few packages, e.g. u-boot, barebox, devicetree, perf which pull this class and for such packages the get_cross_kernel_cc() return None because icecc_is_kernel() fail. Fix this for now by replacing the KERNEL_CC check with the icecc_is_kernel() helper, which is also used by the get_cross_kernel_cc(). That said it's still not very robust to determine a compiler based on a variable or inherited class but at least it fixes the issue for now. (From OE-Core rev: 5e3c6a6384fcdc4a2269172012caae14e5f327ca) Signed-off-by: Marco Felsch <m.felsch@pengutronix.de> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* icecc: convert set_icecc_env to python prefuncsMarco Felsch2024-12-131-109/+91
| | | | | | | | | | | | | | | | | | | | | | | | | | Since bitbake commit f24bbaaddb36 ("data: Add support for new BB_HASH_CODEPARSER_VALS for cache optimisation") the icecc fails with [1]: ERROR: /Yocto/poky/meta/recipes-core/meta/target-sdk-provides-dummy.bb: no-pn NULL prefix WARNING: /Yocto/poky/meta/recipes-core/meta/target-sdk-provides-dummy.bb: Exception during build_dependencies for set_icecc_env The reason for this is the bb.fatal() within the icecc_version(). icecc_version() is called during the "${@}" python variable expansion while bitbake is running the build_dependencies() for the set_icecc_env() function. To avoid this behaviour set_icecc_env() should be converted into a python function which gets called during task[prefuncs] [2], which is done by this commit. [1] https://lists.yoctoproject.org/g/yocto/topic/icecc_support_broken/103429714 [2] https://lists.openembedded.org/g/openembedded-core/topic/110009272 (From OE-Core rev: 444445c5793aaf831ff0293b62a000f8ab7d40bb) Signed-off-by: Marco Felsch <m.felsch@pengutronix.de> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake-config-build: add a plugin for config fragmentsAlexander Kanavin2024-12-132-0/+190
| | | | | | | | | | | | | | | | | | | | | | | | | | This allows fine-tuning local configurations with pre-frabricated configuration snippets in a structured, controlled way. It's also an important building block for bitbake-setup. The tool requires that each fragment contains a one-line summary, and one or more lines of description, as BB_CONF_FRAGMENT_SUMMARY style metadata. There are three (and a half) operations (list/enable/disable/disable all), and here's the 'list' output: alex@Zen2:/srv/storage/alex/yocto/build-64$ bitbake-config-build list-fragments NOTE: Starting bitbake server... Available fragments in selftest layer located in /srv/work/alex/poky/meta-selftest: Enabled fragments: selftest/test-fragment This is a configuration fragment intended for testing in oe-selftest context Unused fragments: selftest/more-fragments-here/test-another-fragment This is a second configuration fragment intended for testing in oe-selftest context (From OE-Core rev: fdb611e13bd7aa00360d3a68e4818ef5f05c8944) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: add an addfragments directive for oe-core and dependent layersAlexander Kanavin2024-12-131-0/+3
| | | | | | | | | | | | Please see the patch to bitbake for syntax and implementation details. The path prefix to fragments is in its own variable so it doesn't have to be hardcoded into tools. (From OE-Core rev: 5bdbabd7b5d244a44c33065b04dd76dad76888a8) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* pixman: remove long-obsolete patchRoss Burton2024-12-132-138/+1
| | | | | | | | | | | | | | | This patch from the Nokia/Scratchbox days[1] was obsoleted by qemu improvements, specifically "linux-user: fake /proc/self/auxv"[2] which was integrated into qemu 1.1.0 in 2011. [1] If you're reading this and reminiscing I suggest standing up and having a stretch, your back will thank you [2] 257450ee59fd7e781cb4e2316ddc845c40b9fc42 (From OE-Core rev: b404dcbe9aeca9e82db929f021344ef3826726ab) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yoto/6.12: bsp/genericarm64: fix configuration warningBruce Ashfield2024-12-133-13/+13
| | | | | | | | | | | | | | | | | | | | | | | | Integrating the following commit(s) to linux-yocto/6.12: 1/1 [ Author: Ross Burton Email: ross.burton@arm.com Subject: arch/arm64/configs: remove CONFIG_SM_DISPCC_8650 Date: Thu, 12 Dec 2024 16:44:00 +0000 This option was removed from the Kconfig in in "clk: qcom: fold dispcc-sm8650 info dispcc-sm8550"[1] but it was not removed from the defconfig. [1] 802b83205519e4253b873bef5c095b147cd69dad Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com> ] (From OE-Core rev: bfed6922fc7ddf8bc30dc2ba5a3aae896d0a2de3) Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto: tweak cve exclusions filesBruce Ashfield2024-12-132-1/+6661
| | | | | | | | | | | | | | | -tiny and -rt were updated to a 6.12 specific inclusion, but the -standard kernel was missed. This commit also creates a 6.12 exclusion file, that is populated with the last updates for the 6.10 kernel. Although it is no longer updated automatically, that may change in the future and it still provides value as a place to manually add CVE exclusions. (From OE-Core rev: ab2e88ba876d954a2fc3eadee5ac860858340d5c) Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* systemd: actively disable Predictable Network Interface Names if !pni-namesAlexander Sverdlin2024-12-121-0/+3
| | | | | | | | | | | | | | | | | | | | | | | | Currently pni-names PACKAGECONFIG option adds "mac" names policy if selected, but nothing otherwise. In systemd Predictable Network Interface Names are applied by default which leads to inconsistend behaviour. One could think that pni-names in DISTRO_FEATURES would enable or disable Predictable Network Interface Names, but currently if not present it's only actively disabled for QEMU via kernel command line (commit 9e9c33d51e40 ("qemuboot/runqemu: Fix 6.2 and later kernel network device naming")). It has no effect on the real HW. If the option is present, it merely adds "mac" into default NamePolicy, which may or may not have observable effects. Make pni-names semantics more consistent by actively suppressing Predictable Network Interface Names if the feature is not present. (From OE-Core rev: 37b98bc93bc404823cc4bbf9039e4d114aac33fa) Signed-off-by: Alexander Sverdlin <alexander.sverdlin@siemens.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-firmware: package firmware for Qualcomm AIC100 and QDU100Dmitry Baryshkov2024-12-121-0/+10
| | | | | | | | | | | Split packages with firmware for Qualcomm AIC100 (AI accelerator) and QDU100 (5G RAN Accelerator). (From OE-Core rev: 856d828963a1bd3b2be0b5eef6df97ea682412c3) Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-firmware: upgrade 20241110 -> 20241210Dmitry Baryshkov2024-12-121-2/+2
| | | | | | | | | | License-Update: additional files (From OE-Core rev: 843d23d03bbfb5bdb7e82177ba97a569024838e3) Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sysvinit: upgrade 3.04 -> 3.11Changqing Li2024-12-127-120/+52
| | | | | | | | | | | | | | | | | | | | | Refresh patches: crypt-lib.patch install.patch pidof-add-m-option.patch realpath.patch Drop patches since upstream already include these changes: 0001-hddown-include-libgen.h-for-basename-API.patch sysvinit_remove_linux_fs.patch Refer: https://github.com/slicer69/sysvinit/releases (From OE-Core rev: f325557ef41737e2fc76bb97cd629b497cba4317) 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>
* maintainers.inc: add self for meson, python3 recipesTrevor Gamblin2024-12-121-4/+4
| | | | | | | | | | | | | | | | The following recipes recently had their maintainership given up, so list myself as maintainer for them: - meson - python3-markdown - python3-smartypants - python3-typogrify (From OE-Core rev: caaa2d4345e9d9e9f1a313c5f4f1ed4e3539fea3) 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>
* ovmf: update 202408 -> 202411Alexander Kanavin2024-12-125-33/+45
| | | | | | | | (From OE-Core rev: 6b420fc5212e7d02cc24942b74cc1307b97f6660) 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>
* librsvg: update 2.58.2 -> 2.59.2Alexander Kanavin2024-12-126-427/+439
| | | | | | | | | | | Upstream has moved from autotools to meson, which requires a substantial amount of tweaks to the recipe. (From OE-Core rev: ae4824f4f6234884a245bce314d6305ad8eb982d) 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>
* maintainers.inc: Update maintainer for pseudo and rpmRobert Yang2024-12-121-2/+2
| | | | | | | | (From OE-Core rev: cc9a55d464503ef1275daf4e2121741df8a4d750) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* classes/utility-tasks: port do_listtasks to use bb.build.listtasksRoss Burton2024-12-121-12/+11
| | | | | | | | | | | Instead of iterating every datastore value by hand to find tasks, use the new bb.build.listtasks() function (bitbake 185c4b) (From OE-Core rev: 466c3ed0d01bc70caa29d5eb8bb99f7d0e6e710c) 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>
* cargo-c: convert to target recipeAlexander Kanavin2024-12-122-2/+3
| | | | | | | | | | | | | | | This was prompted by sstatetests.SStateHashSameSigs2.test_sstate_allarch_samesigs where adwaita-icon-theme would fail due to new librsvg introducing cargo-c-native into dependency path. Rather than look into why is that, I simply converted the recipe into the standard 'target + BBCLASSEXTEND' approach. (From OE-Core rev: 80a2673a3081e623f30f25cc773ac9217e717958) 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>
* rpm: replace use of rpm2cpio with rpm2archiveAlexander Kanavin2024-12-125-11/+9
| | | | | | | | | | | | | | rpm2cpio has been deprecated upstream, so this prepares for its eventual removal. rpm2archive produces a tar archive which can be uncompressed with tar executable from the host. (From OE-Core rev: ed824d3fb23f0c89d8dfdacb2c4ef0b7c21a5144) 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>
* rpm: update 4.19.1.1 -> 4.20.0Alexander Kanavin2024-12-1217-119/+77
| | | | | | | | | | | | | | | | | | | | | With this release, as expected, deprecated openpgp support has been fully removed and replaced with sequoia: https://github.com/rpm-software-management/rpm-sequoia/ Alas, it's written in rust, and has no recipe, so for now signing rpm packages has to be disabled. Remove package name parameter to %prep in source archiving, as it's been dropped in the new rpm, and wasn't needed to begin with. Drop 0001-perl-disable-auto-reqs.patch (files removed upstream). (From OE-Core rev: 8c15b4577d5e554cc2dd5adfb88b816894b05a9a) 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>
* systemd-compat-units: execute postinst on targetAlexander Kanavin2024-12-121-1/+1
| | | | | | | | | | | | | | | | | | | | | | There is a race here where postinst relies on existence of various files from other packages on the target rootfs to operate properly, but doesn't ensure that it runs after all of those packages have been installed. Adding dependencies on those packages is not a solution as the recipe is not supposed to bring them into rootfs, only make adjustments if they are present. This commit moves postinst execution to the first boot; another solution would be to replace the whole recipe with ROOTFS_POSTPROCESS_COMMAND. This was exposed with rpm 4.20 which rearranges the order in which packages are installed, and exposes the issue. (From OE-Core rev: e88f22da19a7f3f9bf23f2a607ffde6b5b1a3265) 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>
* base.bbclass: fix RRECOMMENDS extend issue for multilibChangqing Li2024-12-121-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | During handle PACKAGECONFIG, DEPENDS/RDEPENDS/RRECOMMENDS is appended by calling function appendVar according to the PACKAGECONFIG setting: PACKAGECONFIG[f1] = "\ --with-f1, \ --without-f1, \ build-deps-for-f1, \ runtime-deps-for-f1, \ runtime-recommends-for-f1, \ packageconfig-conflicts-for-f1" [snip of base.bbclass] pkgconfigflags = d.getVarFlags("PACKAGECONFIG") or {} if pkgconfigflags: ... appendVar('DEPENDS', extradeps) appendVar('RDEPENDS:${PN}', extrardeps) appendVar('RRECOMMENDS:${PN}', extrarrecs) ... [snip of base.bbclass] After following commit in meta-oe, [fe3ba7ac5c cryptsetup: demote udev runtime dependency to recommendation] 'udev lvm2' changed from RDEPENDS to RRECOMMENDS, but RRECOMMENDS is not handled in this process, and causes following error: $bitbake lib32-cryptsetup ERROR: QA Issue: lib32-cryptsetup package lib32-cryptsetup - suspicious values 'udev lvm2' in RRECOMMENDS [multilib] In layer openembedded-core, we do have very few recipes that have runtime-recommends-for-f1 in PACKAGECONFIG setting, but f1 is not enabled in PACKAGECONFIGS, so not report error when multilib is enabled. (From OE-Core rev: 2f539a1318a80d3ad5d0d43a9ba4070465e402af) Signed-off-by: Changqing Li <changqing.li@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqa/selftest: Fix failure when configuration contains BBLAYERS:appendOleksandr Hnatiuk2024-12-121-0/+1
| | | | | | | | | | | | | | | | | | | | | When used with `--newbuilddir` option, it replaces relative paths in BBLAYERS variable with absolute paths by evaluating the final value of the variable, converting paths and saving result by assignment (`BBLAYERS =`) at the end of bblayers.conf. This breaks tests when bblayers.conf contains BBLAYERS:append because :append statements are evaluated after all assignments and we end up with the appended layer added twice - first by evaluating final value of the variable, then again by bitbake evaluating BBLAYERS:append. The error is as follows: AssertionError: Command 'bitbake -e' returned non-zero exit status 1: ERROR: Found duplicated BBFILE_COLLECTIONS 'layer-name', check bblayers.conf or layer.conf to fix it. (From OE-Core rev: 516c8e8f722ed0eb85a715a23b5e68d05abe9275) Signed-off-by: Oleksandr Hnatiuk <ohnatiuk@cisco.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* spdx 3.0: Rework how SPDX aliases are linkedJoshua Watt2024-12-123-135/+106
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The SPDX code needs to be able to look up an Element by its SPDX ID, locating the file that (should) contain the SPDX ID and opening it for parsing. Previously, the code would do this be hashing each Element SPDX ID and Alias, and the creating a symbolic link to the file that contains the element with a name of the hash. This worked well as it was possible to look up any arbitrary SPDX ID or alias by simply hashing it and following the symbolic link to get the file. However, the down side of this approach is that it creates a lot of symbolic links, since it will make one or two per Element in the document. This can be a problem when using SPDX_INCLUDE_SOURCES, for example. This change reworks this strategy so that the only Element that gets a symbolic link based on the hash is the singular SpdxDocument that is create for each file. All other Elements are assigned an alias with a special prefix that encodes the hash of SpdxDocument alias. Thus, when attempting to look up an arbitrary alias, the code sees the special prefix, extract the hash, opens the file based on the symlink with that hash name, then finds the matching Element in the file. This drastically reduces the number of symbolic links by making only one per file. This also means that the custom link extension can be removed since it is now superfluous. (From OE-Core rev: 838d64c09657ac53175737fc4e7fd6f01f3dcf47) Signed-off-by: Joshua Watt <JPEWhacker@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* classes-global/insane: Handle case where RPROVIDER is also a providerJoshua Watt2024-12-121-8/+13
| | | | | | | | | | | | | | | | | | | The check to see if a provider of a given package is listed first checks for an exact match of the provider name. However, if this match existed, but didn't match in the task dependencies, it would not continue to look for other providers of package. This would manifest if one (non-virtual) recipe package RPROVIDES the name of a package produced by another recipe. Fix this, and also clean up the code to make it more readable by using a function to check if a runtime dependency is in the task dependencies. In addition, if no provider is found, list all the possible providers instead of the last one that was looked at. (From OE-Core rev: f13de6ab616eb1e38960a2296111febe2a9f4a28) Signed-off-by: Joshua Watt <JPEWhacker@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* vte: upgrade 0.78.1 -> 0.78.2Wang Mingyu2024-12-121-1/+1
| | | | | | | (From OE-Core rev: 24dd3233c70659a0797d5e9a01c32e4b7f3d3d52) Signed-off-by: Wang Mingyu <wangmy@cn.fujitsu.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ttyrun: upgrade 2.35.0 -> 2.36.0Wang Mingyu2024-12-121-1/+1
| | | | | | | (From OE-Core rev: 4ce569996053b0e7c1ce0a63b03184576b8fd4dd) Signed-off-by: Wang Mingyu <wangmy@cn.fujitsu.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sudo: upgrade 1.9.16p1 -> 1.9.16p2Wang Mingyu2024-12-121-1/+1
| | | | | | | (From OE-Core rev: 1f64a8145f6eeed74301a96240148706e2d93c74) Signed-off-by: Wang Mingyu <wangmy@cn.fujitsu.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* stress-ng: upgrade 0.18.06 -> 0.18.07Wang Mingyu2024-12-121-1/+1
| | | | | | | (From OE-Core rev: b67f971f0b2c228ca46fbcd920ef36a285072dd8) Signed-off-by: Wang Mingyu <wangmy@cn.fujitsu.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sqlite3: upgrade 3.47.0 -> 3.47.2Wang Mingyu2024-12-121-1/+1
| | | | | | | (From OE-Core rev: 30ca306e0ee4adb1c15283e262b3b0e2dc1ead09) Signed-off-by: Wang Mingyu <wangmy@cn.fujitsu.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* re2c: upgrade 4.0 -> 4.0.1Wang Mingyu2024-12-121-1/+1
| | | | | | | (From OE-Core rev: d35ed87c4c7713d1ee38efc0863fbaf3515b1b9b) Signed-off-by: Wang Mingyu <wangmy@cn.fujitsu.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* pixman: upgrade 0.44.0 -> 0.44.2Wang Mingyu2024-12-121-1/+1
| | | | | | | (From OE-Core rev: 7bd537726242ae77cdda8daf8d291748b48aaa14) Signed-off-by: Wang Mingyu <wangmy@cn.fujitsu.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 17:41:53 +0000