summaryrefslogtreecommitdiffstats
path: root/meta
Commit message (Collapse)AuthorAgeFilesLines
...
* python3-cryptography-crates.inc: regenerate with updated bbclassMartin Jansa2023-04-061-66/+66
| | | | | | | | | | | | | | | * it's needed for compatibility with updated fetcher from: https://patchwork.yoctoproject.org/project/bitbake/patch/20230405122125.3358972-1-enrico.scholz@sigma-chemnitz.de/ * easiest way to regenerate these is: echo > meta/recipes-devtools/python/python3-cryptography-crates.inc bitbake -c update_crates python3-cryptography git commit (From OE-Core rev: bf6a3cd70d13f05f0e2af2b54635214690a68a78) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* cargo-update-recipe-crates.bbclass: Do not add name= to crate:// URIsPeter Kjellerstedt2023-04-061-1/+1
| | | | | | | | | | | | | With the recent change to the crate fetcher, which automatically sets the name to for each crate to be versioned, there is no longer a need to explicitly set the name= parameter for each URI. This also results in generated files that are compatible with the crate fetcher in Kirkstone and Langdale. (From OE-Core rev: eb272afcd9a12ce2b2f43436b3f84f52cb6cdfb7) Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* build-appliance-image: Update to master head revisionRichard Purdie2023-04-051-1/+1
| | | | | | (From OE-Core rev: 5a96847e7ef2ff72958d739a91c90e2085c04bc6) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* build-appliance-image: Update to master head revisionRichard Purdie2023-04-051-1/+1
| | | | | | (From OE-Core rev: 76f16451343b9e6a0f87eaf15a5c6f5a80b73633) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* busybox: move hwclock init earlier in startupChris Elledge2023-04-051-0/+1
| | | | | | | | | | | | | | | | hwclock.sh had default update-rc parameters which made it run after other tasks that work with the clock such as connman. This causes a time obtained by NTP to be clobbered by a potentially incorrect time in the RTC. Provide non-default INITSCRIPT_PARAMS to have hwclock.sh run during the rc startup before runlevel initscripts start. (From OE-Core rev: 3012bac35ada9a9f66d9e6e2fecaee09527b9d44) Signed-off-by: Chris Elledge <celledge@siteworx.io> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqa/selftest/bblogging: uncomment python stdout checksMark Asselstine2023-04-051-12/+6
| | | | | | | | | | | | Since bitbake commit 81a58647b2f4fc0a2589b2978fc9d81b2bfe6aec [bitbake: build: Make python output print to stdout when running with -v (verbose)] we no longer need to comment out the python stdout checks. (From OE-Core rev: 67886a8473c511c8ab3db2e4587cc5a070979d11) Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qemu: rename deprecated --enable-trace-backend configure optionThomas De Schampheleire2023-04-051-1/+1
| | | | | | | | | | | | | | qemu 6.2 deprecated the configure option '--enable-trace-backend' in favor of '--enable-trace-backends' [1] Rename accordingly. [1] https://wiki.qemu.org/ChangeLog/6.2#Build_Information (From OE-Core rev: 9e41fac1c2ee15aaff9926dac3c0233430adff12) Signed-off-by: Thomas De Schampheleire <thomas.de_schampheleire@nokia.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qemu: retain default trace backend if 'ust' is not enabledThomas De Schampheleire2023-04-051-1/+1
| | | | | | | | | | | | | | | | | | | | | | The qemu build system enables the 'log' trace backend by default, if no explicit choice was made with '--enable-trace-backend=CHOICE'. However, the qemu recipe uses the following PACKAGECONFIG line: PACKAGECONFIG[ust] = "--enable-trace-backend=ust,--enable-trace-backend=nop,lttng-ust," which means that the 'nop' trace backend will be explicitly selected if the 'ust' feature is not enabled. The 'nop' backend removes almost all trace points at compile time, and thus basically means 'disable tracing'. To retain the default trace backend if 'ust' is not enabled, the above PACKAGECONFIG line should either explicitly fall back to the 'log' backend, or not provide any value for the 'disabled' case. This commit chooses the latter to not make any assumption about the upstream default. (From OE-Core rev: c31396a30dcf17ab23ff4dd5943eef5fba20cba6) Signed-off-by: Thomas De Schampheleire <thomas.de_schampheleire@nokia.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qemu: make tracetool-generated output reproducibleThomas De Schampheleire2023-04-052-0/+88
| | | | | | | | | | | '#line' directives written by qemu's tracetool makes the 'debug' package not reproducible due to absolute paths. Apply a patch to use a relative path instead. (From OE-Core rev: 85e30c507b63fa9126887dc6435d1ee6e23bd887) Signed-off-by: Thomas De Schampheleire <thomas.de_schampheleire@nokia.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* cve-extra-exclusions: ignore inapplicable linux-yocto CVEsGeoffrey GIRY2023-04-055-3/+74
| | | | | | | | | | | | | | | | | | Multiple CVEs are patched in kernel but appear as active because the NVD database is not up to date. In common file cve-extra-exclusion.inc, CVEs are ignored if and only if all versions of kernel used are patched. In cve-exclusion_6.1.inc, only ignore CVEs that are patched in v6.1, and not patched in v5.15. Recipes of version 6.1 should include this file. Reviewed-by: Yoann Congal <yoann.congal@smile.fr> (From OE-Core rev: 5feb065f1b1aaf218f71cc9d31a9251b139b9442) Signed-off-by: Geoffrey GIRY <geoffrey.giry@smile.fr> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* xdg-utils: Fix CVE numberRichard Purdie2023-04-052-2/+2
| | | | | | | | | In the previous commit I somehow mixed up and used an incorrect CVE number. Use the correct one. (From OE-Core rev: b3e2729f686ff6e16e11590bcd701c057ae5f1e2) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sanity.bbclass: Update minimum gcc version to 8.0Mark Hatle2023-04-041-3/+3
| | | | | | | | | | | | | | With a gcc older then 8.0, mesa-native will fail to build with the error: sorry, unimplemented: non-trivial designated initializers not supported According to https://docs.mesa3d.org/install.html?highlight=gcc+version#compile the required minimum compiler version is now GCC 8.0. (From OE-Core rev: aa466053bf8a4b7998a462f0b49372d3a68a28e3) Signed-off-by: Mark Hatle <mark.hatle@amd.com> Signed-off-by: Mark Hatle <mark.hatle@kernel.crashing.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* cve-extra-exclusions.inc: Exclude some issues not present in linux-yoctoRichard Purdie2023-04-041-0/+40
| | | | | | | | | | | | | Exclude some CVEs where the patches were backported to the stable series kernels we have. https://www.linuxkernelcves.com/cves/CVE-XXXX-XXXX is useful to help with this. Reviewed-by: Yoann Congal <yoann.congal@smile.fr> (From OE-Core rev: 33448393493d507c4d81c40e43537065a7b61d4c) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* xdg-utils: Add a patch for CVE-2020-27748Richard Purdie2023-04-042-0/+146
| | | | | | | | | Take a patch submitted upstream for the issue while upstream decide what to do. We don't use thunderbird integration so this isn't an issue for us. (From OE-Core rev: b85b7714a44caa70beb2f115483ee52745aa1b97) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* vte: depend on glib-2.0-nativePetr Kubizňák2023-04-041-1/+1
| | | | | | | | | | | When gobject-introspection feature is disabled, glib-2.0-native package dependency is not pulled in but vte has a hard dependency on it (do_configure fails due to missing glib-mkenums). (From OE-Core rev: 686e0cb93f9f6ef663243e62c7a8cc43ca1dcd3a) Signed-off-by: Petr Kubizňák <kubiznak@2n.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gstreamer1.0-plugins: package the internal libraries explicitlyRoss Burton2023-04-041-0/+2
| | | | | | | | | | An upcoming change will simplify the setuptools3-base FILES assignments, which means this recipe needs to package a library explicitly. (From OE-Core rev: bab2e8c76453cf9982af936f20c6b22cc2237ba7) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bind: don't package non-existant .la files into -staticdevRoss Burton2023-04-041-1/+0
| | | | | | | | | | If these files exist they should be packaged into PN-dev, and are with the default FILES:${PN}-dev. (From OE-Core rev: 738434bf567d25de692cd145156263eea1a5de13) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* classes-recipe/setuptools3-base: clean up FILES assignmentsRoss Burton2023-04-041-10/+3
| | | | | | | | | | | Simply inheriting setuptools3-base should put everything in $libdir in PN, and there's no need to replicate the pkgconfig packaging rules as those are the defaults. (From OE-Core rev: 56a32e31d4fdfb908f0edf513d21bc0f2b8c721e) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libnotify: depend on glib-2.0-nativePetr Kubizňák2023-04-041-1/+1
| | | | | | | | | | | When gobject-introspection feature is disabled, glib-2.0-native package dependency is not pulled in but libnotify has a hard dependency on it (do_configure fails due to missing glib-mkenums). (From OE-Core rev: 63cc22caf4dfcde1d7a3a8410559bb227ed95c33) Signed-off-by: Petr Kubizňák <kubiznak@2n.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* webkitgtk: add missing dependenciesPetr Kubizňák2023-04-041-0/+2
| | | | | | | | | | | When gobject-introspection feature is disabled, gettext-native and glib-2.0-native dependencies are not pulled in, which causes failures in do_compile due to missing xgettext and gdbus-codegen. (From OE-Core rev: c9e4c3d437ba7cadb87bc30b85f602b8551a0e17) Signed-off-by: Petr Kubizňák <kubiznak@2n.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gconf: add missing dependenciesPetr Kubizňák2023-04-041-1/+1
| | | | | | | | | | | | When gobject-introspection feature is disabled, glib-2.0-native and gobject-introspection package dependencies are not pulled in but gconf has a hard dependency on them (do_configure fails due to missing introspection.m4 file and glib-gettextize). (From OE-Core rev: d87bc67fde3c8bc6068cb67708953ce88ac31e3f) Signed-off-by: Petr Kubizňák <kubiznak@2n.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-pygobject: depend on gobject-introspectionPetr Kubizňák2023-04-041-1/+1
| | | | | | | | | | When g-i feature is disabled, the gobject-introspection package dependency is not pulled in but pygobject has a hard dependency on it. (From OE-Core rev: 7fae697c6889e17dd47415808a7173670b507047) Signed-off-by: Petr Kubizňák <kubiznak@2n.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* graphene: add gobject-types PACKAGECONFIGPetr Kubizňák2023-04-041-1/+2
| | | | | | | | | | | | | | Add an option to enable/disable build of graphene-gobject. When enabled, add glib dependency (not pulled in implicitly if the gobject-introspection feature is disabled). Default is to enable gobject-types so that graphene-gobject is built (dependency of gtk4). (From OE-Core rev: b82781498cda67f4797de5b8b7c2b90a275a72e1) Signed-off-by: Petr Kubizňák <kubiznak@2n.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* report-error: catch Nothing PROVIDES errorMingli Yu2023-04-041-1/+26
| | | | | | | | | | Make the report-error catch Nothing PROVIDES error and then we can check it directly via error report web. (From OE-Core rev: a57d8f82b83554c821a83eacc02f9c73b263ff02) Signed-off-by: Mingli Yu <mingli.yu@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* rust: update 1.67.1 -> 1.68.1Alexander Kanavin2023-04-0410-79/+65
| | | | | | | | | | | | | Rebase patches; one of the vendored crossbeam versions has been removed upstream, and so crossbeam_atomic.patch is adjusted accordingly. Replace getrandom-open64.patch with a backport. (From OE-Core rev: f5accb4fae49342cbec21718ae7a427615bfcedd) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* rust: install llvm item only onceAlexander Kanavin2023-04-041-1/+1
| | | | | | | | | | Otherwise it triggers a rebuild of llvm-dependent rust pieces every time rust_runx is called, lengthening the builds without need. (From OE-Core rev: aca6b29b508175da9f213b1c6dba5d02a15b8287) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* rust: do not run separate build/install stepsAlexander Kanavin2023-04-041-11/+4
| | | | | | | | | | | | | | Upstream does not actually use or test it this way; if the goal is to install items, then install target should be executed directly. In particular, in latest rust release building stage 2 items has regressed altogether (incorrect dependencies between rust-analyze tool and the libs it needs) and no one noticed. (From OE-Core rev: 7d805f9a9f6b5048308a37a2757d08cca40b1ff3) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* runqemu: respect IMAGE_LINK_NAMEMartin Jansa2023-04-041-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | * when searching for qemuboot.conf * don't assume that IMAGE_LINK_NAME is always <rootfs>-<machine> (with <rootfs>-<machine>.qemuboot.conf) * runqemu: use IMAGE_LINK_NAME set by testimage.bbclass or query with bitbake -e * testimage.bbclass was setting DEPLOY_DIR which I don't see used anywhere else, so I assume it was supposed to be DEPLOY_DIR_IMAGE as mentioned in corresponding runqemu code, do the same with IMAGE_LINK_NAME variable * add virtual/kernel as bitbake -e target in run_bitbake_env to make sure IMAGE_LINK_NAME is defined (kernel-artifact-names.bbclass inherits image-artifact-names.bbclass as well) * improve .qemuboot.conf search 1st search for file matching the rootfs and only when not found try again with .rootfs suffix removed [YOCTO #12937] (From OE-Core rev: 716eb55bb963db7b02d985849cb025898aabc855) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3: Fix failing sysconfig.py test on x86(64 bit) using lib64 as baselib ↵Wentao Zhang2023-04-032-0/+40
| | | | | | | | | | | | | | | | | | | | | | | by updating test_sysconfig for posix_user purelib Steps to trigger the failed test: Edit local.conf to add something as follows: BASELIB = "lib64" IMAGE_INSTALL:append = " python3-tests". bitbake core-image-sato runqemu qemux86-64 nographic slirp Reproducer: $python3 -m test test_sysconfig sysconfig.py use platlibdir for purelib. Update test_sysconfig.test_user_similar() for the posix_user scheme: "purelib" doesn't use sys.platlibdir. (From OE-Core rev: 755321362e994a6a37a0f554b1aea56823de924e) Signed-off-by: Wentao Zhang <wentao.zhang@windriver.com> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* shadow: Fix can not print full login timeout messageSoumya2023-04-032-0/+42
| | | | | | | | | | | | When we do not enter password during login, it is expected to display message "Login timed out after 60 seconds". But it prints only first few bytes(like "Login t") when write is immediately followed by exit. Fix - Calling exit from new handler provides enough time to display full message. Upstream-Status: Accepted [https://github.com/shadow-maint/shadow/commit/670cae834827a8f794e6f7464fa57790d911b63c] (From OE-Core rev: 644cfe9dcf351bfa6c67f4b4d1e7dec416a59021) Signed-off-by: Soumya <soumya.sambu@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* avahi: add missing dependenciesPetr Kubizňák2023-04-031-1/+1
| | | | | | | | | | | | | When gobject-introspection feature is disabled, glib-2.0-native and gobject-introspection package dependencies are not pulled in but avahi has a hard dependency on them (do_configure fails due to missing introspection.m4 file, do_compile fails due to missing glib-mkenums). (From OE-Core rev: fea90325b180ba8d2b19704dc8911a9175527c61) Signed-off-by: Petr Kubizňák <kubiznak@2n.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqa/runtime: clean up deprecated backslash expansionRoss Burton2023-04-033-5/+8
| | | | | | | (From OE-Core rev: 77085a05240c3f8226b9f2199c977f2555807789) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* at-spi2-core: depend on glib-2.0-nativePetr Kubizňák2023-04-031-1/+1
| | | | | | | | | | | When gobject-introspection feature is disabled, glib-2.0-native package dependency is not pulled in but at-spi2-core has a hard dependency on it (do_configure fails due to missing glib-genmarshal). (From OE-Core rev: 954411393a50b8d09cc42f1098e54193d6b19e1d) Signed-off-by: Petr Kubizňák <kubiznak@2n.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libgudev: depend on glib-2.0-nativePetr Kubizňák2023-04-031-1/+1
| | | | | | | | | | | When gobject-introspection feature is disabled, glib-2.0-native package dependency is not pulled in but libgudev has a hard dependency on it (do_configure fails due to missing glib-mkenums). (From OE-Core rev: 8fd140011f89ededdfd7feb1c0e3a2d67e06808a) Signed-off-by: Petr Kubizňák <kubiznak@2n.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* json-glib: depend on glib-2.0-nativePetr Kubizňák2023-04-031-1/+1
| | | | | | | | | | | When gobject-introspection feature is disabled, glib-2.0-native package dependency is not pulled in but json-glib has a hard dependency on it (do_configure fails due to missing glib-mkenums). (From OE-Core rev: 2d67634d778bce9efdad9df75b3fe3e224708d7f) Signed-off-by: Petr Kubizňák <kubiznak@2n.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* harfbuzz: depend on glib-2.0-nativePetr Kubizňák2023-04-031-0/+2
| | | | | | | | | | | When gobject-introspection feature is disabled, glib-2.0-native package dependency is not pulled in but harfbuzz has a hard dependency on it (do_configure fails due to missing glib-mkenums). (From OE-Core rev: 77e6edba704873d21c2cf946d1be18e13abb9f5e) Signed-off-by: Petr Kubizňák <kubiznak@2n.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* selftest: runqemu: use better error message when asserts failMartin Jansa2023-04-031-3/+6
| | | | | | | | | | | | * It was showing whole log and that the runqemu command failed, but not where the log file is, nor why it thinks the runqemu failed [YOCTO #12937] (From OE-Core rev: ad4b72e6524114a3bdee10cab71f194ea143cd24) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* selftest: runqemu: better check for ROOTFS: in the logMartin Jansa2023-04-031-1/+2
| | | | | | | | | | | | | | | | | | * it was searching for line like this: ROOTFS: [/OE/build/poky/build/build-st-2023-03-20-esdk-runqemu-patch1/runqemu.RunqemuTests.test_boot_machine_ext4/build-st/tmp/deploy/images/qemux86-64/core-image-minimal-qemux86-64-20230320081121.rootfs.ext4] but with IMAGE_NAME_SUFFIX changed to something else than default ".rootfs" or with my pending changes the line looks like this: ROOTFS: [/OE/build/poky/build/build-st-2023-03-20-esdk-runqemu-patch2/runqemu.RunqemuTests.test_boot_machine_ext4/build-st/tmp/deploy/images/qemux86-64/core-image-minimal-qemux86-64.rootfs-20230320085744.ext4] and test was failing. * Check for whole line starting with ROOTFS: and ending just with .ext4 [YOCTO #12937] (From OE-Core rev: 7a0f622f23aff2c4eeca0606e7682931eb53287a) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* selftest: imagefeatures.py: don't mix tabs and spaces for indentationMartin Jansa2023-04-031-4/+4
| | | | | | | | | | * introduced in: https://git.openembedded.org/openembedded-core/commit/?id=96d4486df6d870ef19e2055b026729e66bc118f3 (From OE-Core rev: 143f624116802579e7a6804c8d4b562f931880c8) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* cargo-update-recipe-crates: force name overridesFrederic Martinsons2023-04-011-19/+16
| | | | | | | | | | | | | | | | | | | | A project can have multiple Cargo.lock (provides multiple binaries for example) and each one can depends on differenct version of the same crates. Even within the same Cargo.lock file, it is possible to have different version of same crates. To avoid conflicts, override the name with the version for all crates checksum Moreover, when searching for Cargo.lock, we should ignore specific dir like .git (no use to walk down there) and .pc (because it can have a Cargo.lock if this file was patched) (From OE-Core rev: 1795e98a04ad09b011afcc7cc3bf6dc49475b19a) Signed-off-by: Frederic Martinsons <frederic.martinsons@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meta-selftest: provide a recipe for zvariantFrederic Martinsons2023-04-011-0/+93
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This recipe is for showing a "real world" example of a crate that depends on some git repositories. Usually, this kind of crate is built within a global workspace (here it is the zbus project) and so doesn't need a Cargo.lock on its own. For the sake of the demonstration, I had to tweak things a little to be able to compile zvariant in standalone (no relative path in dependency, no symlink to LICENSE provide a Cargo.lock) The use case where the crate had some git repository in dependency is very common for "private" crate that are not aimed to be published on crates.io. When the project grow bigger, it is common to have a bin and multiple lib developped in parallel, and these libs are surely on a git repostitory. A test case have been also added to check for: - the previous patch about git subpath parameter and devtool - the correctness of overriding dependencies (first patch of the series) (From OE-Core rev: 409e045f96f69877de6f36ed14c5c19a9cb74eaf) Signed-off-by: Frederic Martinsons <frederic.martinsons@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* patch: support of git patches when the source uri contained subpath parameterFrederic Martinsons2023-04-011-13/+44
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This is for a specific case where: - A recipe use a subpath on a git repo (e.g. git://repo.git/projects;subpath=subproject) - The recipe contains a patch to apply - a devtool modify is used on this recipe With these conditions, the patch cannot be applied at all. GitApplyTree class is used for handling patch under devtool, but when subpath is present in SRC_URI, the resulting git tree is dirty (every files and directories which was not in subpath are suppressed) and so "git am" refuse to apply patches. That would not be an issue since the GitApplyTree have a fallback to PatchTree in case of error, but during this error management, there is a "git reset --hard HEAD" call which suppress the subpath operation and finally prevents the patch to be applied even with PatchTree. When devtool is not involved, only PatchTree class is used and the above problem is irrelevant. To support git patching during devtool, the presence of subpath and the dirtyness of the repo are checked. If both conditions are met, we directly call PatchTree like it was already done in case of error during git apply. (From OE-Core rev: d86cac2759cf7e91f4ff240833385e28e729ab79) Signed-off-by: Frederic Martinsons <frederic.martinsons@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* devtool: add support for multiple git url inside a cargo based recipeFrederic Martinsons2023-04-011-3/+1
| | | | | | | | | | | | | | | | Without that, the possible git urls that are in SRC_URI of a recipe are removed from SRC_URI during devtool process and so the cargo_common_do_patch_paths in cargo_common.bbclass cannot patch these packages to fetch them locally. I use a generic type name because I foresee this change will be useful for recipe that used a package manager (cargo but also npm) see https://bugzilla.yoctoproject.org/show_bug.cgi?id=11015 (From OE-Core rev: 474658a3681c343385c359a21c3693401217298d) Signed-off-by: Frederic Martinsons <frederic.martinsons@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* cargo_common.bbclass: add support of user in url for patchFrederic Martinsons2023-04-011-1/+4
| | | | | | | | | To handle url like git://git@repo/project (From OE-Core rev: ad99ede096aff03c974b8725d90d3c9d1056bae0) Signed-off-by: Frederic Martinsons <frederic.martinsons@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* cargo_common.bbclass: Support local github reposAlex Kiernan2023-04-011-0/+30
| | | | | | | | | | | | | | | | | | | | | | Since disable network was added cargo configurations which reference git repos fail as they attempt to fetch across the network as part of do_compile, even if EXTRA_OECARGO_PATHS to add them as part of `paths` is used, as this is documented as only working for packages which exist in crates.io. Add parsing of the SRC_URIs for git repos and include `[patch]` sections to redirect to the checked out source repos which the bitbake fetcher has already populated. There are still cases which don't work - if you have multiple copies of the same repo with different revisions, there's currently no way to represent that and anything using a repo which has a virtual manifest will fail to build (see https://github.com/rust-lang/cargo/issues/4934). (From OE-Core rev: 684a8af41c5bb70db68e75f72bdc4c9b09630810) Signed-off-by: Alex Kiernan <alex.kiernan@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* cve-update-nvd2-native: new CVE database fetcherMarta Rybczynska2023-04-012-2/+335
| | | | | | | | | | | | | | | | | | | Add new fetcher for the NVD database using the 2.0 API [1]. The implementation changes as little as possible, keeping the current database format (but using a different database file for the transition period), with a notable exception of not using the META table. Minor changes that could be visible: - the database starts in 1999 instead of 2002 - the complete fetch is longer (30 minutes typically) [1] https://nvd.nist.gov/developers/vulnerabilities (From OE-Core rev: fb62c4c3dbca4e58f7ce6cf29d4b630a06411a97) Signed-off-by: Marta Rybczynska <marta.rybczynska@syslinbit.com> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqa: whitespace and indentation cleanupsEnrico Jörns2023-03-314-16/+16
| | | | | | | (From OE-Core rev: 4922221d1259e2f78233f17bb901cdac5b9aa520) Signed-off-by: Enrico Jorns <ejo@pengutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqa/utils/qemurunner: fix undefined TimeoutExpiredEnrico Jörns2023-03-311-1/+1
| | | | | | | (From OE-Core rev: 19ae3f4440b09d4cfe4bc589d859d476168541bd) Signed-off-by: Enrico Jorns <ejo@pengutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqa/utils/qemurunner: limit precision of timing debugging outputEnrico Jörns2023-03-311-7/+7
| | | | | | | | | | | | | * There is no need to be that precise. It just irritates in the logs. * There is also no point in printing plain time.time() value a single time while only using formatted printout everywhere else, thus remove it. * Use %d for printing integer times (From OE-Core rev: f0988cb8cf8d03708490cca4eba345492ef78d52) Signed-off-by: Enrico Jorns <ejo@pengutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqa/utils/qemurunner: replace hard-coded user 'root' in debug outputEnrico Jörns2023-03-311-2/+2
| | | | | | | | | | | | Since login user is configurable with boot_patterns['send_login_user'], unconditionally using 'root' in the debug message can be confusing. Also fix the debug message to say 'Logged in' instead of 'Logged'. (From OE-Core rev: 900e3d42b918b5a33d8d952b3a8078fbe72ba98f) Signed-off-by: Enrico Jorns <ejo@pengutronix.de> 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 12:47:32 +0000