Wang Mingyu [Wed, 5 Nov 2025 23:46:47 +0000 (07:46 +0800)]
btrfs-tools: upgrade 6.16 -> 6.17
Changelog:
==========
* inspect list-chunks: more sorting keys, descending order
* fi resize: add support for offline (unmounted) growing of single device
* device stats: add support for offline (unmounted) reads
* quota status: new command, overview what mode is enabled, tunables
* fi commit-stats: new command, print various commit stats from sysfs (since
kernel 6.1)
* balance start: print warning and delay start if there's a missing device
in the filesystem
* mkfs:
* print zoned mode (native, emulated)
* check:
* verify device bytes in super block item and in chunk tree
* other
* updated CI, new and updated tests
* cleanups, refactoring
* documentation updates
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
3.54.3 - 2025-09-21
-------------------
* Do not skip symbols both in Gio and in platform specific :mr:`452`
3.54.2 - 2025-09-13
-------------------
* Prefix platform specific symbols with platform name :mr:`451`
3.54.1 - 2025-09-12
-------------------
* Excempt GioPlatform namespaces from required version check :mr:`450`
3.54.0 - 2025-09-06
-------------------
* Fix compatibility with Python 3.14 :mr:`433`
* Add platform specific symbols back to Gio module :mr:`445`
* Include docs from old GNOME wiki :mr:`441`
* Add override for `GLib.MainContext.query()` :mr:`446`
* Fix optional inout parameter marshalling :mr:`447`
3.53.0 - 2025-08-27
-------------------
* Drop Python upper limit :mr:`418`
* Add `__enum|flags_values__` back to GEnum and GFlags :mr:`420`
* Fix asyncio event loop selector with Python 3.13 :mr:`421`
* Support `Gtk.Template` on sub-classed Python classes :mr:`199`
* Use GI Repository singleton if GLib >= 2.85 :mr:`427`
* Expose finish_func on function info to determine if a function can be used as awaitable :mr:`428`
* Documentation updates :mr:`424` :mr:`426` :mr:`429` :mr:`430`
* `ParamSpec` objects now return the expected enum type :mr:`432`
* Fix `Gio.ActionMap` override for `Gio.Application` :mr:`435`
* Fix regression for functions with multiple callbacks :mr:`436` :mr:`437`
* Cleanup: callable argument cache :mr:`438`
* Format Python and C code :mr:`386`
* Fix compatibility with GLib 2.84 :mr:`443`
* (chore) clean up array cache code :mr:`440`
Signed-off-by: Jörg Sommer <joerg.sommer@navimatix.de> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
See release notes at
- http://downloads.yoctoproject.org/releases/opkg/opkg-0.9.0.release-notes
[0.9.0] - 2025-06-27
Semiannual opkg release.
Bumping the minor version as a result of the project build tooling changing from autotools to cmake.
- Added a Dockerfile container definition (`:docker/`) for a valid developer build environment for opkg.
- It's recommended that project contributors use this container to build and test their changes.
- The AutoTools-based build framework has [been replaced](https://git.yoctoproject.org/opkg/commit/?id=3f6040e321634471ec442fb0e80f140f1437e90b) with a more modern, CMake framework.
- Refer to the `docs/CONTRIBUTING.md` documentation for updated build instructions.
Peter Marko [Sat, 22 Nov 2025 19:37:10 +0000 (20:37 +0100)]
libarchive: upgrade 3.8.2 -> 3.8.3
Release Notes [1]:
Libarchive 3.8.3 is a bugfix and security release.
Security fixes:
* lib: Create temporary files in the target directory (#2753)
* lha: Fix for an out-of-bounds buffer overrun when using p[H_LEVEL_OFFSET] (#2768)
* 7-zip: Fix a buffer overrun when reading truncated 7zip headers (#2769)
Notable bugxies:
* lz4 and zstd: Support both lz4 and zstd data with leading skippable frames (#2771)
Full Changelog: [2]
a832a5222e48 (HEAD, tag: llvmorg-21.1.6) Reland "[LoongArch] Add `isSafeToMove` hook to prevent unsafe instruction motion" (#167465) 2d631cc168b2 [CMake][Release] Stop linking against stage1 runtimes (#164017) 6ca64545e1eb [MachineCopyPropagation] Remove logic to recognise and delete no-op moves produced after forwarded uses (#167336) 69586a904bb8 [RISCV] Correct the CFA offsets for stack probing. (#166616) 2fde0df91125 [clang][modules] Fix crash in enum visibility lookup for C++20 header units (#166272) 251d2d374e01 [Github] Backport ABI Workflow Changes to Release Branch 4b2ac3f7a210 [debugserver] Fix debugserver build on < macOS 10.15 (#166599) 4aaab27c2343 Bump version to 21.1.6
Veeresh Kadasani [Mon, 17 Nov 2025 17:54:22 +0000 (23:24 +0530)]
weston: Add PipeWire as runtime dependency
- Add pipewire as a runtime dependency in PACKAGECONFIG[pipewire].
This ensures the PipeWire backend is properly enabled and the
runtime dependency is present when selected.
Wang Mingyu [Mon, 17 Nov 2025 00:42:28 +0000 (08:42 +0800)]
libdnf: upgrade 0.74.0 -> 0.75.0
optional-check.patch
removed since it's included in 0.75.0
Add patches to fix compilation error with musl:
0001-dnf-repo-Define-FNM_EXTMATCH-if-not-already-like-und.patch
0001-utils-utils.cpp-fix-compilation-with-musl.patch
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Enrico Jörns [Mon, 24 Nov 2025 22:49:26 +0000 (23:49 +0100)]
barebox: upgrade 2025.09.0 -> 2025.11.0
Changes in 2025.11.0
--------------------
* New boards supported: i.MX93 FRDM, Enclustra Mercury+ SA2.
* Stricter validation of network data in NFS client code.
* Enhance 'parted' command: allows creating partitions up to the end of the
device.
* Various fixes and improvements.
* Added support for device mapper and dm-verity.
Prepares for secure boot without the need for FIT images.
* Added security policy support.
Kconfig-level decision of operations allowed/forbidden in a specific
security mode.
* New boards supported: Samsung Galaxy S8, Samsung Galaxy S20 5G, Radxa
Rock-5T and Protonic PRT8ML.
* Various fixes and improvements.
Changelog:
- Fix issue with handling display of battery charge level.
- Fix issue with BASS permissions not requiring encryption.
- Fix issue with handling abort for OBEX SRM operation.
- Fix issue with handling device privacy.
- Add support for HFP call answer support.
- Add support for HFP simple 3-way call support.
Full changelog:
https://github.com/bluez/bluez/compare/5.84...5.85
----
Other notes:
- A new testing tool is added called 6lowpan-tester
- A patch is removed since it is included in the 5.85 release
Signed-off-by: Guðni Már Gilbert <gudni.m.g@gmail.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Moritz Haase [Mon, 24 Nov 2025 05:55:33 +0000 (06:55 +0100)]
curl: Ensure 'CURL_CA_BUNDLE' from host env is indeed respected
Due to what looks like a copy'n'paste mistake, the environment setup script
might override 'CURL_CA_BUNDLE' from the host env instead of leaving it
untouched. Fix that.
Paul Barker [Mon, 3 Nov 2025 20:11:20 +0000 (20:11 +0000)]
pseudo: Add hard sstate dependencies for pseudo-native
Where a task (such as do_package) runs under fakeroot, the corresponding
setscene task (do_package_setscene) will also run under fakeroot when
restoring from sstate. Assuming pseudo is used as the fakeroot
implementation, we need pseudo-native and all its runtime dependencies
to be available in the sysroot before running any setscene tasks under
fakeroot.
We already add a hard dependency from all do_package_setscene tasks to
virtual/fakeroot-native:do_populate_sysroot in base.bbclass, but this
does not cover transitive dependencies. So, extend the dependencies of
pseudo-native:do_populate_sysroot_setscene to ensure that the sqlite3
library is also available in the sysroot before running fakeroot
setscene tasks.
[YOCTO #15963]
Signed-off-by: Paul Barker <paul@pbarker.dev> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
ImportError: Failed to import test module: apt
Traceback (most recent call last):
File "/usr/lib/python3.13/unittest/loader.py", line 396, in _find_test_path
module = self._get_module_from_name(name)
File "/usr/lib/python3.13/unittest/loader.py", line 339, in _get_module_from_name
__import__(name)
~~~~~~~~~~^^^^^^
File "/lava-downloads/core-image-sato/meta/lib/oeqa/runtime/cases/apt.py", line 8, in <module>
from oeqa.utils.httpserver import HTTPService
File "/lava-downloads/core-image-sato/meta/lib/oeqa/utils/httpserver.py", line 9, in <module>
from bb import multiprocessing
ModuleNotFoundError: No module named 'bb'
Signed-off-by: Mikko Rapeli <mikko.rapeli@linaro.org> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
To avoid errors we need to set a weak default for DEBUG_PREFIX_MAP_EXTRA
as it is not always set by toolchain include files.
Also, bug YOCTO #15976 mixes flags to the llvm compiler in rust and
we need to avoid the canon-prefix-map option in DEBUG_PREFIX_MAP_EXTRA.
For now, just remove this until we can properly fix the rust flags handling.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Gyorgy Sarvari [Thu, 20 Nov 2025 12:19:46 +0000 (13:19 +0100)]
bitbake.conf, gcc toolchain: add -fcanon-prefix-map to map-prefixes
This patch adds -fcanon-prefix-map to the list of compile file-prefixes
list in case at least gcc 13 is used (it's a gcc-only flag).
This flag used to be part of this list in the past, but was removed with [1].
Since then the source file paths are not canonicalized, which makes
the system to miss some (and sometimes all) source files to include
in the corresponding -src packages. As an example sqlite3 and audiofile
(from meta-oe) produces empty src packages, mostly due to the pathes:
they frequently use relative paths that don't match up with the
absolute path specified in the file-preifx map:
`pwd`/../../foo.cpp and ${S}/foo.cpp might refer to the same file, but
the first one won't match the prefix-map, so it is omitted.
This patch adds this option again with gcc in the target case.
Signed-off-by: Gyorgy Sarvari <skandigraun@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
configfragments.py: Correct the help for enable-fragment
The help entry for --quiet had been added to list-fragments rather than
enable-fragment.
Due to the fact that --quiet is a global option, this actually adds a
dummy --quiet option as it would otherwise hide the global option, but
would never be set since any --quiet argument would already have been
parsed when this option is parsed.
Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Current du parameters used in wic scripts are conflicting: -b implies
--block-size=1 while -k implies --block-size=1K. When both parameters
are used, coreutils du and uutils du do not react similarly, leading to
failures on Ubuntu 25.10.
As we do want to use the 1K block size, remove -b and add
--apparent-size that was implied by it, so we have a predictable
behaviour.
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
gawk: use native gawk when building glibc and grub
Different versions of gawk can produce different output,
so depending on which version is installed on the build host,
reproducibility issues can occur:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=16072
So far only glibc and grub have been identified to have
the issue; probably more fixes of similar nature will be
required going forward.
Adjust the gawk recipe to apply target-only tweaks
(particularly the removal of awk symlink to allow for alternatives)
to only target and nativesdk variants, so that native installs
both awk and gawk executables.
[YOCTO #16072]
Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Robert Yang [Sun, 16 Nov 2025 11:54:20 +0000 (03:54 -0800)]
package.bbclass: Fix base_ver for AUTOINC
The srcpv isn't in PV any more after the following commit:
a8e7b0f932 base/package: Move source revision information from PV to PKGV
So the version.find(srcpv) will be -1, which would make base_ver to something like:
glibc-2.39+git-r (The 0 is removed)
There will be bugs when both of the following conditions are met:
* The srcrev is upgraded from value such as cff104 to b027d5 (b is less c)
* The PR value is changed from value such as r0 to r10
This would make glibc-2.39+git-r can't match glibc-2.39+git-r1, so the AUTOINC won't work,
and would still be git0, then buildhistory would report errors like:
ERROR: glibc-2.39+git-r0 do_packagedata_setscene: QA Issue: Package version for package glibc-src went backwards which would break package feeds (from 0:2.39+git0+cff1042cce-r0.0 to 0:2.39+git0+b027d5b145-r10.0) [version-going-backwards]
Strip PR to make it work as before, just like it stripped the string after
srcpv in the past.
Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
local.conf.sample: comment out the root-with-empty-password setting
This was not a good default; the autobuilder relied on it, but this
has been fixed, there's now a separate fragment as well, and testimage
has a check for the needed image features. Let's take this out and
be more secure by default everywhere.
Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
local.conf.sample: do not set PACKAGE_CLASSES as it is matching oe-core's default
This setting isn't necessary as it matches what is set in oe-core
already. It may also interfere with settings on other places
such as distro files or fragments.
Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
meta/files/bitbake-setup.schema.json: move to bitbake repo
The schema for bitbake-setup configurations was provisionally
placed into oe-core, as it is an extension of an earlier
layer setup schema, but with bitbake-setup becoming the primary
way to set up layers, it makes sense to maintain both schemas
in bitbake, so that any updates and tweaks can be done in
lockstep in a single repository.
Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Ross Burton [Thu, 13 Nov 2025 16:34:38 +0000 (16:34 +0000)]
initscripts: don't read /proc/cmdline in populate-volatile during build
The populate-volatile script will check for "clearcache" in the kernel
command line and wipe the caches if it has been set. This is useful at
boot, but we shouldn't be checking the kernel commandline when being
ran on the build machine at rootfs-time.
[ YOCTO #16056 ]
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>
Vishwas Udupa [Wed, 12 Nov 2025 11:28:23 +0000 (16:58 +0530)]
findutils:/var is populated by base-files, so no need to repack empty dir
findutils installs an empty /var which is already created
by base-files. It doesn't need to be packaged by findutils.
this helps to align towards stateless
system expectations or when updates are done via meta-updater.
Jon Mason [Thu, 13 Nov 2025 15:18:01 +0000 (10:18 -0500)]
runqemu: avoid setting "mem=" when using a DTB
Some emulated machines, such as the Raspberry Pi models, fail to boot
if a fixed "mem=" value is passed on the kernel command line. When a
DTB is used (QB_DTB is set), the memory size is already defined there,
so specifying it again is unnecessary and can cause issues.
Skip adding "mem=" to the kernel command line when QB_DTB is present.
Signed-off-by: Jon Mason <jon.mason@arm.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
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>
Peter Marko [Thu, 13 Nov 2025 12:15:33 +0000 (13:15 +0100)]
oeqa: drop unnecessary dependency from go runtime tests
The tests do not use scp command, so openssh-scp is not needed.
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>
Peter Marko [Thu, 13 Nov 2025 08:11:48 +0000 (09:11 +0100)]
go-helloworld: fix license
The example repo doesn't seem to have ever been under MIT.
It started with Apache-2.0, later changed to standard go license BSD-3.
The license file exists in the sources, so use that one instead of
taking it from the OE-Core license directory.
Note that this was already fixed in scarthgap and kirkstone, but it was
not submitted to master. Also the old releases still had Apache, so this
patch is different now with new versioni of thie component.
License-Update: Fix license declaration.
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>
Peter Marko [Thu, 13 Nov 2025 07:45:25 +0000 (08:45 +0100)]
oeqa: fix package detection in go sdk tests
The test are skipped if architecture contains dash because TARGET_ARCH
contains underscore while package name contains dash. Here the
translation needs to be done.
Note that poky distro default arch has dash:
MACHINE="qemux86-64"
TARGET_ARCH="x86_64"
ERROR: Nothing PROVIDES 'go-cross-canadian-x86_64'. Close matches:
gcc-cross-canadian-x86-64
gdb-cross-canadian-x86-64
go-cross-canadian-x86-64
TRANSLATED_TARGET_ARCH="x86-64"
Quoting meta/classes-recipe/cross-canadian.bbclass:
TRANSLATED_TARGET_ARCH is added into PN
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>
Upgrade the firmware package to latest release. Add new
Qualcomm firmware packages, rename HP package, and update
FILES path for packages ${PN}-ti-{tas2563, tas2781}.
Ross Burton [Wed, 12 Nov 2025 21:06:50 +0000 (21:06 +0000)]
classes/gnomebase: set S using GNOMEBN instead of BPN
For the majority of recipes, the default S is correct. But a few recipes
have a package name that is not the recipe name (such as GConf), and
we already handle this in the SRC_URI assignment.
Use GNOMEBN in the S assignment instead of PN so that S is correct too.
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>
terminal: Show a warning when launched terminal quickly exits
Terminals quitting in less than one second are likely the result of a
failure to execute the launched command: show a warning including the
command that was launched, so the user can try to debug this.
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
As the poky repository is no longer used, measurements are indexed using
the oe-core commit. But as bitbake, oe-core and meta-yocto are now
retrieved from separate gits, while measuring performances for a given branch
at some time interval, we can get the same commit for oe-core but
different ones for bitbake or meta-yocto. As a consequence, metadata
associated with the same index (oe-core commit) might differ.
To work around this, relax the equality checks for commit, commit_time
and commit_count since they might no longer match.
Ideally we'd group them into separate results but for now, treat them
as being the same.
[Based on work from Mathieu Dubois-Briand but fixed differently] Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Anuj Mittal [Fri, 7 Nov 2025 15:53:30 +0000 (21:23 +0530)]
logrotate: remove reference to state file in CONFFILES
Since commit a1f7225884 (logrotate: Do not create logrotate.status file) in
poky, logrotate.status is not installed or packaged. Remove reference to it from
CONFFILES and don't try to create /var/lib which is already taken care of by
base-files.
Joshua Watt [Thu, 6 Nov 2025 15:50:21 +0000 (08:50 -0700)]
wayland: Remove event_loop_timer test
The event_loop_timer test requires precise timing constraints (10's of
milliseconds) which cannot be achieved on qemu testing targets. Remove
this test to prevent spurious failures.
features_check: improve error message for missing required DISTRO_FEATURES
The original message for REQUIRED_DISTRO_FEATURES entries that were
missing from DISTRO_FEATURES was:
ERROR: Nothing PROVIDES 'core-image-weston'
core-image-weston was skipped: missing required distro feature 'wayland'
(not in DISTRO_FEATURES)
For newcomers, this is error message doesn't provide enough information to
identify the root cause, which could be: using the wrong DISTRO. This patch
changes the error message to include the distro name:
ERROR: Nothing PROVIDES 'core-image-weston'
core-image-weston was skipped: using DISTRO 'nodistro', which is missing
required DISTRO_FEATURES: 'wayland'
Signed-off-by: Walter Werner SCHNEIDER <contact@schnwalter.eu> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
8e2cd28cd4ba (HEAD, tag: llvmorg-21.1.5) [OpenMP] Fix preprocessor mismatches between include and usages of hwloc (#158349) df3145bf4239 [clang-shlib] Fix linking libclang-cpp on Haiku (#156401) 6bb6ffef0a5d [LLD][COFF] Fix manifest UAC trustInfo namespace (#165285) 0921531330ad [llvm-objcopy][COFF] Update .symidx values after stripping (#153322) c346c16f93d5 [BPF] Do not emit names for PTR, CONST, VOLATILE and RESTRICT BTF types (#163174) 11ef7520536c [BPF] Support for `DW_TAG_variant_part` in BTF generation (#155783) 495a2ab653ae [Hexagon] Add REQUIRES: asserts to test a2178ebcb02a [Hexagon] Incorrect MIR after "hexinsert" pass (#164021) 04102d998d0e [AArch64][llvm] Relax mandatory features for Armv9.6-A (#163973) 5c802f9eac66 [Clang] Do not warn on UTF-16 -> UTF-32 conversions. (#163927) e94561caef48 workflows/release-documentation: Allow secrets pass through from calling workflow (#162765) 1600cf040584 [Github] Only look at previous commit for MacOS Premerge (#164483) cd7d2db5a50c [lld][test] Fix AArch64 build attribute test cleanup 2cdfa9d9383c [X86] Use pseudo instructions to zero registers in `buildClearRegister` (#163358) 9faef12c7209 [sancov] Fix stack-depth tracking to use debug locations (#162428) 45afac62e373 Bump version to 21.1.5
Ross Burton [Thu, 6 Nov 2025 18:14:57 +0000 (18:14 +0000)]
nativesdk: don't map packaging variables if the recipe inherits nativesdk
The nativesdk class uses a ClassExtender to remap variables and
references, for example turning foo to nativesdk-foo. We need to do this
always because when the nativesdk class is inherited in a recipe these
need to update automatically: DEPENDS=bar should be DEPENDS=nativesdk-bar.
This mapping extends to the packaging variables (RDEPENDS, etc) as it is
usual for nativesdk to be used via BBCLASSEXTEND, so the recipe would be
written using RDEPENDS:${PN}=bar and the class would turn that into
nativesdk-bar automatically.
Some recipes don't use BBCLASSEXTEND and instead inherit nativesdk
directly. These recipes typically use "nativesdk-bar" explicitly and the
remapping isn't needed. However, the remapping still runs: it normally
has no effect but it will still run.
This is a problem for the recipes that use sdk-provides-dummy.inc to
provide names that we don't want to be in the SDK. Notably,
nativesdk-target-provides-dummy provides "pkgconfig" because packages
can have that literal dependency injected into them by rpmdeps, and
the remapping was changing this to nativesdk-pkgconfig: the intended
provides wasn't present and it became impossible to install pkgconfig
into the nativesdk sysroot.
Note that this broke when the class extension switched to use the new
bitbake filtering API[1], as this meant the remapping happens when the
variables are _read_ instead of at parse time.
[1] oe-core 24a9858a892 ("classes/lib: Switch classextend to use new filter API")
Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Mike Crowe [Mon, 3 Nov 2025 15:42:34 +0000 (15:42 +0000)]
sanity: Emit the error message if CONNECTIVITY_CHECK_MSG is set
Users may still be interested in the actual error message even if there
is a custom message for failure of the connectivity check since the
cause may be intermittent.
Signed-off-by: Mike Crowe <mac@mcrowe.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Niko Mauno [Tue, 4 Nov 2025 08:33:30 +0000 (08:33 +0000)]
cve-update-db-native: pycodestyle fixes
Fixes following pycodestyle complaints:
cve-update-db-native.bb:80:39: E712 comparison to True should be 'if cond is True:' or 'if cond:'
cve-update-db-native.bb:128:20: E401 multiple imports on one line
cve-update-db-native.bb:130:18: E401 multiple imports on one line
cve-update-db-native.bb:171:21: E741 ambiguous variable name 'l'
cve-update-db-native.bb:335:26: E225 missing whitespace around operator
cve-update-db-native.bb:344:12: E713 test for membership should be 'not in'
cve-update-db-native.bb:347:12: E713 test for membership should be 'not in'
Also leaves out a redundant 'gzip' import in update_db_file().
Signed-off-by: Niko Mauno <niko.mauno@vaisala.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Niko Mauno [Tue, 4 Nov 2025 08:33:29 +0000 (08:33 +0000)]
cve-update-nvd2-native: pycodestyle fixes
Fixes following pycodestyle complaints:
cve-update-nvd2-native.bb:95:54: E712 comparison to True should be 'if cond is True:' or 'if cond:'
cve-update-nvd2-native.bb:127:15: E211 whitespace before '('
cve-update-nvd2-native.bb:127:17: E201 whitespace after '('
cve-update-nvd2-native.bb:127:19: E201 whitespace after '('
cve-update-nvd2-native.bb:127:44: E202 whitespace before ')'
cve-update-nvd2-native.bb:127:46: E203 whitespace before ','
cve-update-nvd2-native.bb:174:20: E401 multiple imports on one line
cve-update-nvd2-native.bb:183:29: E203 whitespace before ':'
cve-update-nvd2-native.bb:236:16: E111 indentation is not a multiple of 4
cve-update-nvd2-native.bb:241:16: E111 indentation is not a multiple of 4
cve-update-nvd2-native.bb:336:39: E222 multiple spaces after operator
Signed-off-by: Niko Mauno <niko.mauno@vaisala.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Richard Purdie [Mon, 10 Nov 2025 13:59:03 +0000 (13:59 +0000)]
oeqa/selftest/devtool: Update after upstream repo changes
The upstream changed the branch name, moving to archive/ so we need to
update too. Take the opportunity to match the new location too to avoid
the redirect.
We could use a different branch but upstream would probably eventually
rename that too so this may last longer.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The rationale is that both properties are relative to their respective directories
and that should be documented and clear from their names (without being too verbose).
Based on a patch from Alexander Kanavin <alex@linutronix.de> but with
updated naming.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Gyorgy Sarvari [Thu, 23 Oct 2025 10:50:58 +0000 (12:50 +0200)]
openssl: extend check_cwm test timeout
Fixes [YOCTO 14649]
The default 3s test execution timeout isn't always enough for the check_cwm test
on the autobuilder in case there is a high load on the host machine,
and due to this this case fails sometimes.
This patch doubles the timeout for this testcase to 6 seconds to allow enough
time for execution even if there is high CPU usage by other processes.
Ross Burton [Mon, 3 Nov 2025 14:21:46 +0000 (14:21 +0000)]
kea: fix CVE-2025-11232
Backport a patch from upstream to resolve CVE-2025-11232:
Invalid characters cause assert
To trigger the issue, three configuration parameters must have
specific settings: "hostname-char-set" must be left at the default
setting, which is "[^A-Za-z0-9.-]"; "hostname-char-replacement" must
be empty (the default); and "ddns-qualifying-suffix" must NOT be empty
(the default is empty). DDNS updates do not need to be enabled for
this issue to manifest. A client that sends certain option content
would then cause kea-dhcp4 to exit unexpectedly.
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>
projects / thirdparty / openembedded / openembedded-core.git / log
