summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* xmlcatalog: limit to native recipes onlyRoss Burton2024-01-121-2/+6
| | | | | | | | | | | | | The sysroot postinst is explicitly native-only, so use more overrides to ensure that we don't try to run them outside of native recipes. Also add a comment so this doesn't get forgotten again, and link to the related bug. (From OE-Core rev: 38a5fc5dbb33fd3314f0a98c861a842342add064) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* shadow: link executables statically for -native variantAlexander Kanavin2024-01-122-0/+15
| | | | | | | | | | | | shadow 4.14.x adds a number of libraries it dynamically links with (md, bsd, attr). This causes troubles in setscene tasks where shadow executables are used (such as useradd), as pulling in the needed dynamic libraries needs unpleasant special-casing. (From OE-Core rev: 495ff95eae14a91c94187f78a0b30c7957c9b168) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* shadow: update 4.13 -> 4.14.2Alexander Kanavin2024-01-128-378/+16
| | | | | | | | | | | | | | | | | | | | | | | License-Update: formatting, spdx conversion Drop: 0001-Disable-use-of-syslog-for-sysroot.patch (issue fixed upstream) 0001-Fix-can-not-print-full-login.patch 0001-Overhaul-valid_field.patch CVE-2023-29383.patch (backports) libbsd is a new native dependency, as otherwise glibc >= 2.38 is needed. A similar fix is added to musl in order to define non-standard __BEGIN_DECLS/__END_DECLS. (From OE-Core rev: e85069acf304fe0b68583cf79fe3ec4f775dca68) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* glibc: Set status for CVE-2023-5156 & CVE-2023-0687Simone Weiß2024-01-121-0/+2
| | | | | | | | | | | | Set `CVE_STATUS`for those CVEs, they have already been fixed with the latest pull for stable branch fixes done in rev e444d2bed0ea140a574414fcd5a689867e8ba312. Hence the issues are fixed already. (From OE-Core rev: 6e6fe23c95f1d0a8a0503cb71557cf3272bf9945) Signed-off-by: Simone Weiß <simone.p.weiss@posteo.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* cairo: upgrade to 1.18.0Ross Burton2024-01-126-202/+27
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The changelog is large[1] but: Added: - Type 3 colour and COLRv2 fonts - Tee surfice automatically enabled - Meson build system Removed: - The cairo-sphinx tool - The XML, GL, GLES, Qt5, BeOS, OS/2, DirectFB, DRM, Cogl, and OpenVL backends - Autotools build system These CVE patches have been merged upstream: CVE-2018-19876.patch: https://gitlab.freedesktop.org/cairo/cairo/-/commit/90e85c2493fdfa3551f202ff10282463f1e36645 CVE-2019-6461.patch: https://gitlab.freedesktop.org/cairo/cairo/-/commit/09643ee1abdd5daacebfcb564448f29be9a79bac CVE-2019-6462.patch: https://gitlab.freedesktop.org/cairo/cairo/-/commit/bbeaf08190d3006a80b80a77724801cd477a37b8 CVE-2020-35492.patch: https://gitlab.freedesktop.org/cairo/cairo/-/commit/c986a7310bb06582b7d8a566d5f007ba4e5e75bf Some niche options have been removed in the migration to Meson, so the recipe can be cleaned up. Put libcairo-fdr ("flight data recorder") in the perf-utils package instead of deleting it. There is an executable test for IPC behaviour that needs to be set via a cross file if qemu-user isn't available, thanks to Alex Kanavin for this portion. [1] https://www.cairographics.org/news/cairo-1.18.0/ (From OE-Core rev: 9a4ca6b08d6031ebb67adcdd650aa59acd4fb5fb) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meson: use pkg-config in the cross filesRoss Burton2024-01-121-2/+2
| | | | | | | | | | | | >From Meson 1.3.0, the "pkgconfig" entry is deprecated and "pkg-config" should be used instead[1]. [1] https://mesonbuild.com/Release-notes-for-1-3-0.html#machine-files-pkgconfig-field-deprecated-and-replaced-by-pkgconfig (From OE-Core rev: d64b307891422e290bbe821d4303b3af526bbe17) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* opkg-utils: Backport fix to drop --numeric-owner parameterKhem Raj2024-01-122-0/+35
| | | | | | | | | | It fixes the issue with different GIDs during ipk creation and image creation time (From OE-Core rev: a7f7d6f0c504f3f88801e0ba89a43e9b671fe4d3) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* selftest/SStatePrintdiff: ensure all base signatures are present in sstate ↵Alexander Kanavin2024-01-121-15/+19
| | | | | | | | | | | | | | | | | | | | in test_image_minimal_vs_base_do_configure The test relies on all tasks in the dependency tree of the tasks being changed having valid signatures in sstate, so that the recursive discovery of the base invalid tasks stops there, and doesn't go further. This may not always occur, particularly when hash equivalency combined with different build host architectures prevents them from getting created in regular builds: https://autobuilder.yoctoproject.org/typhoon/#/builders/127/builds/2725/steps/15/logs/stdio The other two tests (that change specific recipes) already ensure this, but this test (which changes a basic task definition) does not. (From OE-Core rev: e37445320ca1a8913d6ed768681ff32de24eef94) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* coreutils: Ignore line-bytes.sh and no-allocate tests on muslKhem Raj2024-01-121-0/+6
| | | | | | | | | | | bash fails in xmalloc when running these tests. More thorough investigation may reveal real cause, however, it seems to fail on other musl distros as well. (From OE-Core rev: cd31bb507bfb794379950dd0aa38b810ba194d2f) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* tcl: Fix prepending to run-ptest scriptKhem Raj2024-01-121-1/+1
| | | | | | | | | | This ensures that string is prepended properly and eclosed in '' Fixes the ptest runs on musl (From OE-Core rev: 7bb45591f9caa7ff6b065220927a26e8261e2866) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* util-linux: enable gtk-docRoss Burton2024-01-122-2/+4
| | | | | | | | | | | | | Now that we've solved the util-linux - gtk-doc - xmlto - util-linux dependency loop, we can enable gtk-doc in util-linux. We explicitly disable it in util-linux-libuuuid as this doesn't have API documentation. (From OE-Core rev: 6999719143df04816c74fbc46d4a97b377bc0b36) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* kmod: fix configure with autopoint calling gtkdocizeRoss Burton2024-01-122-2/+34
| | | | | | | | | | GTKDOC_DOCDIR is obsolete now, so fix the build by passing the documentation directory in the GTK_DOC_CHECK call. (From OE-Core rev: c2f0e8ccd57c18fee36fc0adbbaf63e2302b8268) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gtk-doc: don't manually call gtkdocizeRoss Burton2024-01-121-10/+0
| | | | | | | | | | | | | | | | | | | The autoreconf call will now call gtkdocize if needed, so we don't need to run it manually here. This obsoletes GTKDOC_DOCDIR. If this is needed then the replacement is to ensure that the configure.ac has a call to GTK_DOC_CHECK which passes --docdir. For example, this is the change required for kmod: -GTK_DOC_CHECK([1.14],[--flavour no-tmpl-flat]) +GTK_DOC_CHECK([1.14],[--flavour no-tmpl-flat --docdir libkmod/docs]) (From OE-Core rev: 57b0201bfccb4552893d72dc4d76eaa855618563) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gtk-doc: don't use docdir set in environment in gtkdocizeRoss Burton2024-01-122-0/+25
| | | | | | | | | | | The gtkdocize script was accidentally respecting $docdir from the environment as the default documentation directory. This is a problem as bitbake.conf exports $docdir, resulting in configure failures. (From OE-Core rev: d7f8f56e2a91abbadf53fd4c48d6f0e55ac749d1) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gtk-doc: remove obsolete logicRoss Burton2024-01-121-9/+2
| | | | | | | | | | | | | This manual disabling of gtk-doc for autotools and meson in native and nativesdk builds is replicating logic above for target builds. Instead, use one assignment for all builds, as we explicitly disable gtk-doc in native builds and it can be useful in nativesdk. (From OE-Core rev: e13b019c61d86f1add32f23795f6e71110c6a70c) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gtk-doc: fix DEPENDSRoss Burton2024-01-121-1/+1
| | | | | | | | | | The use of xmlto and six was removed many years ago, instead depend directly on docbook-xml and docbook-xsl. (From OE-Core rev: 3e2114df7b70d8a16873d7e1fb1e61eedf7d3e2a) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* autotools: don't exclude gtkdocizeRoss Burton2024-01-121-1/+1
| | | | | | | | | | gtkdocize can now be ran successfully from autoreconf, so there's no need to exclude it and run it manually. (From OE-Core rev: 891ec38d4c5cc5ac7bc34938276261ebd6f6d54e) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* autotools: append to EXTRA_AUTORECONFRoss Burton2024-01-121-1/+1
| | | | | | | | | | Inherit order may mean that this class is inherited after assignments, so extend instead of assign EXTRA_AUTORECONF. (From OE-Core rev: 83958b4bdea90a0bb9331d33c2f266900a108fee) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* glib-2.0: no need to depend on target gtk-docRoss Burton2024-01-123-2/+22
| | | | | | | | | | | | The meson.build looks for a target gtk-doc, but it should be looking for the native package. Fixing this means we can drop the need for a target gtk-doc package. (From OE-Core rev: f91694fa8f5c2c3e6f4946300f040677cb0828fd) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* migration-guide: add release notes for 4.3.2Lee Chee Yang2024-01-122-0/+248
| | | | | | | | (From yocto-docs rev: 29cee590d59294306600a119048a234f10375603) Signed-off-by: Lee Chee Yang <chee.yang.lee@intel.com> Reviewed-by: Michael Opdenacker <michael.opdenacker@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* documentation: Add UBOOT_BINARY, extend UBOOT_CONFIGJörg Sommer2024-01-122-17/+24
| | | | | | | | | | | | UBOOT_CONFIG accepts a third parameter for the UBOOT_BINARY that isn't documented. To show its usage another example from the meta-freescale layer was picked. (From yocto-docs rev: 8b227582efbe9957026cdce4aef5621661af1fa5) Signed-off-by: Jörg Sommer <joerg.sommer@navimatix.de> Reviewed-by: Michael Opdenacker <michael.opdenacker@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* manuals: document VSCode extensionEnguerrand de Ribaucourt2024-01-126-3/+56
| | | | | | | | | | | | | | | | The VSCode extension is now officially maintained and published by the Yocto Project so it should be referenced in the manuals to help users discover it. I located the most relevant places to reference the extension by looking at how the old Eclipse plugin was documented in the 2.6 manuals as well as the current Toaster references. (From yocto-docs rev: 645153504690aa8a69b028e95a5e9d2da9644cf1) Signed-off-by: Enguerrand de Ribaucourt <enguerrand.de-ribaucourt@savoirfairelinux.com> Reviewed-by: Michael Opdenacker <michael.opdenacker@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual: document cmake-qemu classAdrian Freihofer2024-01-121-0/+29
| | | | | | | | (From yocto-docs rev: b2e396bd970ea8f27ba575b49c1489e2181442b8) Signed-off-by: Adrian Freihofer <adrian.freihofer@siemens.com> Reviewed-by: Michael Opdenacker <michael.opdenacker@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* dev-manual: update license manifest pathIlya A. Kriveshko2024-01-121-1/+1
| | | | | | | | | | | After changes in openembedded-core@1a4ab9f, image licenses moved one directory down into ${SSTATE_PKGARCH} subdir. (From yocto-docs rev: ea9675f079cef919a9d13ab12d095144b2eae6ab) Signed-off-by: Ilya A. Kriveshko <iillyyaa@gmail.com> Reviewed-by: Michael Opdenacker <michael.opdenacker@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual: classes: remove insserv bbclassMaxin B. John2024-01-121-10/+0
| | | | | | | | | | | | | | | | insserv.bbclass was removed from oe-core: commit e6bb5dbb62257a7de730ea9085dfd89520f3e47d Author: Richard Purdie <richard.purdie@linuxfoundation.org> Date: Sun May 10 12:30:49 2015 +0100 insserv: Remove (From yocto-docs rev: 41a15a80a325cb63a41be81e632ec2799bfb2957) Signed-off-by: Maxin John <maxin.john@gmail.com> Reviewed-by: Michael Opdenacker <michael.opdenacker@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* dev-manual: start.rst: update use of Download pageSimone Weiß2024-01-121-8/+10
| | | | | | | | | | | The yocto website has changed its structure. Update the section for Accessing the Downloads page to match the new structure. (From yocto-docs rev: d8fdec653f96c4ddcb705ff0ef17ed641afcfe2d) Signed-off-by: Simone Weiß <simone.p.weiss@posteo.com> Reviewed-by: Michael Opdenacker <michael.opdenacker@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual: update tested and supported distrosMichael Opdenacker2024-01-121-10/+7
| | | | | | | | | | | | | | | | According to currently active workers https://autobuilder.yoctoproject.org/typhoon/#/workers Also correct the text saying that SANITY_TESTED_DISTROS lists currently tested distros. Also replace AlmaLinux 8.8 and 9.2 by just AlmaLinux 8 and 9, as we update our workers anyway. (From yocto-docs rev: bceadfad0954e8473b0e87bba8d6b1e67fd88eef) Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* contributor-guide: use "apt" instead of "aptitude"Michael Opdenacker2024-01-121-1/+1
| | | | | | | | | As used in the rest of the manual. (From yocto-docs rev: 5a5dfc446bb62568da50056660d18c5c309d1051) Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* rootfs.py: check depmodwrapper execution resultYang Xu2024-01-101-1/+2
| | | | | | | | | | | | | The execution result of depmodwrapper is not checked which makes depmod generation failed sliently and hard to detect. So check exection result and stop building if depmodwrapper failed. (From OE-Core rev: 2f88e7d331390c6aaecc4522253e24791aec299e) Signed-off-by: Yang Xu <yang.xu@mediatek.com> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* kmscube: Add package versionFabio Estevam2024-01-101-0/+3
| | | | | | | | | | | | kmscube meson.build passes version : '0.0.1', so add a package version entry to match. Suggested-by: Martin Jansa <martin.jansa@gmail.com> (From OE-Core rev: be1b8f2c7f6763f64f7fdfd6e17586403bd63a7e) Signed-off-by: Fabio Estevam <festevam@denx.de> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* kmscube: Change header file to <GLES3/gl3.h>Fabio Estevam2024-01-102-1/+36
| | | | | | | | | | | | | | Since kmscube commit 96d63eb59e34 ("kmscube: Add gears mode"), kmscube fails to build on platforms without <GL/gl.h>. Fix it by changing the header file to <GLES3/gl3.h>. Reported-by: Martin Jansa <martin.jansa@gmail.com> (From OE-Core rev: f44f79298fc909aea9fcc8ebc848a96e9ff5a647) Signed-off-by: Fabio Estevam <festevam@denx.de> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-firmware: Fix the linux-firmware-bcm4373 FILES variableRodrigo M. Duarte2024-01-101-0/+1
| | | | | | | | | | | | | This commit includes the 'cyfmac4373-sdio.clm_blob' file in the list of files for the linux-firmware-bcm4373 package. Without this file, the linux-firmware package adds all firmware packages to the image. (From OE-Core rev: 7886d3b77200e4488393fa11c8198658fcf386cd) Signed-off-by: Rodrigo M. Duarte <rodrigo.duarte@ossystems.com.br> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* rng-tools: remove obsolete build time dependency on sysfsutilsdavid d zuhn2024-01-101-1/+1
| | | | | | | | | | | | This package used to use libsysfs, but has been modified to read the /sys file system directly. This build dependency is no longer needed. (From OE-Core rev: 9ee39dd1d505f787e7bf4e3aa2b527f17c3a78cd) Signed-off-by: david d zuhn <david.zuhn@sonos.com> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* syslinux: Allow mtools to be optionalJoshua Watt2024-01-101-5/+12
| | | | | | | | | | | | | | | | Adds a PACKAGECONFIG to syslinux to determine if the mtools version of the utilities is installed or not. The difference between the two versions is that the mtools version can be used by any user with write permission, while the non-mtools can only be used by root. The syslinux-nomtools package is removed, as it was empty and doesn't appear to be used anyway (From OE-Core rev: 06da552733091bc8d332bb932c86cbc8362d44b9) Signed-off-by: Joshua Watt <JPEWhacker@gmail.com> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* systemd: add udev-bash-completion packageCorentin Guillevic2024-01-101-1/+3
| | | | | | | | | | | | | | | | Move the 'udevadm' autocompletion script into a dedicated package. Indeed, bash (and therefore, the bash-completion package) is not always installed. But the 'udevadm' autocompletion script remains in ${datadir}/bash-completion. Creating a dedicated package allows better split, and avoids installing it if the bash-completion package is missing. (From OE-Core rev: 7155ceadbd90b7c90fa0d734f8bc8b089ddd12f3) Signed-off-by: Corentin Guillevic <corentin.guillevic@smile.fr> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* u-boot: Upgrade to 2024.01Fabio Estevam2024-01-103-1/+1
| | | | | | | | | | Upgrade to U-Boot 2024.01. (From OE-Core rev: 727ff6fed97118113dc191605bf5551ca0da134d) Signed-off-by: Fabio Estevam <festevam@denx.de> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* selftest/sstatetests: include fetcher diagnostics into CDN test failure messageAlexander Kanavin2024-01-101-2/+6
| | | | | | | | | | | | | This will help finding out what kind of error the server actually returned, as sporadic CDN failures continue to occur. [YOCTO #15335] (From OE-Core rev: 7f09c4c5a0fe4ff213f205927f618a77b72aeef3) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* icon-naming-utils: take tarball from debianAlexander Kanavin2024-01-101-2/+2
| | | | | | | | | | | Upstream website has disappeared; the tarball can still be downloaded but this is probably not for long. (From OE-Core rev: af59c518467d1174d1d63594fdd3279a2fdbd8f8) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libpcre2: fix upstream version checkAlexander Kanavin2024-01-101-1/+1
| | | | | | | | (From OE-Core rev: 0eb4e166d293e0e595e4d0a70f378cb8014425ee) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* taglib: fix upstream version checkAlexander Kanavin2024-01-101-0/+1
| | | | | | | | (From OE-Core rev: 2ed130333fb4f378e4d2a91b3d37d12716dd41f7) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gptfdisk: Make the version consistentMingli Yu2024-01-101-19/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | The previous change [262aa17e0e popt: update 1.18 -> 1.19] backports a patch [1] for gptfdisk and make the version bump from 1.0.9 to 1.0.9.1 and make the package version inconsistent as below: root@qemux86-64:~# rpm -qa | grep gptfdisk gptfdisk-1.0.9-r0.core2_64 root@qemux86-64:~# rpm -ql gptfdisk /usr /usr/sbin /usr/sbin/cgdisk /usr/sbin/fixparts /usr/sbin/gdisk /usr/sbin/sgdisk root@qemux86-64:~# gdisk --help GPT fdisk (gdisk) version 1.0.9.1 [snip] So update the bumped version part to make the package version consistent. [1] https://sourceforge.net/p/gptfdisk/code/ci/5d5e76d369a412bfb3d2cebb5fc0a7509cef878d (From OE-Core rev: 8b43f06736321c3e9e6a9f418139058be4f2b355) Signed-off-by: Mingli Yu <mingli.yu@windriver.com> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-cython: update 0.29.36 -> 3.0.7Alexander Kanavin2024-01-102-2/+5
| | | | | | | | | | | | | | | | pep517 build backends require cython 3.x when python is at 3.12, so we can't hold this update any longer. There are only a few things in meta-oe and meta that break anymore, and fixes for them are provided at the same time as this patch. License-update: http -> https (From OE-Core rev: 21507a3be23a604259a6a903a7083db54d29487f) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-pyyaml: make compatible with cython 3.xAlexander Kanavin2024-01-102-0/+55
| | | | | | | | | | | | | This has been rejected by upstream in favour of requiring obsolete cython until there's 'proper' 3.x support. Months later, there's still no progress so let's just take the rejected fix, as it does work (as reported by others as well), and allows moving forward with cython. (From OE-Core rev: cf4e45176a37b6f53a6316ec6b1556d6aea39b57) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* selftest/sstatetest: re-enable gcc printdiff testAlexander Kanavin2024-01-101-1/+1
| | | | | | | (From OE-Core rev: 976832eb0c3fc0170a84ff7ab92352ca6f18c383) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* selftest/sstatetests: fix up printdiff test to match rework of printdiff logicAlexander Kanavin2024-01-102-9/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | Other than the formatting changes, there are two functional ones: - use perlcross instead of quilt, as quilt is special in the sense of being excluded from task hash calculcations. perlcross is a full participant. - run the full test (local + sstate) for gcc do_preconfiure change as the necessary fix has been implemented (sstatesig/find_siginfo: special-case gcc-source when looking in sstate caches) Note that when several tasks are found to have changed (as is the case when base do_configure is adjusted), find_siginfo() runs glob.glob("*/*/*taskname*") against autobuilder sstate cache for each of those tasks (six or seven times). This is an expensive operation taking several minutes. I left it in for now, but if it's proven too slow the test would have to be reduced to checking a specific base recipe (e.g. zstd-native) rather than a distant image target. [YOCTO #15289] (From OE-Core rev: 0ef7cf324718412c5b6c376acfbc4079ecd7d465) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: bitbake/runqueue: rework 'bitbake -S printdiff' logicAlexander Kanavin2024-01-101-15/+26
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Previously printdiff code would iterate over tasks that were reported as invalid or absent, trying to follow dependency chains that would reach the most basic invalid items in the tree. While this works in tightly controlled local builds, it can lead to bizarre reports against industrial-sized sstate caches, as the code would not consider whether the overall target can be fulfilled from valid sstate objects, and instead report missing sstate signature files that perhaps were never even created due to hash equivalency providing shortcuts in builds. This commit reworks the logic in two ways: - start the iteration over final targets rather than missing objects and try to recursively arrive at the root of the invalid object dependency. A previous version of this patch relied relies on finding the most 'recent' signature in stamps or sstate in a different function later, and recursively comparing that to the current signature, which is unreliable on real world caches. - if a given object can be fulfilled from sstate, recurse only into its setscene dependencies; bitbake wouldn't care if dependencies for the actual task are absent, and neither should printdiff I wrote a recursive function for following dependencies, as doing recursive algorithms non-recursively can result in write-only code, as was the case here. [YOCTO #15289] (Bitbake rev: aadeca63da5d96160ce4d6d71da556e2e033f9b7) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: ui/knotty: properly handle exceptions when calling runCommand()Mark Asselstine2024-01-101-10/+52
| | | | | | | | | | | | | | | | | | | | | | | | | | In runCommand() the send() and recv() can fail and raise BrokenPipeError and EOFError exceptions when the bitbake-server is unexpectedly terminated. In these cases a python traceback is currently dumped. Similarly updateFromServer() which calls runCommand() can also raise these and other exceptions, and currently lacks proper exception handling resulting in python traceback. We wrap calls to runCommand() and updateFromServer() in a try/except block as well as improve the exception handling for updateToServer(). This along with the earlier commit which added text to the BrokenPipeError and EOFError exceptions in runCommand() to indicate a bitbake-server termination may have occurred, should improve the user's ability to understand and handle these errors. An easy way to trigger each of the runCommand() exceptions is to 'kill -9' bitbake-server before (causes EOFError) or after (causes BrokenPipeError) the "Loading Cache" stage. (Bitbake rev: 804d366ee3ddc0f37f0a6c712c8d42db45b119bc) Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: server/process: catch and expand multiprocessing connection exceptionsMark Asselstine2024-01-101-2/+8
| | | | | | | | | | | | | | | | | | | | | | | Doing builds on systems with limited resources, or with high demand package builds such as chromium it isn't uncommon for the OOM Killer to be triggered and for bitbake-server to be selected as the process to be killed. When the bitbake-server does terminate unexpectedly due to the OOM Killer or otherwise, this currently results in a generic python traceback with little indication as to what has failed. Here we trap and raise the exceptions while extending the exception text in runCommand() to make it clear that this is most likely caused by the bitbake-server unexpectedly terminating. Callers of runCommand() should be updated to properly handle the BrokenPipeError and EOFError exceptions to avoid printing a python traceback, but even if they don't, the added text in the exceptions should provide some hints as to what might have caused the failure. (Bitbake rev: 5ff62b802f79acc86bbd6a99484f08501ff5dc2d) Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: ast: Fix EXPORT_FUNCTIONS bugRichard Purdie2024-01-102-4/+103
| | | | | | | | | | | | | | | | If you have two classes, both of which set EXPORT_FUNCTIONS for the same funciton and a standard funciton definition for the function that is exported, the export function can sometimes overwrite the standard one. The issue is that the internal flag the code uses isn't ovweritten if the variable is giving a new value. Fix the issue by using a comment in the code that is injected so that we know if it is ours or not. Also add some testing for EXPORT_FUNCTIONS, not perfect but a start. (Bitbake rev: 66306d5151acb0a26a171c338d8f60eb9eb16c6b) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: fetch/wget/checkstatus(): include the URL in debugging output about ↵Alexander Kanavin2024-01-101-1/+1
| | | | | | | | | | | | | | | | | | | | | | status check failure Previously the output wasn't useful for finding out what was the actual URL that failed, particularly in heavily multi-threaded invocations: DEBUG: checkstatus() urlopen failed: HTTP Error 404: Not Found With this change, the problem is described specifically: DEBUG: checkstatus() urlopen failed for http://cdn.jsdelivr.net/yocto/sstate/all/universal/4f/91/sstate:gettext-minimal-native:x86_64-linux:0.22.4:r0:x86_64:11:4f91b650ebd7be601cbd0e3a37a8cc6385a3f4ee616f931969b50709ed8bf044_create_spdx.tar.zst: HTTP Error 404: Not Found This will help with CDN cache tests in particular. When some object isn't available, we need to know why: 4xx error, 5xx error, timeout error or any other issue. (Bitbake rev: ecd9b92815563509f55264ed6e7498aee797cedd) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2024-07-06 12:57:31 +0000