wayland-protocols 1.49 includes the following changes:
- Improve multi-GPU support in linux-dmabuf-v1
- Add Windows BT.2100 image descriptions to color-management-v1
- A new experimental protocol for fractional scaling
Peter Marko [Thu, 11 Jun 2026 22:06:10 +0000 (00:06 +0200)]
openssl: upgrade 3.5.6 -> 3.5.7
Release information [1]:
OpenSSL 3.5.7 is a security patch release. The most severe CVE fixed in this release is High.
This release incorporates the following bug fixes and mitigations:
* Fixed heap use-after-free in PKCS7_verify(). (CVE-2026-45447)
* Fixed CMS AuthEnvelopedData processing may accept forged messages. (CVE-2026-34182)
* Fixed unbounded memory growth in the QUIC PATH_CHALLENGE handler. (CVE-2026-34183)
* Fixed NULL pointer dereference in QUIC server initial packet handling. (CVE-2026-42764)
* Fixed AES-OCB IV ignored on EVP_Cipher() path. (CVE-2026-45445)
* Fixed possible heap buffer overflow in ASN.1 multibyte string conversion. (CVE-2026-7383)
* Fixed out-of-bounds read in CMS password-based decryption. (CVE-2026-9076)
* Fixed heap buffer over-read in ASN.1 content parsing. (CVE-2026-34180)
* Fixed PKCS#12 files with PBMAC1 are accepted with short HMAC keys. (CVE-2026-34181)
* Fixed possible NULL dereference in password-dased CMS decryption. (CVE-2026-42766)
* Fixed NULL pointer dereference in CRMF EncryptedValue decryption. (CVE-2026-42767)
* Fixed multi-RecipientInfo Bleichenbacher Oracle in CMS_decrypt() and PKCS7_decrypt(). (CVE-2026-42768)
* Fixed trust anchor substitution via cert/issuer typo in CMP rootCaKeyUpdate. (CVE-2026-42769)
* Fixed FFC-DH peer validation uses attacker-supplied q. (CVE-2026-42770)
* Fixed incorrect tag processing for empty messages in AES-GCM-SIV and AES-SIV modes. (CVE-2026-45446)
Refreshed patches.
Installed new test files to pass ptests.
Wang Mingyu [Wed, 10 Jun 2026 09:49:29 +0000 (17:49 +0800)]
kbd: upgrade 2.9.0 -> 2.10.0
0001-Preserve-only-necessary-metadata-during-install.patch
0001-libkbdfile-Fix-problem-with-undeclared-sym_gzopen.patch
removed since they're included in 2.10.0
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>
Wang Mingyu [Wed, 10 Jun 2026 09:49:26 +0000 (17:49 +0800)]
gpgme: upgrade 2.0.1 -> 2.1.0
Changelog:
===========
* New flags "is_de_vs" and "beta_compliance" for encryption results.
* New decryption flag GPGME_DECRYPT_SESSION_HASH and new field
session_hash in gpgme_decrypt_result_t. For details see the gpg
option --show-session-key.
* Setting of attributes for CMS signatures is now supported via
gpgme_sig_notation_add.
* New context flag "export-filter".
* Extend the internal gpgsm_assuan_simple_command to consume all
received lines. This fixes a possible lockup introduced by the
fix for T7759.
* Fix passphrase cancel handling.
* Fix a regression wrt the auto-key-locate option.
* Handle the case when pinentry is invoked multiple times.
* Don't cap ISO dates beyond year 2037 on Windows.
* Treat empty DISPLAY envvar as unset.
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>
Wang Mingyu [Wed, 10 Jun 2026 09:49:19 +0000 (17:49 +0800)]
btrfs-tools: upgrade 6.19.1 -> 7.0
Changelog:
===========
- btrfstune: add ability to do offline conversion to the remap tree
(experimental feature)
- mkfs: add hole detection when precalculating size for --rootdir
- fixes: recognize fs-verity tree items in various tools (check)
- enable PCLMUL implementation on Musl (previously using SSE 4.2 at best)
- help format changed to be in line with common packages like util-linux
- reject writes to filesystem during check/btrfstune in case there's pending
state of device replace or balance
- other:
build ARM64 static binaries (attached to GH release) backward compatibility level is 'archv8-a'
CI updates
documentation updates
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>
Anders Heimer [Mon, 15 Jun 2026 11:14:00 +0000 (13:14 +0200)]
archiver: fix .pc tar exclude pattern
Remove shell quote characters from the .pc exclude argument now that tar is
run with an argv list.
Fixes: 7390e72669 ("classes/lib: Start to covert strings to lists...") Signed-off-by: Anders Heimer <anders.heimer@est.tech> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Anders Heimer [Mon, 15 Jun 2026 08:02:38 +0000 (10:02 +0200)]
package_manager/ipk: fix dummy install arguments
Use self.config_file and the temporary rootfs arguments for both opkg
update and the noaction install in dummy_install().
Also convert the touched opkg update call away from shell=True.
Fixes: 7390e72669 ("classes/lib: Start to covert strings to lists...") Signed-off-by: Anders Heimer <anders.heimer@est.tech> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Richard Purdie [Mon, 1 Jun 2026 09:43:55 +0000 (10:43 +0100)]
classes/lib: Start to convert strings to lists of command parameters
To follow best practises and avoid shell=True subprocess usage, start to
convert subprocess commands to use lists instead of strings. This improves
variable quoting and models modern coding standards.
In some cases we need to add different exception handling after the removal
of the shell indirection.
Convert some Popen calls to use more modern subprocess wrappers and tweak
the encoding handling to match modern parameters. Environment variables
can be passed through env and current directory via cwd.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Richard Purdie [Sat, 13 Jun 2026 07:07:42 +0000 (08:07 +0100)]
sanity: Update minimum git version to 2.22.0
I suspect we use functionality from newer versions of git than is documented.
Update to 2.22.0 as the minimum version as we are about to use
"git branch --show-current" which is in that version.
2.22.0 was released in 2019 and all our supported distros are well beyond
this version.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Otavio Salvador [Fri, 12 Jun 2026 02:48:29 +0000 (23:48 -0300)]
quota: use native rpcgen and a single-word RPCGEN_CPP
The rpc PACKAGECONFIG regenerates rquota.{c,h} and rquota_clnt.c from
rquota.x with rpcgen at build time, as the tarball ships no
pre-generated copies. Two problems made this fail:
- rpcgen was picked up from the host via HOSTTOOLS rather than from the
build, which is non-deterministic and breaks on hosts that have no
rpcgen at all.
- rpcgen execs its C preprocessor as a single program name, but OE
exports $CPP as a multi-word "gcc -E --sysroot=... <flags>" string,
so rpcgen reports "cannot find C preprocessor" and aborts.
Depend on rpcsvc-proto-native so rpcgen comes from the build, and set
RPCGEN_CPP to the single-word cross cpp so the preprocessor can be
exec'd.
Tested with bitbake quota (configure/compile/install/package) on
qemuarm.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Joshua Watt [Thu, 11 Jun 2026 15:55:55 +0000 (09:55 -0600)]
ffmpeg, x264: Add comment about circular dependency
There is a circular dependency on x264 and ffmpeg that can be triggered
if both enable the PACKAGECONFIG for the other. We don't have a way to
solve this yet, but add a comment to indicate that this is the case so
that users are not surprised when it occurs.
Hangtian Zhu [Thu, 11 Jun 2026 08:17:33 +0000 (16:17 +0800)]
wpa-supplicant: add PACKAGECONFIG controls for suiteb, wnm, and mbo
Add optional PACKAGECONFIG entries for suiteb, wnm, and mbo and map
these to the corresponding upstream build flags:
- suiteb: enable CONFIG_SUITEB and CONFIG_SUITEB192 for
WPA-EAP-SUITE-B/WPA-EAP-SUITE-B-192 enterprise modes
- wnm: enable CONFIG_WNM for IEEE 802.11v Wireless Network Management
- mbo: enable CONFIG_MBO for Multi Band Operation extensions used with
BSS Transition Management
Upstream hostap configuration keeps these as optional capabilities.
Exposing them as PACKAGECONFIG options lets distros opt in for
enterprise and roaming use cases without changing the default oe-core
feature set.
Some makeinfo commands like makeinfo --version, makeinfo --html fail on target
with errors like:Can't locate xxx.pm in @INC
This is because texinfo's texi2any requires several core Perl modules
that are split into separate packages in OE. Add the missing modules
to RDEPENDS so they are pulled into the image automatically.
Signed-off-by: Xiaozhan Li <Xiaozhan.Li.CN@windriver.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Tushar Darote [Mon, 8 Jun 2026 12:59:56 +0000 (18:29 +0530)]
gstreamer1.0-plugins-bad: handle padded buffers in wl_shm buffer creation
Use GstBuffer metadata when constructing wl_shm buffers so stride and size reflect the actual buffer layout.
This fixes incorrect rendering with DMA-backed buffers that include padding or custom strides.
broke npm install commands within the npm bitbake class since NpmEnvironment.run() expects a list
instead of a string. Update the remaining callers to pass list-based commands to avoid:
AttributeError: 'str' object has no attribute 'append'
Signed-off-by: Eric Meyers <eric.meyers@arthrex.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Ross Burton [Wed, 10 Jun 2026 16:06:49 +0000 (17:06 +0100)]
libedit: fix build on clang+musl
It turns out that the patch I deleted previously[1] is actually needed
in builds with both clang and musl. Bring it back, whilst both talking
to upstream and resurrecting an old clang patch to resolve the underlying
issue.
- QEMU 11.0.0 has officially dropped all support for 32-bit host systems.
This includes the ability to build the system emulator (softmmu) on
any 32-bit host architecture. Add COMPATIBLE_HOST for class-target and
class-nativesdk to restrict builds to 64-bit architectures. Fix SDK
build failure when SDKMACHINE is 32-bit.
Note: QEMU 11.0.0 still supports emulating 32-bit guest architectures
(such as qemu-system-i386 or qemu-system-arm) as long as they are
running on a 64-bit host.
- qemu-targets.inc: skip linux-user targets when HOST_ARCH is not in the
set of architectures supported by QEMU 11.0.0's linux-user mode
(64-bit only: aarch64, loongarch64, mips64, ppc64, riscv64, s390x,
sparc64, x86_64).
- Add --cpu=${TUNE_ARCH} to EXTRA_OECONF for class-target, and add
--cpu=${SDK_ARCH} to nativesdk configure options to fix build
failure. QEMU 11's configure script falls back to 'uname -m' (x86_64)
when it cannot detect the host CPU.
- Add 0012-meson-fix-close_range-detection-on-older-glibc.patch:
the meson has_function('close_range') check succeeds at link time on
hosts with kernel >= 5.9 even when glibc < 2.34 does not declare the
function, causing implicit declaration errors. Add a prefix include
so the check only succeeds when the header declares close_range().
- Add 0013-hw-scsi-vhost-scsi-include-standard-headers-for-vhost-worker-structs.patch:
on build hosts with kernel headers < 6.0, vhost-scsi.c fails to
compile due to missing struct vhost_vring_worker/vhost_worker_state.
Include QEMU's bundled standard-headers before the system header,
matching the pattern already used in hw/virtio/vhost-backend.c.
- Drop fix-strerrorname_np.patch (fixed upstream).
Drop 0001-linux-user-elfload.c-Correction-to-HWCAP2-accessor.patch
(fixed upstream).
Drop 0001-accel-tcg-Fix-iotlb_to_section-for-different-Address.patch
(fixed upstream).
AI-Generated: kiro-cli
Signed-off-by: Quan Sun <Quan.Sun@windriver.com> Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This was merged in master, assuming that SDL UI frontend would be disabled next,
to allow update to qemu 11.x where that fronted has a regression.
Now that it was decided we should try and fix (or help fix) the actual issue
in that frontend [1], keeping this change would effectively disable testing
of the Gtk+ UI frontend (which is not enabled by default), which is an
undesirable regression in testing.
Wei Deng [Fri, 5 Jun 2026 03:00:41 +0000 (08:30 +0530)]
bluez5: set L2CAP IMTU for OBEX profile listeners
Backport upstream fix that adds an imtu field to default_settings for
OBEX profiles (OPP, FTP, PBAP, MAS, MNS) and applies it to the L2CAP
listening socket via bt_io_set(). Without this, the listening socket
advertises the L2CAP minimum of 672 bytes in L2CAP_CONFIGURATION_RSP,
limiting the peer's outgoing PDU size and degrading Rx throughput.
Upstream-Status: Backport [bluez/bluez@646014a] Signed-off-by: Wei Deng <wei.deng@oss.qualcomm.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
oeqa/selftest/archiver: Do not run bitbake -c clean unnecessarily
Now that the archiver bbclass properly adapts its output based on its
configuration, it should no longer be needed to run `bitbake -c clean`
before invoking the archiver. There is one exception, which is due to
modifying DL_DIR as it does not automatically trigger a re-fetch.
Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
archiver.bbclass: Properly remove artifacts when configuration changes
Before, the different archiver tasks that produce artifacts would just
add to the common output directory. This meant that changing how the
archiver is configured would just add more artifacts, but never remove
any. E.g., if "dumpdata" was enabled, it would add the environment data
for each built recipe to the artifacts. However, if it was then
disabled, all the generated artifacts would remain until each recipe was
manually cleaned, or the entire tmp directory was removed.
This adds a task that cleans the output directory if needed. It is a
separate task that all the other archiver tasks depend on because they
all write to the same output directory so it must only be cleaned once.
This also means it has to depend on all variables that affect any of
the other tasks.
Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Ross Burton [Mon, 8 Jun 2026 11:44:18 +0000 (12:44 +0100)]
lib/oe/recipeutils: make stable_upgrade argument optional in get_recipe_upstream_version()
The change[1] that added the stable_upgrade argument made it optional
for the high-level get_recipe_upgrade_status() function, but not
get_recipe_upstream_version().
This function is exposed API so be kind to users and also make it an
optional argument there.
[1] oe-core 1ed8fdda035 ("recipeutils: add optional stable_upgrade parameter to get_recipe_upgrade_status")
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>
Mengshi Wu [Mon, 8 Jun 2026 05:56:06 +0000 (13:56 +0800)]
bluez5: fix gatt cache sync issue
There is a timing issue to update DB Hash value.
The gatt_client_service_changed() callback in src/device.c
is called from service_changed_complete() in gatt-client.c,
which is invoked after db_hash_read_cb() has already updated
the hash. Adding store_gatt_db(device) here guarantees the
db is persisted with the correct, up-to-date hash for both
the addition and removal cases.
uboot-sign: sign SPL FIT into a copy of the SPL DTB
mkimage's -K flag injects the public key into the DTB in-place. When
the signing target is the compile-output file (spl/u-boot-spl.dtb),
each test run accumulates key nodes from all previous runs in the same
work directory. With SPL_SIGN_CONF=1 every injected key carries
required = "conf", so mkimage requires ALL of them to have signed the
configuration. When a subsequent test uses a different key only its own
key signed the FIT, causing the verification to fail with:
Failed to verify required signature 'key-<previous-keyname>'
Fix this by copying the compile-output DTB to SPL_DTB_SIGNED first and
passing the copy as the -K target. The original spl/u-boot-spl.dtb is
never modified, so each build starts from a clean state regardless of
how many times the task has been run.
Signed-off-by: Adrian Freihofer <adrian.freihofer@siemens.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
oeqa/selftest/fitimage: fix missing whitespace around assignment
BitBake conf parser expects spaces around '=' in assignment statements.
The missing spaces in the config string written to selftest.inc caused a
BitBake warning about non-standard syntax.
Signed-off-by: Adrian Freihofer <adrian.freihofer@siemens.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Peter Marko [Fri, 5 Jun 2026 12:04:55 +0000 (14:04 +0200)]
rootfs: move tasks using image_list_installed_packages to postuninstall
Since some packages can be uninstalled, any task querying installed
packages should be run only after both installation and uninstallation
is completed.
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 [Fri, 5 Jun 2026 12:04:34 +0000 (14:04 +0200)]
vex: remove obsolete semicolon
Usage of semicolon as separator in ROOTFS/IMAGE_*COMMAND was deprecated
long time ago.
Remove it.
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>
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>
Haiqing Bai [Thu, 4 Jun 2026 03:01:32 +0000 (03:01 +0000)]
xev: upgrade 1.2.6 -> 1.2.7
ChangeLog: fd3a07b9:meson: Add option to build with meson 79f0cc47:gitlab CI: drop the ci-fairy check-mr job 61c956d8:Clear -Wunused-parameter warnings 0513c8e4:Add missing indentation to second line of CreateNotify output 5d90d0e9:randr: Protect against XErrors getting output info e2c157e7:man page: fix warnings from `mandoc -T lint` eae9d09e:Improve man page formatting 8b9e87a3:Accept --help & --version as aliases to -help & -version c69f783f:Add -help option
Signed-off-by: Haiqing Bai <haiqing.bai@windriver.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Richard Purdie [Fri, 5 Jun 2026 09:11:53 +0000 (10:11 +0100)]
base: Allow zstd and xz decompression from the host tools
We have xz and zstd in HOSTTOOLS but not ASSUME_PROVIDED. In most cases where
we have a dependency on xz-native or zstd-native, we need to compress files
or we need the libraries those recipes provide. In some cases we just need
decompression though.
Compression output is version dependent so we need those dependencies. Libraries
need headers so those are needed too. THe main place we could benefit are the
unpack dependencies from base.bbclass.
Therefore add "XXX-decompress" PROVIDES to those recipes, then change the
dependency in base.bbclass to indicate decompression only. We can then
ASSUME_PROVIDED the decompression side of things to optimise builds whilst
still keeping the other dependencies functional.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Richard Purdie [Fri, 5 Jun 2026 09:12:46 +0000 (10:12 +0100)]
sysstat: Add missing xz-native DEPENDS
sysstat uses xz to compress man pages. The version from the host may vary
and hence make the output non-reproducible so we need xz-native in
DEPENDS to make the output deterministic.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Also, adjust qemu recipe to be using it, instead of its
own internal copy. With qemu 11.x the internal copy is removed
and so a separate qemu-qmp recipes becomes a requirement.
Split out from a patch from Quan Sun <Quan.Sun@windriver.com>
Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Bin Cao [Thu, 4 Jun 2026 10:10:28 +0000 (18:10 +0800)]
insane.bbclass: check for build host HOME directory in packaged files
Extend package_qa_check_buildpaths to also detect the build host's
HOME directory path in target packages. This catches cases where
\$HOME-derived paths (such as userbase in Python's sysconfig) leak
into the rootfs.
Signed-off-by: Bin Cao <bin.cao.cn@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Bin Cao [Thu, 4 Jun 2026 10:10:27 +0000 (18:10 +0800)]
python3: sanitize userbase in _sysconfig_vars JSON to avoid host path leak
The _sysconfig_vars__linux_x86_64-linux-gnu.json file contains a
"userbase" field that is populated from the build host user's $HOME
at build time. This leaks the build host user's home directory path
into the target rootfs.
The existing py_package_preprocess() cleanup for this JSON file only
strips known OE build path prefixes (STAGING_DIR_TARGET, RECIPE_SYSROOT,
etc.), but the userbase value comes from the build user's $HOME
environment variable which doesn't match any of those patterns.
Set userbase to an empty string in the packaged JSON. This is safe
because at runtime, sysconfig.get_config_vars() always recomputes
userbase by calling _getuserbase(), which resolves the actual target
user's ~/.local path dynamically. The static value in the JSON is
never used for runtime path resolution.
Signed-off-by: Bin Cao <bin.cao.cn@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Haixiao Yan [Mon, 1 Jun 2026 06:46:41 +0000 (14:46 +0800)]
subversion: fix svn-revision.txt conflict when building for qemux86-64
The revision-install target in Makefile.in generates svn-revision.txt
by first trying to run the cross-compiled svnversion binary on the host.
When the target architecture is x86-64 (same as the build host), the
cross-compiled binary can execute on the host. If the host has libapr1
installed, the 64-bit svnversion succeeds and outputs "Unversioned
directory", while the 32-bit (lib32) binary lacks the 32-bit libapr1
and fails, falling back to "unknown". The differing content causes an
RPM file conflict on /usr/include/subversion-1/svn-revision.txt when
lib32-subversion-dev and subversion-dev are installed together in
do_rootfs.
This does not affect non-x86-64 targets (e.g. ARM) because the
cross-compiled binary cannot execute on the x86-64 host, so both
64-bit and 32-bit builds fall through to the same fallback.
Since the source is a release tarball with no SVN metadata, the correct
value is always "unknown". Fix by patching Makefile.in to skip the
svnversion invocations entirely.
Signed-off-by: Haixiao Yan <haixiao.yan.cn@windriver.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Chen Qi [Mon, 18 May 2026 05:55:53 +0000 (13:55 +0800)]
upstream-stable-release-point.bbclass: add bbclass for stable point upgrade
If a recipe can do stable version upgrade and the stable parts of the version
is seperated by '.', then it can inherit this bbclass.
By default, the stable parts number is 2, which means the following upgrades
are stable version upgrades:
x.y.z -> x.y.z+1
x.y.z+1 -> x.y.z+1.zz
x.y.z+1.zz -> x.y.z+2
Recipes that have different stable version parts can also inherit this bbclass
and set STABLE_VERSION_PARTS. For example, systemd sets this variable to "1".
For recipes whose stable version part is not separated by '.', they should not
inherit this bbclass and intead set UPSTREAM_STABLE_RELEASE_REGEX themselves.
For example, openssh's stable part is separted by 'p' and should not inherit
this bbclass.
Mark Hatle [Wed, 3 Jun 2026 21:57:39 +0000 (16:57 -0500)]
pseudo: Update to version 1.9.8
Changelog:
Makefile.in: Bump to 1.9.8
pseudo_client.h: Fix typo in the comment
client: permissions drop setuid and setgid
tests: Add setuid permission check
pseudo_client.h: Add +s to PSEUDO_DB_MODE for mkdir
tests: Add test that returned stat is correct
pseudo_client.h: Make it clear both macros must be updated together
Makefile.in: Add pseudo_client.h as a dependency
Signed-off-by: Mark Hatle <mark.hatle@kernel.crashing.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The package_tar class was removed in 90ce19122802
("meta/classes-global: remove package_tar.bbclass"), remove the deltask
for the nopackages class as well.
The package_tar.bbclass was removed in 90ce19122802
("meta/classes-global: remove package_tar.bbclass"), remove the
documentation variable associated with it as well.
Remove a [True, False] list evaluation that itself relied on evaluating
a boolean condition. Instead pass the boolean condition directly.
The previous version works because int(True)=1 and int(False)=0.
So:
=> pkg_type = Manifest.PKG_TYPE_ATTEMPT_ONLY
=> [False, True][pkg_type == Manifest.PKG_TYPE_ATTEMPT_ONLY]
=> [False, True][True]
=> [False, True][1]
=> True
The install_order instance variable was only ever set to
Manifest.INSTALL_ORDER, modified nowhere and used as is. Instead of
using an instance variable use Manifest.INSTALL_ORDER directly to
simplify the code for those reading it.
The install_order instance variable was only ever set to
Manifest.INSTALL_ORDER, modified nowhere and used as is. Instead of
using an instance variable use Manifest.INSTALL_ORDER directly to
simplify the code for those reading it.
Ross Burton [Mon, 1 Jun 2026 14:07:04 +0000 (15:07 +0100)]
curl: fix mbedtls detection
The mbedtls detection logic in curl is broken and resulted in build
paths leaking into curl-config and libcurl.pc. Backport a patch to fix
the detection by looking for a symbol that wasn't removed in mbedtls 3.0
five years ago, and remove the explicit sysroot reference as it is no
longer needed.
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>
oeqa/selftest: test_testimage_virgl_gtk_sdl: run only if gtk or sdl are enabled in base config
The test was forcibly enabling both gtk and sdl in qemu and then running the test.
This changes the logic to skip the test if neither is enabled,
and run gtk and/or sdl tests only if either is already enabled
in the base config that was in place before running the selftest.
Together with disabling sdl support in qemu by default this effectively
skips the test on the yocto autobuilder, resolving the selftest
failures seen with qemu 11.0.
Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
projects / thirdparty / openembedded / openembedded-core.git / log
