summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
...
* dnf: drop python3-iniparse from DEPENDS and RDEPENDSGuðni Már Gilbert2024-12-031-2/+1
| | | | | | | | | | | | | | python3-iniparse dependency was dropped 2019, see the following commit as reference: https://github.com/rpm-software-management/dnf/pull/1329/commits/d7d0e0e2f9d8c7d021c794821ad0b56a39ebc01f When looking at the Git history, this happened around tag 4.2.1 (From OE-Core rev: 05220b4907ab654e829d97ab68d48f76330937dd) Signed-off-by: Guðni Már Gilbert <gudni.m.g@gmail.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-poetry-core: drop python3-six from RDEPENDSGuðni Már Gilbert2024-12-031-1/+0
| | | | | | | | | | | | | | | Looking at the history, python3-six was removed as a dependency in the poetry.lock file in v1.5.2 Even before v1.5.2 and until now (v1.9.1) there is no code in the package which imports the six module. So it can be safely dropped from the recipe. (From OE-Core rev: 1ed30cd9426e1f8a6caf31277f0349343a06f2d4) Signed-off-by: Guðni Már Gilbert <gudni.m.g@gmail.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* kmscube: Use COPYING for licensing informationFabio Estevam2024-12-031-1/+1
| | | | | | | | | | | | | | | | | | Since kmscube commit d874c7811854 ("add license file"), the COPYING file has been introduced for holding the licensing information for the project. Make LIC_FILES_CHKSUM point to the COPYING file to make the licensing text information more explicit instead of extracting it from the kmscube.c file. License-Update: Point to the dedicated COPYING file. (From OE-Core rev: 6615fa4428166a6f50c1350574bb760009cb957e) Signed-off-by: Fabio Estevam <festevam@denx.de> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc: remove unused JAVA variableRasmus Villemoes2024-12-031-1/+0
| | | | | | | | | | | | | | | | As commit 81551871b183 (gcc: Remove Java support variables) correctly stated Java support was removed in upstream gcc 7. but this line snuck back in with commit bbf32e24608c (gcc-9: Add recipes for gcc 9.1 release). (From OE-Core rev: 136619477f0ce7c9da0762bbbeb1227a1ad6c0c7) Signed-off-by: Rasmus Villemoes <ravi@prevas.dk> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libinput: upgrade 1.26.2 -> 1.27.0Wang Mingyu2024-12-031-2/+2
| | | | | | | | | | | Changelog: https://gitlab.freedesktop.org/libinput/libinput/-/releases (From OE-Core rev: 8517adafdaf3bfdcf6467e80e347b24cd154b406) Signed-off-by: Wang Mingyu <wangmy@fujitsu.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* buildhistory: Drop git-gc call as obsoleteRichard Purdie2024-12-031-1/+0
| | | | | | | | | | | | | | buildhistory used to result in many individual objects in the repo which could affect performance. This gc call was added over a decade ago to avoid those performance issues. Modern git calls git-gc when needed and this kind of workaround should no longer be needed. There is a small chance this is contributing to problems with the autobuilder buildhistory repositories, so simplifying the code may help that too. (From OE-Core rev: 0a88f9109f7670a6b188463a19392d445af6ff40) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gnu-efi: upgrade to 4.0.0Ross Burton2024-11-292-22/+17
| | | | | | | | | | | | gnu-efi isn't making releases on SourceForge anymore, so switch to git clones and track releases on GitHub. License-Update: "Copright" typo fixed. (From OE-Core rev: 958a1e5e911a3cd7912f9207528a2c9d61c2af6a) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gnu-efi: fix licenseRoss Burton2024-11-291-1/+1
| | | | | | | | | | gnu-efi is a mix of BSD and GPL licensed source code, not a choice between the two. (From OE-Core rev: 186ccb678a83468c8d1b8a457ed600921c932627) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gnu-efi: remove obsolete patchRoss Burton2024-11-292-42/+0
| | | | | | | | | | | | | | | | | The original patch in 2013[1] did this: +-libefi.a: libefi.a($(OBJS)) ++libefi.a: $(OBJS) The Makefile no longer uses this syntax and simply replacing $^ with $(OBJS) is a no-op, so this patch isn't needed. [1] meta-intel c2c13d4dba2d9c70862891adf0b250ce2be65f68 (From OE-Core rev: fd80af9abce3547f7e929e592bababd3c736bcee) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gnu-efi: pass HOSTCC and INCLUDEDIRRoss Burton2024-11-291-2/+5
| | | | | | | | | | | | Pass the correct host compiler (HOSTCC) and include directory to the build. Also enable verbose builds (V=1). (From OE-Core rev: 093e4222948b29dafc272c97b9f200e4b126cadd) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcr: correct gpg2 -> gpghongxu2024-11-291-2/+2
| | | | | | | | | | Due to commit [gnupg: upgrade 2.5.0 -> 2.5.1] applied, drop gpg2 and use gpg to instead (From OE-Core rev: ff50a4aba5394dc7c19a862f2cfbcd46ff9d6079) Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gnupg: upgrade 2.5.0 -> 2.5.1hongxu2024-11-297-26/+15
| | | | | | | | | | | | | | | | | | Due to upstream [build: Remove configure option --enable-gpg-is-gpg2][1], drop option --enable-gpg-is-gpg2 and remove gpg2/gpgv2 installation Due to upsream [doc: Remove included yat2m and build HTML versions of the man pages.][2], it used standard detection on yat2m other than build it from source. Because no native recipe provide yat2m in Yocto, explicitly disable doc via option --disable-doc [1] https://github.com/gpg/gnupg/commit/2125f228d36c0882a87bce433a18253154653d50 [2] https://github.com/gpg/gnupg/commit/60c541f5880e8c603ca9372d3ca8b7ad68b97018 (From OE-Core rev: 3a00465f4b0c01580fb27e0c462696bd4f840828) Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python: backport patches to support openssl 3.4.0Peter Marko2024-11-293-0/+1505
| | | | | | | | | | https://github.com/python/cpython/pull/127331 https://github.com/python/cpython/pull/127361 (From OE-Core rev: e5f3a1793e34fb4cd1e53ca60b67f9a9f084b7a6) Signed-off-by: Peter Marko <peter.marko@siemens.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* openssl: upgrade 3.3.1 -> 3.4.0Peter Marko2024-11-294-35/+28
| | | | | | | | | | | | | | Release information: https://github.com/openssl/openssl/blob/openssl-3.4/NEWS.md#major-changes-between-openssl-33-and-openssl-340-22-oct-2024 Handles CVE-2024-9143 Refreshed patches. (From OE-Core rev: 45c6b85ccc8157f0dd31eb3d5138832ced7966d5) Signed-off-by: Peter Marko <peter.marko@siemens.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: runqueue: Fix scenetask processing performance issueRichard Purdie2024-11-291-1/+5
| | | | | | | | | | | Analysis shows that "bitbake core-image-ptest-all" spends a lot of time in scenequeue_updatecounters and much of it is rebuilding a set which doens't change. Reorder the code to avoid that performance glitch. (Bitbake rev: 923c19b9713e398d8e66e6d4422dfd4c18a03486) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: runqueue: Optimise setscene loop processingRichard Purdie2024-11-291-2/+8
| | | | | | | | | | Rather than looping through things we looped through on the previous execution, start looping where we left off for setscene processing. This gives speed improvements depending on the kind of build being executed. (Bitbake rev: 00f4d932e3af0eeb333339cbe942010fc76dee0f) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: runqueue: Fix performance of multiconfigs with large overlapRichard Purdie2024-11-291-2/+4
| | | | | | | | | | | | | | | | | | | There have been complaints about the performance of large multiconfig builds for a while. The key missing data point was that the builds needed to have large overlaps in sstate objects. This can be simulated by building the same things with just different TMPDIRs. In runqueue/bitbake terms this equates to large numbers of deferred tasks. The issue is that the expensive checks in the setscene loop were hit every time through runqueue's execute function before the check on deferred tasks. This leads to task execution starvation as that only happens once per iteration. Move the skip check earlier in the function which speeds things up enormously and should improve performance of such builds for users. (Bitbake rev: 9c6c506757f2b3e28c8b20513b45da6b4659c95f) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* kmscube: Upgrade to the latest revisionFabio Estevam2024-11-292-33/+1
| | | | | | | | | | | Upgrade to the latest revision and remove the patch because the original problem has already been fixed upstream by kmscube commit 311eaaaa473d ("kmscube: gears: use only GLES2"). (From OE-Core rev: 3348b02f72bf7cf62f73cce74caffe2c51d43b1a) Signed-off-by: Fabio Estevam <festevam@denx.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* scocat: upgrade 1.8.0.0 -> 1.8.0.1hongxu2024-11-292-16/+16
| | | | | | | | | Rebase 0001-fix-compile-procan.c-failed.patch to 1.8.0.1 (From OE-Core rev: d9b9f3d5e034fa5fb92beb050a03856bbddf0383) Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gpgme: upgrade 1.23.2 -> 1.24.0hongxu2024-11-295-102/+39
| | | | | | | | | | | | | | | | | Reabse patches: - 0001-pkgconfig.patch - 0001-autogen.sh-remove-unknown-in-version.patch Drop backport patch: - 0004-python-import.patch Drop obsolete patch: - 0008-do-not-auto-check-var-PYTHON.patch (From OE-Core rev: 181205d5ccb3ba0473813cd62b19d95ba034ab0a) Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* man-db: upgrade 2.12.1 -> 2.13.0hongxu2024-11-292-40/+1
| | | | | | | | | | | | | Due to meta-clang has upgraded clang to 19.1.2 release [1] which contains clang fix [2], drop 0001-man-Move-local-variable-declaration-to-function-scop.patch [1] https://github.com/kraj/meta-clang/commit/d3180c5e597f587c822192caba3ceced2452b861 [2] https://github.com/llvm/llvm-project/commit/8bd06d5b6584 (From OE-Core rev: 779218621fc5c3c0498c489510a93f50528fba41) Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: fetch2: fix unpack of a single zstd filePascal Eberhard2024-11-291-1/+1
| | | | | | | | | | | | | | | | do_unpack generates a 'Bitbake Fetcher Error: UnpackError' when uncompressing a single 'file.zst', zstd command line returns the error 'unexpected end of file', and the input file 'file.zst' becomes empty. The command line is 'zstd --decompress --stdout file.zst > file.zst'. So the issue is that the input and output filenames are the same. Fix the output filename when using zstd for a single file. (Bitbake rev: 5881ca0e0d53937cd25a57ff682a3b7577b0b7f8) Signed-off-by: Pascal Eberhard <pascal.eberhard@se.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* migration-guides: add release notes for 4.0.23Lee Chee Yang2024-11-292-0/+210
| | | | | | | | (From yocto-docs rev: 5835cb574881d57785f099c768467177d077e867) Signed-off-by: Lee Chee Yang <chee.yang.lee@intel.com> Signed-off-by: Antonin Godard <antonin.godard@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual: classes: fix bin_package descriptionAntonin Godard2024-11-291-17/+28
| | | | | | | | | | | | | | | | The previous bin_package description was confusing: it would instruct to use the git fetcher to extract the content of an RPM package using the `subpath` option - but that's not possible as the git fetcher can be used to clone a repository but not to do the extraction. Update the description by telling what it really does and what it doesn't do, and by giving an HTTPS+RPM example. Reviewed-by: Quentin Schulz <quentin.schulz@cherry.de> (From yocto-docs rev: 305f024bf99ba02b153eed0cebe3d36594868497) Signed-off-by: Antonin Godard <antonin.godard@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* classes.rst variables.rst: add documentation for uki.bbclassMikko Rapeli2024-11-292-0/+92
| | | | | | | | | | | | | | Documentation for the new class. [YOCTO #15650] https://bugzilla.yoctoproject.org/show_bug.cgi?id=15650 (From yocto-docs rev: fd46074dc7bba49ab49c706c408c92958e67cfa4) Signed-off-by: Mikko Rapeli <mikko.rapeli@linaro.org> Reviewed-by: Antonin Godard <antonin.godard@bootlin.com> Signed-off-by: Antonin Godard <antonin.godard@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* migration-guides: add release notes for 5.0.5Lee Chee Yang2024-11-292-0/+228
| | | | | | | | (From yocto-docs rev: 4175839e718db49bf6971e900c1cf176d03458d7) Signed-off-by: Lee Chee Yang <chee.yang.lee@intel.com> Signed-off-by: Antonin Godard <antonin.godard@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* selftest/static-group: Add seatRichard Purdie2024-11-281-0/+1
| | | | | | | | | With a group added to the seatd recipe, we need an entry in our static group file for selftest. (From OE-Core rev: 655d334584769a9b9d86cf8fab2c06bc0878d0b3) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* weston-init: Make weston user member of seat groupKhem Raj2024-11-281-3/+2
| | | | | | | | | | This enables weston launch to access the seatd socket /run/seatd.sock to communicate properly to acquire seat (From OE-Core rev: c9f2ec1cccbf4b716364efd34a27138b34424212) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* seatd: Create seat user and package systemd serviceKhem Raj2024-11-282-3/+10
| | | | | | | | | | | | | | With latest version seatd does not work properly if user access permissions are not correctly set, therefore create 'seat' group and package the seatd.service file and enable it by default with systemd distro feature set logind to systemd when using systemd as default init system (From OE-Core rev: 26746a02fc94b569f633d581b27a8634cfba38f5) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* mtd-utils: upgrade 2.2.0 -> 2.2.1Alexander Kanavin2024-11-281-2/+2
| | | | | | | | (From OE-Core rev: 6cffa7312241236daea86449977375fd7b50de9f) 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>
* barebox: move version checksum to common .incEnrico Jörns2024-11-283-2/+5
| | | | | | | | | | | | This makes it more obvious to update barebox and barebox-tools together and should help the AUH to update both. Suggested-by: Alexander Kanavin <alex.kanavin@gmail.com> (From OE-Core rev: 9753d5cb44c2d648e19a2e7706590ca4390b2965) Signed-off-by: Enrico Jörns <ejo@pengutronix.de> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* barebox: upgrade 2024.09.0 -> 2024.10.0Enrico Jörns2024-11-281-1/+1
| | | | | | | | | | | | | | | Regular barebox release. * cleanups and bug fixes * larger font for high-res displays Changelog: https://lore.barebox.org/barebox/ZxIdBi3xLj0dHqzi@pengutronix.de/T/ (From OE-Core rev: 39166d2a5d5ab11513697c1a1c94284e30837a21) Signed-off-by: Enrico Jörns <ejo@pengutronix.de> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* cve-check: fix cvesInRecordPeter Marko2024-11-281-5/+6
| | | | | | | | | | | | | | | | | | | | | | Currently flag cvesInRecord is set to false if all CVEs are ignored or patched. This is inconsistent as it shows false if a CVE was fixed via patch and true if this CVE was fixed by upgrade. In both cases the CVE is valid and was fixed. As I understand this flag, it should say if any CVE exists for particular component's product (regardless of how this CVE is handled) and can be used to validate if a product is correctly set. Note that skipping ignored CVEs may make sense in some cases, as ignored may mean that NVD DB is wrong, but in many cases it is ignored for other reasons. Further patch can be done to evaluate ignore subtype but that would be against my understanding of this flag as described above. (From OE-Core rev: c5d499693672ec9619392011b765941cf94aa319) 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>
* cve-check: restore CVE_CHECK_SHOW_WARNINGS functionalityPeter Marko2024-11-281-0/+5
| | | | | | | | | | | | | | Commit 05ef4f2a7b225c8d230eaca8d333ffb921729d79 removed this functionality by accident. It was implemented in text exporter, while it should have been a global feature independent on exporter type to avoid such accidental deletion. (From OE-Core rev: 2996b11596afca288a6b7f409a5287063d331f3b) Signed-off-by: Peter Marko <peter.marko@siemens.com> Cc: Marta Rybczynska <marta.rybczynska@ygreky.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libssh2: mark CVE-2023-48795 as fixedPeter Marko2024-11-281-0/+3
| | | | | | | | | | | NVD DB has typo in version (1.11.10 instead of 1.11.1) Version 1.11.1 is the currently the latest one, there is no .10 (From OE-Core rev: 92886f91dc6ed3f41771bc984aa11269bd68abe0) 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>
* qemu: Fix build on riscv64Khem Raj2024-11-282-0/+42
| | | | | | | | (From OE-Core rev: 50383df4d704053383d20ab9e2a40cd1ef49b8d5) 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>
* default-providers: define keymaps virtual runtime providerPeter Marko2024-11-284-7/+1
| | | | | | | | | | | | VIRTUAL-RUNTIME_keymaps is defined in busybox init manager and also in some package groups. Defining distro features in recipes is wrong. Also this is not directly related to init manager. So move all these definitions to default-providers.inc (From OE-Core rev: 00f667bb5007a372950a137bf9e8b0e62f44f7d6) Signed-off-by: Peter Marko <peter.marko@siemens.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* init-manager: define dev_manager for all init managersPeter Marko2024-11-284-1/+5
| | | | | | | | | | | | | | | | | | | | | | | | | Currently VIRTUAL-RUNTIME_dev_manager is defined by some init managers with "??=" and in packagegroup-core-boot with "?=". This means that this variable is different in this package group and in all other the recipes. This was discovered when trying to use new feature INIT_MANAGER when migrating to scarthgap and using systemd distro. After deleting all VIRTUAL_RUNTIME providers defined in init-manager-systemd udev was installed additionally via packagegroup-core-boot. Having a distro settings overriden in single recipe is wrong and needs to be corrected. Therefore let's define the setting in all init managers and remove it from packagegroup-core-boot. core-image-tiny-initramfs has a dilemma - use busybox-mdev even if distro does not enable it in busybox recipe to keep the image tiny, or rather not install it even if distro enables it in busybox. This patch chooses the first option. (From OE-Core rev: 89e2652ac83f2602d6dd60623a225b88dc67d288) Signed-off-by: Peter Marko <peter.marko@siemens.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* kernel-uboot: Support lzma compressed algorithmJamin Lin2024-11-281-0/+2
| | | | | | | | | | | | | | | | | | | Linux kernel supports to compress its output binary with lzma algorithm and U-Boot support to decompress lzma compressed image. Both xz and lzma algorithms are identical and users can use xz utility with format parameter to compress Image which supports lzma algorithm. Add the following command to support lzma. This command is refer to Linux kernel, https://github.com/torvalds/linux/blob/master/arch/powerpc/boot/wrapper "xz --format=lzma -f -6 linux.bin" (From OE-Core rev: 211178065bdca293c84c41a9a1e79c10df95b6ad) Signed-off-by: Jamin Lin <jamin_lin@aspeedtech.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* tcl: resolve conflicts with tcl8's man pagesThomas Perrot2024-11-282-2/+2
| | | | | | | | | | | | | | | | | | Change the suffix from 'tcl' to 'tcl9' and from 'tcl8' to avoid conflicts with the man pages provided by the tcl packages. file /usr/share/man/mann/vwait.ntcl conflicts between attempted installs of tcl-doc-9.0.0-r0.riscv64 and tcl8-doc-8.6.15-r0.riscv64 file /usr/share/man/mann/while.ntcl conflicts between attempted installs of tcl-doc-9.0.0-r0.riscv64 and tcl8-doc-8.6.15-r0.riscv64 file /usr/share/man/mann/yield.ntcl conflicts between attempted installs of tcl-doc-9.0.0-r0.riscv64 and tcl8-doc-8.6.15-r0.riscv64 file /usr/share/man/mann/yieldto.ntcl conflicts between attempted installs of tcl-doc-9.0.0-r0.riscv64 and tcl8-doc-8.6.15-r0.riscv64 file /usr/share/man/mann/zlib.ntcl conflicts between attempted installs of tcl-doc-9.0.0-r0.riscv64 and tcl8-doc-8.6.15-r0.riscv64 [...] (From OE-Core rev: b961021cc47c53ddd602e6038f5faf02416455b3) Signed-off-by: Thomas Perrot <thomas.perrot@bootlin.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3: package tkinter's shared objectsDan McGregor2024-11-281-0/+1
| | | | | | | | | | | | | | | Seems every time python is updated this gets removed. That's likely because the tk option can't be enabled in python3-native without creating a dependency loop. Instead of manually editing the manifest every time, explicitly add it in the recipe as suggested by Alexander Kanavin. (From OE-Core rev: d2e82fc12509950ea30fa20fcbe9fc148b6cff1c) Signed-off-by: Dan McGregor <dan.mcgregor@usask.ca> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3: do not overwrite FILES contentsDan McGregor2024-11-281-1/+0
| | | | | | | | | | | | | | | Instead of relying completely on the python packaging manifest, allow some default values. This is useful for the edge cases that can't be found automatically by the create_manifest step. In particular, tkinter can't be built for python3-native, so its consistently missed in manifest updates. (From OE-Core rev: cc5ec75b50618ce42d5b19d0aad0b44611bf8fbe) Signed-off-by: Dan McGregor <dan.mcgregor@usask.ca> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-flit-core: upgrade 3.9.0 -> 3.10.1Ross Burton2024-11-281-7/+1
| | | | | | | | | | | | | | | | | | | | | | | | | Summary of changes: - The ``--python`` option can now take the path of a virtualenv folder, as an alternative to a Python executable. - The metadata in packages now has the names of optional dependency groups ("extras") normalised, complying with version 2.3 of the metadata standard. - Fix potential substitution of environment variables into passwords read from ``.pypirc`` files. - A warning is now shown when building packages which specify the old ``flit.buildapi`` backend, which should be replaced by ``flit_core.buildapi``. It's a good idea to always set a maximum version for the build requirement, to protect against changes in future major versions of Flit. - Avoid using the deprecated ``datetime.utcfromtimestamp()``. - The tests for ``flit_core`` are no longer part of the installed package, reducing the size of the wheels. Remove the -tests package, as the tests are no longer installed. (From OE-Core rev: 102e3524361d7d07f0dee09b1b12346b1184268f) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-numpy: inherit pkgconfigTrevor Gamblin2024-11-281-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This was supposed to be added in oe-core commit fd656aaf7fbe ("python3-numpy: upgrade 1.26.4 -> 2.1.3"), but it somehow got missed in the final version of that patch. Add it now to fix possible do_compile errors on some systems, due to host paths sneaking into the meson build options, e.g.: | Build machine cpu family: x86_64 | Build machine cpu: x86_64 | Host machine cpu family: x86_64 | Host machine cpu: x86_64 | Target machine cpu family: x86_64 | Target machine cpu: x86_64 | Program python3 found: YES (/home/tgamblin/workspace/yocto/poky/build/tmp/work/core2-64-poky-linux-musl/python3-numpy/2.1.3/recipe-sysroot-native/usr/bin/nativepython3) | Did not find pkg-config by name 'pkg-config' | Found pkg-config: NO | Run-time dependency python found: NO (tried pkgconfig, pkgconfig and sysconfig) | | ../numpy-2.1.3/meson.build:41:12: ERROR: Python dependency not found | | A full log can be found at /home/tgamblin/workspace/yocto/poky/build/tmp/work/core2-64-poky-linux-musl/python3-numpy/2.1.3/build/meson-logs/meson-log.txt and notably (meson-log.txt snippet): |x86_64-poky-linux-musl-g++ -m64 -march=core2 -mtune=core2 -msse3 -mfpmath=sse -fstack protector-strong -O2 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security --sysroot=/media/build/poky/build/tmp/work/core2-64-poky-linux-musl/python3-numpy/2.1.3/recipe-sysroot -I/media/build/poky/build/tmp/work/core2-64-poky-linux-musl/python3-numpy/2.1.3/recipe-sysroot/usr/include/python3.13 -I/usr/include/python3.13 A bug has been filed about this and the related gcc issue: https://bugzilla.yoctoproject.org/show_bug.cgi?id=15672 With pkgconfig on the inherit line, all include directives in meson-log.txt end up looking something like: |-I/home/tgamblin/workspace/yocto/poky/build/tmp/work/core2-64-poky-linux-musl/python3-numpy/2.1.3/recipe-sysroot/usr/include/python3.13 (From OE-Core rev: b8503a2c5000262a400375321de75161357111fb) Signed-off-by: Trevor Gamblin <tgamblin@baylibre.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* lib: oe: license: Add missing importJoshua Watt2024-11-281-0/+1
| | | | | | | | | | The code in this file uses oe.qa, but it was not imported resulting an an exception when a license error was detected (From OE-Core rev: e44cb7c5b7281d614ed51fdec06dad0a7211528a) Signed-off-by: Joshua Watt <JPEWhacker@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-isodate: move to meta-pythonGuðni Már Gilbert2024-11-282-17/+0
| | | | | | | | | python3-rdflib was the last consumer of this recipe in oe-core. (From OE-Core rev: 72cc499429b0869385223ba21fe03849c6145b89) Signed-off-by: Guðni Már Gilbert <gudni.m.g@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-rdflib: drop python3-isodate from RDEPENDSGuðni Már Gilbert2024-11-281-1/+1
| | | | | | | | | | | | On Python 3.11+, the built-in datetime module is used instead. This change was made in v7.1.0 release. See PR 2929: https://github.com/RDFLib/rdflib/blob/main/CHANGELOG.md#2024-10-17-release-710 (From OE-Core rev: 70cb0adf3612fb15b6b2723c0af6ba1467d210b5) Signed-off-by: Guðni Már Gilbert <gudni.m.g@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* classes/go-vendor: Use UNPACKDIR instead of WORKDIRJoshua Watt2024-11-281-1/+1
| | | | | | | | | | modules.txt is provided using file:// in SRC_URI, therefore it will be found in UNPACKDIR instead of WORKDIR (From OE-Core rev: 114fe16f96280f40a9cea20b02b2743be42645dd) Signed-off-by: Joshua Watt <JPEWhacker@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* insane: Split ERROR_QA into CHECKLAYER_REQUIRED_TESTSRichard Purdie2024-11-281-19/+18
| | | | | | | | | | | | | | | We'd like to start requiring some set of checks are enabled for Yocto Project Compatible Status and to pass yocto-check-layer. Start by splitting ERROR_QA into two sets, the ones we think can be required and the ones we know have challenges to implement (e.g. with prebuilt binaries). To change the required list, the YP TSC would need to approve. (From OE-Core rev: ce2e42ace2d15fb6745437cf0a7f07d28398ca12) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: Remove custom exception backtrace formattingJoshua Watt2024-11-285-119/+25
| | | | | | | | | | | | | | | | | | | | | | | Removes the code in bitbake to show custom backtrace formatting for exceptions. In particular, the bitbake exception code prints function arguments, which while helpful is a security problem when passwords and other secrets can be passed as function arguments. As it turns out, the handling of the custom serialized exception stack frames was pretty much made obsolete by d7db75020ed ("event/msg: Pass formatted exceptions"), which changed the events to pass a preformatted stacktrack list of strings, but the passing of the serialized data was never removed. Change all the code to use the python traceback API to format exceptions instead of the custom code; conveniently traceback.format_exception() also returns a list of stack trace strings, so it can be used as a drop in replacement for bb.exception.format_exception() (Bitbake rev: 2cda75a185aaf8f657f072dac34f8cef9d75f63a) Signed-off-by: Joshua Watt <JPEWhacker@gmail.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-04 15:37:10 +0000