This test validates bitbake/default-registry/configurations/*.conf.json
against bitbake-setup.schema.json:
INFO - test_validate_bitbake_setup_default_registry (bblayers.BitbakeLayers.test_validate_bitbake_setup_default_registry)
DEBUG - Validating .../poky/bitbake/bin/../default-registry/configurations/oe-nodistro.conf.json
DEBUG - Validating .../poky/bitbake/bin/../default-registry/configurations/poky-master.conf.json
INFO - ... ok
INFO - test_validate_examplelayersjson (bblayers.BitbakeLayers.test_validate_examplelayersjson)
INFO - ... ok
INFO - ----------------------------------------------------------------------
INFO - Ran 2 tests in 110.469s
INFO - OK
INFO - RESULTS:
INFO - RESULTS - bblayers.BitbakeLayers.test_validate_bitbake_setup_default_registry: PASSED (0.92s)
INFO - RESULTS - bblayers.BitbakeLayers.test_validate_examplelayersjson: PASSED (0.19s)
INFO - SUMMARY:
INFO - oe-selftest () - Ran 2 tests in 110.469s
INFO - oe-selftest - OK - All required tests passed (successes=2, skipped=0, failures=0, errors=0)
(From OE-Core rev: 86978295c228640e2c33076d1f51db9f2fe7063b)
Signed-off-by: Yoann Congal <yoann.congal@smile.fr>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Extract a function "validate_json"
* Read bitbake variables in setUpClass to avoid makeing repeated calls
to bitbake
* Allow to specify the schema relative to $COREBASE/meta/files/
* Specify the Base URI to allow schema to reference each other
(From OE-Core rev: b10b4d5b6376fd828c1cb843ea2e24da298657b6)
Signed-off-by: Yoann Congal <yoann.congal@smile.fr>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This schema is a bit loose and should validate any configuration files working with
bitbake-setup but, also, some broken ones:
* If present, a "bb-layer" can be an empty array.
* bb-setup need at least one of "bb-layers" or "oe-template", that is
not enforced in the current schema.
* bb-setup accepts "configurations = []" but it results in a impossible
choice in interactive mode. This is rejected by the schema.
* In each configuration, "name" and "description" are optional but the
flatten configuration must have them. This is not enforced by the
schema.
To test a configuration files against this schema: (for exemple to
validate bitbake default registry)
$ pip install check-jsonschema
$ check-jsonschema -v --schemafile meta/files/bitbake-setup.schema.json bitbake/default-registry/configurations/*
ok -- validation done
The following files were checked:
bitbake/default-registry/configurations/oe-nodistro.conf.json
bitbake/default-registry/configurations/poky-master.conf.json
(From OE-Core rev: 15107ba12ff35b27c2c0ae5a9dcc9c1418f55b13)
Signed-off-by: Yoann Congal <yoann.congal@smile.fr>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Adding option to be able to import debugsources.zstd directly.
The linux-yocto-debugsources.zstd is generated in every build and
does not require any additional configuration.
In contrast, SPDX_INCLUDE_COMPILED_SOURCES needs to be explicitly
added and increases build time.
(From OE-Core rev: c84a8958f30bbb982656ddcbe7476f6f81e1a6fb)
Signed-off-by: Daniel Turull <daniel.turull@ericsson.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
https://github.com/libarchive/libarchive/releases/tag/v3.8.2
Libarchive 3.8.2 is a bugfix and security release.
Security fixes:
* 7zip: Fix out of boundary access (#2668)
* tar reader: fix checking the result of the strftime (#2719, CVE-2025-25724)
(From OE-Core rev: d858f87bc9baf4a01f977861c5521f2d5ffeb5fd)
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>
Brings following bugfixes on top of 21.1.3
222fc11f2b8f Bump version to 21.1.4
480a90482e5b release/21.x: [clang-format] Fix a crash on BAS_BlockIndent (#164047)
3333dd88a493 Update clang/lib/Format/TokenAnnotator.cpp
54cdd973782e [clang-format] Annotate ::operator and Foo::operator correctly (#164048)
ceeb93096c79 [libclang/python] Return None instead of null cursors from Token.cursor (#163183)
7e153f5372ed [clang-format] Fix an assertion failure on comment-only config files (#163111)
faca424bc5f7 [clang-format] Correctly handle backward compatibility of C headers (#159908)
c5a3aa8934b0 [libc++] Properly implement array cookies in the ARM ABI (#160182)
0d819a9104b2 [libunwind] Fix aarch64 SEH unwinding with a debugger attached (#162867)
464d75ad5f26 [MachinePipeliner] Add test missed in #154940 (NFC) (#163350)
ffa6b0c365ec [MachinePipeliner] Limit the number of stores in BB (#154940)
570c4c944338 [clang] Fix catching pointers by reference on mingw targets (#162546)
c6af6be3cd1c [libc++][docs] Add missing entry for P3379R0 to `21.rst`
a2e93dce5f2b [Hexagon][llvm-objdump] Start a fresh packet at symbol boundaries. (#163466)
dfdee9a929aa [clang][modules] Derive mtime from PCM timestamps, not PCM files (#162965)
bd9bc536b4ac [LLD] [COFF] Fix aarch64 delayimport of sret arguments (#163096)
7b785dcb70f6 [LLD][COFF] Fix tailMergeARM64 delayload thunk 128 MB range limitation (#161844)
a847f1832857 [Hexagon] Support lowering of setuo & seto for vector types in Hexagon (#158740)
e14b5e82244e [clang-format] Fix a bug in wrapping { after else (#161048)
b54051ac74cb [clang-format] Correctly annotate RequiresExpressionLBrace (#155773)
c9fbd571b52c dfsan: Fix test with gcc 15.
68f118f265c9 Switch dtls_test.c from XFAIL to UNSUPPORTED on aarch64.
a86b1e397e90 compiler-rt: Make the tests pass on AArch64 and with page size != 4096.
c03b58bb091e [clangd] Fix code action kind for readability-identifier-naming fixes (#162808)
caef7619d5fd [clang-format] Fix a bug in OneLineFormatOffRegex (#162961)
5386abc82ab8 [libc++][ranges] Fix `ranges::join_view` segmented iterator trait (#158347)
18593ab316f6 workflows/release-binaries: Run tests on the same runner as the build (#162421)
13bee3a798b1 [Mips] Fix clang crashes when assembling invalid MIPS beql instructions with --arch=mips (#156413)
0d1b9249d189 [CI] Add dyung and c-rhodes to the Release Asset List (#162478)
c000f3226bdf [Mips] Fixed libunwind::Registers_mips_o32::jumpto to allow for load delay (#152942)
276050887539 [LLDB][ProcessWindows] Set exit status on instance rather than going through all targets (#159308)
(From OE-Core rev: 343b2e113322859c6c3021215acc498a94b69a0b)
Signed-off-by: Deepesh Varatharajan <Deepesh.Varatharajan@windriver.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
When deploying on devices with a RO root-filesystem, devtool would
fail on writing to the hard-coded "deploylist_path = '/.devtool'"
Since devtool already supports deploying to a different root-prefix
with: hostname[:destdir], we can make use of this guaranteed RW
location to place the deployment-list there.
Add the destdir parameter to the _prepare_remote_script function, to
construct the deploylist_path from it. For the 'undeploy' the same
host:destdir splitting logic is used as in 'deploy'.
Now it is possible to modify and build a recipe 'foo-bar' with
devtool, and have its ./image content deployed through:
$build> devtool deploy foo-bar target:/opt/development-overlay
Or removed again with:
$build> devtool undeploy foo-bar target:/opt/development-overlay
(From OE-Core rev: 216a4c4a4ee58222127c830ac56126bdbb95308d)
Signed-off-by: Johannes Schneider <johannes.schneider@leica-geosystems.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Tear down method is executed even when the tests are disabled. This lead
to SSH being used to run commands on the target, and as it might fail
when no SSH server is present, we had to use ignore_ssh_fails=True here.
Instead, remove log file just before it is created: it will remain on
the target after the test is run, but this should be acceptable.
(From OE-Core rev: 8b119b1a0fa618c03fbee1bcc755785fedd2d923)
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Setup and tear down methods are executed even when the tests are disabled.
This lead to SSH being used to run commands on the target, and as it
might fail when no SSH server is present, we had to use
ignore_ssh_fails=True here.
Instead, run cleanup tasks in tests themselves and remove the tear down
method.
Also, the wtmp configuration file is not modified since the test was
modified a few years ago: there is no need to backup and restore it.
(From OE-Core rev: c90f79ae221573b2d5100f2d25b12f77e33113d7)
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
If the SYSTEMD_SERVICE variable contains a template instance that has
dots in the name such as "xyz.openbmc_project.my@instance.service", the
regex splits on all the dots resulting in the following python
exception:
Exception: ValueError: too many values to unpack (expected 3)
To continue to support service files with dots in the name, this changes
to first split only on the '@' to isolate the name, then split the
second half on the last dot to get the remaining two parameters.
Splitting on the last dot allows dots in the instance name, as well.
Confirmed when building that the three parameters for template instances
without dots came out the same and that template instances with dots
include the full name with dots in the first parameter.
Confirmed when using an instance name with dots that the full instance
name came out correctly with dots.
CC: Ross Burton <Ross.Burton@arm.com>
(From OE-Core rev: 09a37ecf0aeff674e49d7bddd5421011a885da2e)
Signed-off-by: Jason M. Bills <jason.m.bills@linux.intel.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Upgrade the firmware package, add new package for Intel Sensor Hub on
Pather Lake platforms.
License-Update: new and updated firmware
(From OE-Core rev: d7bb55ef931f1c36fd3adc4989e8c7324bd08771)
Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
If we have changes on SPDX_LICENSES content we ended up building invalid sstate-cache archives.
The default value for the SPDX_LICENSES is the file meta/files/spdx-licenses.json but this file
don't use the bitbake fetcher and because of this their checksum is not validated.
So we need to add this file to the build dependency chain of the SPDX.
For example, currently we have bump from 3.24.0 to 3.27.0 on master-next for the file
meta/files/spdx-licenses.json. Since the file content is not taken into account, we end
up creating invalid sstate-cache artifacts on the autobuilder on master-next builds.
This created sstate-cache artifacts will also be available to master branch users
that are using the upstream sstate-cache mirror.
If someone is using the public mirror but still following the master branch
they will encounter something like the following error which this change aims to resolve.
| ERROR: initramfs-rootfs-image-1.0-r0 do_create_image_sbom_spdx: http://spdxdocs.org/openembedded-alias/by-doc-hash/57301e8063a8bf25308226271627db2b78675cda9f648c5c6c14a2b9c18f48dc/zlib/UNIHASH/license/3_27_0/Zlib not found in /work/build/tmp/deploy/spdx/3.0.1/armv8a/by-spdxid-hash/57/57301e8063a8bf25308226271627db2b78675cda9f648c5c6c14a2b9c18f48dc.spdx.json
(From OE-Core rev: 10669f6f615058293671fb16454601580b7b34e9)
Signed-off-by: Jose Quaresma <jose.quaresma@oss.qualcomm.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
We can have more files types in the chain of dependencies and not just libs.
(From OE-Core rev: f400ba75f2d7987abb177a43f94874a7fdc1ec0a)
Signed-off-by: Jose Quaresma <jose.quaresma@oss.qualcomm.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
GCC is not buildable with clang and when using clang
for native compiler this fails to build native parts
(From OE-Core rev: 38825ed9e8f24a2ae31df377f7f3c971bc617a19)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This ensures that, native pieces in target builds
are build with correct flags to be able to run on build host
(From OE-Core rev: c82e49d1707f2057baa3f7fbaeea0b785712a11f)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
No need to edit rpaths in llvm-config, this is not
needed anymore because the llvm-config used is from
standard install inside sysroot unlike when rust-llvm
was used, where it was installed into its own location
to avoid conflicts with llvm-config coming from llvm/clang
(From OE-Core rev: c91addea22c7e857e583a89d4597f6e676210e6b)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Cc: Deepesh Varatharajan <Deepesh.Varatharajan@windriver.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
According to https://www.gtk.org/docs/installations/linux/#gtk-v3x the new
place for downloads is download.gnome.org aka $GNOME_MIRROR (ftp.g.o
redirects to this). And new versions are without `+`.
Update opengl.patch, handle new `is_gl_context_current`.
Overview of Changes in GTK+ 3.24.51, 29-09-2025
===============================================
* Wayland:
- Force window titles to be valid utf8
- Flush tablet events when neccessary
* X11:
- Avoid a use-after-free with threads
* Windows:
- Avoid min/max buttons for dialogs
* Images:
- Replace a few calls to gdk_pixbuf_get_pixels
with read_pixels to avoid thread-safety issues
* GL:
- Try harder to keep the GL context current
* Input:
- Make compose file parsing more robust
* Translation updates:
Catalan
Esperanto
Persian
Overview of Changes in GTK+ 3.24.50, 07-08-2025
===============================================
* Themes:
- Add a progress-working-symbolic icon
- Support strokes in symbolic icons
- Update theme CSS
- Remove hardcoded Cantarell font
* GtkShortcutsWindow:
- Differentiate all keypad symbols visually
* GtkApplication:
- Register unsandboxed apps with the portals
* macOS:
- Remove redundant NSView calls
- Fix some memory leaks
- Don't try to use the file transfer portal
* Windows:
- Always mark windows as minimizable
* X11
- Fix problems with gtk_window_get_geometry
* Wayland:
- Fix a crash
* Input:
- Make compose sequence visuals configurable
* Printing:
- Fix the build with libcups 3
- Support gnome-papers as previewer
* Translation updates
Nepali
Persian
Uzbek (Latin)
Overview of Changes in GTK+ 3.24.49, 05-03-2025
===============================================
* Fix a crash in GtkIMContext
* Fix crashes in DND with GtkPlug/GtkSocket
* Wayland:
- Fix erroneous crossing events, causing menus to malfunction
- Support the cursor-shape protocol
* X11:
- Enforce size limits on windows, preventing lockups
* macOS:
- Fix pen tilt handling
* Translation updates
Bulgarian
Thai
Overview of Changes in GTK+ 3.24.48, 25-02-2025
===============================================
* Switch to the new ci-based release process
Overview of Changes in GTK+ 3.24.44, 24-01-2025
===============================================
* GtkFileChooser:
- Stop replacing : (colon) with U+2236 (ratio)
* GtkEmojiChooser:
- Update to Unicode 16 / CLDR 46
* GtkSpinButton:
- Use semantically appropriate icon names
- Make numeric spin buttons always LTR
* GtkEntry:
- Stop guessing text direction from keyboard layout
- Add a shortcut and context menu item to change text direction
* GtkEventControllerMotion:
- Make enter and leave signals work
* Accessibility:
- Use message dialog titles as names
* GDK:
- Fix portal handling of gvfs files
* Wayland:
- Support the xdg_foreign_v2 protocol
- Try to fix monitor geometry on sway
- Improve font setting fallback
- Use a better default cursor size
- Fix a crash during DND
* macOS:
- Fix a UI hang
* Translation updates:
Bulgarian
Farsi
Hindi
Hungarian
Icelandic
Latvian
Serbian
(From OE-Core rev: 7f370c3b9c10e723324ea8f924011c5f570749d4)
Signed-off-by: Jörg Sommer <joerg.sommer@navimatix.de>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This adds a feature to specify the disk ID when creating a disk with
the wic tool. This is useful when using the DOS partition scheme and
booting with root=PARTUUID=<partuuid>. In DOS partitions, the partition
ID is <diskid>-<partition-number>, so it makes sense to let the user
define the disk ID.
You can specify it in the kickstart file using the --diskid argument
to the bootloader command. The value can be given in decimal or
hexadecimal format (e.g. 3735928559 or 0xdeadbeef). If omitted, the
previous behaviour does not change.
(From OE-Core rev: a31453fd52e0a52f3fa02cb9ae0878ea3782c2b7)
Signed-off-by: Steffen Greber <sgreber@lilafast.org>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Pick commit per NVD CVE report.
Note that there were two patches for this, first [1] and then [2].
The second patch moved the original patch to different location.
Cherry-pick of second patch is successful leaving out the code removing
the code from first location, so the patch attached here is not
identical to the upstream commit but is identical to applying both and
merging them to a single patch.
[1] https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=1108620d7a521f1c85d2f629031ce0fbae14e331
[2] https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=72efdf166aa0ed72ecc69fc2349af6591a7a19c0
(From OE-Core rev: 98df728e6136d04af0f4922b7ffbeffb704de395)
Signed-off-by: Peter Marko <peter.marko@siemens.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
See release notes at
- http://downloads.yoctoproject.org/releases/opkg/opkg-0.8.0.release-notes
[0.8.0] - 2025-01-10
The minor version bump in this release is due to the changes to cURL error output line format.
- [Changed](https://git.yoctoproject.org/opkg/commit/?id=ab03377868256427279b36c4b2a298edae4260b8) the error output for the curl download backend, to now report the HTTP error code for failed requests.
- e.g. `error: log_curl_download_error: Failed to download headers of https://foo.bar/all/Packages.gz: The requested URL returned error: 401`
- Enabling debug-verbosity, while using the cURL backend, [will now](https://git.yoctoproject.org/opkg/commit/?id=ce6fede3db931bb0da70d1334cdc4101d0aec702) print cURL's verbose error log to stderr when there is a download failure.
- The verbose output may contain confidential information about your cURL transactions. So this is your reminder that debug-verbosity should not be enabled in production systems or sensitive security environments.
- The commandline configuration file option (`-f`) [can now](https://git.yoctoproject.org/opkg/commit/?id=36d08b93d2859992b624a4ba2f412cfa5c766050) be specified multiple times, and each configuration file will be loaded and their settings merged.
- [Fixed](https://git.yoctoproject.org/opkg/commit/?id=c87188d7535684fddb8cf80993c147b215602b63) a bug in control field parsing where custom fields whose keys are similar to other fields could be confused by the parser.
(From OE-Core rev: ff78c4c4453643c24494fa872a58e424b9772f9c)
Signed-off-by: Etienne Cordonnier <ecordonnier@snap.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
When building an entire multilib image (e.g. lib32-core-image-minimal)
we need to ensure that the unneeded packages in ROOTFS_RO_UNNEEDED get
the multilib prefix applied before they are compared against the list of
installed packages inside Rootfs._uninstall_unneeded() to decide whether
they need to be installed.
Before this change with local.conf containing:
MACHINE = qemuarm64
require conf/multilib.conf
MULTILIBS = "multilib:lib32"
DEFAULTTUNE:virtclass-multilib-lib32 = "armv7at-neon"
IMAGE_FEATURES = "read-only-rootfs"
running:
bitbake lib32-core-image-minimal
tar tavf tmp/deploy/images/qemuarm64/lib32-core-image-minimal-qemuarm64.rootfs.tar.zst|grep postinst
shows three files:
-rwxr-xr-x 0/0 25 2018-03-09 12:34 ./etc/init.d/run-postinsts
lrwxrwxrwx 0/0 0 2018-03-09 12:34 ./etc/rcS.d/S99run-postinsts -> ../init.d/run-postinsts
-rwxr-xr-x 0/0 2153 2018-03-09 12:34 ./usr/sbin/run-postinsts
whereas with this change there are no matching files.
(From OE-Core rev: 77c35362fb13c75145f9f999216b3d879ab18b77)
Signed-off-by: Mike Crowe <mac@mcrowe.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Right now all signing is done with a single variable: UBOOT_SIGN_ENABLE.
This has the side effect of not allowing for signing the fitImage while
not signing the uboot files.
This patch creates three new variables specific to FIT_KERNEL and
defaults them to the corresponding UBOOT variables. That way all
existing code will remain the same, but we can selectively control just
signing the fitImage without also signing the uboot files.
(From OE-Core rev: 313ff06fdfec36a09328dbd60471bd53127fabe3)
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #15909]
SPDX validation was failing due to the use of `crate://crates.io/...` as the
`downloadLocation`, which is not a valid SPDX URL as per the 2.2 specification.
This patch updates `fetch_data_to_uri()` in `spdx_common.py` to detect when the
fetcher type is "crate" and instead use the `url` attribute, which contains a
valid HTTP(S) URL in the expected format, e.g.:
https://crates.io/api/v1/crates/<name>/<version>/download
This aligns the SPDX metadata for Rust crates with the specification and avoids
validation errors in tools consuming SPDX documents.
Tested with the `python3-bcrypt` recipe and verified that the
generated `spdx.json` contains a valid `software_downloadLocation`.
Reference: https://bugzilla.yoctoproject.org/show_bug.cgi?id=15909
(From OE-Core rev: 7cadbd1a22e18847d03b5baa902f5581d3e0aafa)
Signed-off-by: Jayasurya Maganuru <Maganuru.Jayasurya@Windriver.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The default installation umask is 0027 for Kea-built artifacts.
And it caused package conflicts as following:
Error: Transaction test error:
file /usr/lib/pkgconfig conflicts between attempted installs of kea-dev-3.0.1-r0.x86_64_v3 and btrfs-tools-dev-6.16-r0.x86_64_v3
file /usr/lib/pkgconfig conflicts between attempted installs of libgcrypt-dev-1.11.2-r0.x86_64_v3 and kea-dev-3.0.1-r0.x86_64_v3
I submitted an issue to the upstream and found upstream alreadly known this issue.
https://gitlab.isc.org/isc-projects/kea/-/issues/4171https://gitlab.isc.org/isc-projects/kea/-/issues/3993
Then I follow the method in the SPEC file of upstream to fix this problem in Yocto.
https://gitlab.isc.org/isc-projects/kea-packaging/-/blob/master/rpm/kea.spec?ref_type=heads
meson setup build \
--buildtype release \
--install-umask 0022 \
--bindir %{_bindir} \
(From OE-Core rev: 0294c265a1f662e2b68b3a462da113cfa835485b)
Signed-off-by: Liu Yiding <liuyd.fnst@fujitsu.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
After kea has been upgrade to 3.0.1,the build system changed to meson,but the config of build system is still be EXTRA_OECONF. So this commit fix it.
(From OE-Core rev: df3f4196693ae82bddebe134f3af0db92e5d5712)
Signed-off-by: Liu Yiding <liuyd.fnst@fujitsu.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The last enrty of req_its_fields was not taken into account and the test
passed even if the last entry was not found in the its file.
(From OE-Core rev: 34e872ab23067231fb93c3b31ad5a439e9c17cb8)
Signed-off-by: Adrian Freihofer <adrian.freihofer@siemens.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Reproducibility looks OK.
ptests look OK:
|============================================================================
|Testsuite summary
|# TOTAL: 48977
|# PASS: 46513
|# SKIP: 2426
|# XFAIL: 33
|# FAIL: 0
|# XPASS: 5
|# ERROR: 0
|DURATION: 119
|END: /usr/lib/python3-numpy/ptest
|2025-10-19T16:03
|STOP: ptest-runner
|TOTAL: 1 FAIL: 0
Release notes (https://github.com/numpy/numpy/releases/tag/v2.3.4):
The NumPy 2.3.4 release is a patch release split between a number of maintenance
updates and bug fixes. This release supports Python versions 3.11-3.14. This
release is based on Python 3.14.0 final.
Changes
- The npymath and npyrandom libraries now have a .lib rather than a .a
file extension on win-arm64, for compatibility for building with MSVC
and setuptools. Please note that using these static libraries is
discouraged and for existing projects using it, it's best to use it
with a matching compiler toolchain, which is clang-cl on Windows on
Arm.
(From OE-Core rev: 4e8d533ccecf1310218ad5d36a7ec20ee5e0ccd4)
Signed-off-by: Trevor Gamblin <tgamblin@baylibre.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
base-files already provides /var/lock as a symbolic link to /run/lock, and
since /run is created and mounted as tmpfs during init, there is no need
to explicitly create /var/lock within initramfs.
This avoids the following spurious error during boot:
mkdir: can't create directory '/var/lock': No such file or directory
(From OE-Core rev: 24629a0e81291900edf0967bb218ba51dfa90ce9)
Signed-off-by: Ricardo Salveti <ricardo@foundries.io>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Upgrade to latest 1.25.x release [1]:
$ git --no-pager log --oneline go1.25.2..go1.25.3
28622c1959 (tag: go1.25.3) [release-branch.go1.25] go1.25.3
e05b2c92d9 [release-branch.go1.25] crypto/x509: rework fix for CVE-2025-58187
79ec0c94f3 [release-branch.go1.25] spec: update spec date to match release date
This release addresses breakage caused by a security patch included in Go 1.25.2
and 1.24.8, which enforced overly restrictive validation on the parsing of X.509
certificates. We've removed those restrictions while maintaining the security
fix that the initial release addressed [2].
[1] https://github.com/golang/go/compare/go1.25.2...go1.25.3
[2] https://groups.google.com/g/golang-announce/c/YEyj6FUNbik
(From OE-Core rev: d5f281bf13995117d98af809a2caea91e241713e)
Signed-off-by: Peter Marko <peter.marko@siemens.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fix following conflicts when enabling multilib.
Error: Transaction test error:
file /usr/include/llvm/Config/llvm-config.h conflicts between attempted installs of lib32-llvm-dev-21.1.3-r1.core2_32 and llvm-dev-21.1.3-r1.x86_64_v3
(From OE-Core rev: 886b0fb60a0b2ebbe3186c790db6e0a41eeb8741)
Signed-off-by: Liu Yiding <liuyd.fnst@fujitsu.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Drop upstreamed patch and refresh remaining patches.
Release information:
* https://www.python.org/downloads/release/python-3138/
* 3.13.8 is the eighth maintenance release of 3.13, containing around
200 bugfixes, build improvements and documentation changes since
3.13.7.
* https://www.python.org/downloads/release/python-3139/
* This Python 3.13.9, a maintenance release for Python 3.13.
* 3.13.9 is an expedited release containing a fix for one specific
regression in Python 3.13.8
(From OE-Core rev: 78d83ced968a46579cff8bfa0b4f462689c46c00)
Signed-off-by: Peter Marko <peter.marko@siemens.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
See https://docs.mesa3d.org/relnotes/25.2.5.html.
0001-glx-provide-glx.pc.patch is in 25.2.5 via commit 293a26135d83
("glx: provide glx.pc") so can be dropped.
(From OE-Core rev: 33498005ff8099b743efaf1ae431ba1a0ba597a0)
Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Dropped fix-armv7-compilation.patch, because it is included in this
release.
Dropped no-musttail-arm.patch, because it has been solved by project
(a bit differently)[1]
Added a new backported patch, fix-musl-compilation.patch
to avoid build error when compiling with musl libc:
.../Source/bmalloc/libpas/src/libpas/pas_probabilistic_guard_malloc_allocator.c:52:10: fatal error: execinfo.h: No such file or directory
| 52 | #include <execinfo.h>
| | ^~~~~~~~~~~~
Another patch, fix_op_instanceof_handler_for_32-bit_C-loop_build.patch is under review by
upstream. It fixes compiling for 32-bit targets by fixing the following error:
error: label 'op_instanceof_return_location' used but not defined
[1]: https://github.com/WebKit/WebKit/blob/webkitgtk-2.50.0/Source/WTF/wtf/Compiler.h#L280
Changelog:
2.50.0:
- Fix rendering with software rasterization enabled.
- Fix WebAudio issues after idling for a minute.
- Fix several crashes and rendering issues.
2.49.90:
- Add support for font collection / fragment identifiers.
- Fix web process deadlock on exit.
- Fix stuttering when playing WebP animations
- Fix CSS animations with cubic-bezier timing function.
- Do not start the MemoryPressureMonitor if it's disabled
- Translation updates: Polish, Slovenian.
- Fix several crashes and rendering issues.
2.49.4:
- Enable CSS property font-variant-emoji is now enabled by default.
- Improve emoji font selection.
- Add SVT-AV1 encoder support to media backend.
- Show device scale factor in webkit://gpu.
- Fix font rendering of composed characters with certain fonts.
- Fix handling of font synthesis properties (bold/italic).
- Fix documentation of WebKitDeviceInfoPermissionRequest.
- Fix several crashes and rendering issues.
2.49.3:
- Add new API to get the theme color of a WebKitWebView.
- Fix rendering with GTK 3.
- Notify automation session on abnormal disconnections.
- Fix a crash by ensuring SkiaRecordingResult is destroyed on the main thread.
- Fix build on s390x.
- Fix the build with GTK 3.
- Fix several crashes and rendering issues.
2.49.2:
- Enable damage propagation to the UI process by default.
- Pass available input devices from UI process to web process for Interaction Media Features.
- Always have a fallback when domain does not have known base.
- Fix URL after HSTS upgrade in case of redirection.
- Fix rendering when device scale factor change comes before the web view geometry update.
- Ensure web view is focused on tap gesture.
- Fix a crash when setting WEBKIT_SKIA_GPU_PAINTING_THREADS=0.
- Fix several crashes and rendering issues.
- Translation updates: Brazilian Portuguese, Swedish.
2.49.1:
- Change threaded rendering implementation to use Skia API instead of WebCore display
list that is not thread safe. This also allowed to improve performance by recording
layers once and replaying every dirty region in different worker threads.
- Added hybrid rendering mode that tries to use the GPU worker threads, but if they
are all busy the CPU worker threads are used if possible.
- Add volume locking support to media player.
- Add support for tracing counters with Sysprof.
- Fix several crashes and rendering issues.
(From OE-Core rev: 4caf886da6c9d74298aab0b953c0540dc2f49942)
Signed-off-by: Gyorgy Sarvari <skandigraun@gmail.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
There are conflict of config files between kea and lib32-kea:
| Error: Transaction test error:
| file /etc/kea/kea-dhcp4.conf conflicts between attempted installs of lib32-kea-3.0.1-r0.core2_32 and kea-3.0.1-r0.x86_64_v3
| file /etc/kea/kea-dhcp6.conf conflicts between attempted installs of lib32-kea-3.0.1-r0.core2_32 and kea-3.0.1-r0.x86_64_v3
Update this patch after kea was upgraded to 3.0.1.
(From OE-Core rev: 5318fba1f4bc50e658aee9461cc919ab093a8293)
Signed-off-by: Liu Yiding <liuyd.fnst@fujitsu.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Change the build-appliance image to include current git trees of the
separate bitbake/openembedded-core/meta-yocto repositories, instead of
the merged poky repository as that is being discontinued.
[ YOCTO #16002 ]
(From OE-Core rev: 501e78ea84979d175f5e6b7978c669f3f80a4355)
(From OE-Core rev: 57dbe13f87cc2cfc87ed12dcca12382ba710be94)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
If compression is used, a lot of compressed firmware files are
not packaged otherwise.
(From OE-Core rev: 8695d01a47490d48103e9f292e1ea3ee4753d98e)
(From OE-Core rev: d3315badb8bf4bc9c32ba13bb31febb6aea3cfe7)
Signed-off-by: Zoltán Böszörményi <zboszor@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
If FIRMWARE_COMPRESSION is set, the newly added code to remove
unlicensed firmware fails with:
| Remove unlicensed firmware: acenic/tg1.bin
| rm: cannot remove '.../work/all-oe-linux/linux-firmware/20250917/image/usr/lib/firmware/acenic/tg1.bin': No such file or directory
This is because the code does not consider that the file may be
compressed.
Fix it by factoring out the code to construct the compressed file
name suffix from do_install:append() into a python function and
also use it for the actual file names listed in REMOVE_UNLICENSED.
(From OE-Core rev: 79fc52e2d729bf30a901055a9864280d3055bbeb)
(From OE-Core rev: ecfb4494a9bc23cb1b1532cff32d67d4384ded3e)
Signed-off-by: Zoltán Böszörményi <zboszor@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The cargo class defaults to out-of-tree builds in WORKDIR/build, but
at no point was that directory cleaned. This causes problems with the
rust standard library recipe (libstd-rs) which installs manually with cp,
so rebuilds can be contaminated with the contents of previous builds.
I believe that post-release we should switch cargo.bbclass to mandating
out-of-tree builds to reduce the complexity, but for now in out-of-tree
builds we can just delete the ${B}/target directory.
Note that we use ${B}/target because there at least were reasons to use
that name[1], it is unclear if these limitations still hold. We can't
simply clean ${B} because that will break recipes that use cargo and
something else to build, for example librsvg.
[1] https://github.com/rust-lang/cargo/pull/1657
(From OE-Core rev: 1452ac7a44196454a52f3f6d883290ddcccfd3f8)
(From OE-Core rev: 9d9ce457630ea7403ffe7028e3370647db0b83fa)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Use the SMAIL-GPL license name, as that is the official SPDX name and we
now have it in our license list.
This means we can delete the SMAIL_GPL license, that appears to be only
used by debianutils and nobody else.
(From OE-Core rev: a8b0d3bc7b073cc0e9e8a735df6d36a4816520dc)
(From OE-Core rev: af771279f3ef8aa2ba137e018da8fc6bf6a1b335)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Use scripts/pull-sdpx-licenses.py to refresh the license list and add
any new licenses that we previously did not have license texts for.
(From OE-Core rev: 560acb29d9f9d3a66223122e2cbca7a24a80f209)
(From OE-Core rev: f9903f74ee36de4dd592f3bc8b1ce7b08f32608c)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The cargo class already sets this, so there's no need to set it again.
The value set by cargo.bbclass is actually ${B}/target, so update the
do_install task to match.
(From OE-Core rev: 3557f1c294531e7f8c34a2b0677e8c03f1b1be77)
(From OE-Core rev: ec51c22e902c2556438f1323a71a5e47ef00681e)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Bumping the -dev kernel to 6.18+
(From OE-Core rev: 7a900ff52d76490f42236f9dd898ded0da77058e)
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
commit f589e1df23251d8319063da0a61c1016b2a0bf85 (HEAD -> master)
Author: Bruce Ashfield <bruce.ashfield@gmail.com>
Date: Wed Oct 15 18:12:20 2025 -0400
tools/Kconfiglib: add support for transitional attribute
We need to update the parser to handle:
commit f9afce4f32e9a120fc902fa6c9e0b90ad799a6ec
Author: Kees Cook <kees@kernel.org>
Date: Tue Sep 23 14:34:18 2025 -0700
kconfig: Add transitional symbol attribute for migration support
During kernel option migrations (e.g. CONFIG_CFI_CLANG to CONFIG_CFI),
existing .config files need to maintain backward compatibility while
preventing deprecated options from appearing in newly generated
configurations. This is challenging with existing Kconfig mechanisms
because:
1. Simply removing old options breaks existing .config files.
2. Manually listing an option as "deprecated" leaves it needlessly
visible and still writes them to new .config files.
3. Using any method to remove visibility (.e.g no 'prompt', 'if n',
etc) prevents the option from being processed at all.
Add a "transitional" attribute that creates symbols which are:
- Processed during configuration (can influence other symbols' defaults)
- Hidden from user menus (no prompts appear)
- Omitted from newly written .config files (gets migrated)
- Restricted to only having help sections (no defaults, selects, etc)
making it truly just a "prior value pass-through" option.
The transitional syntax requires a type argument and prevents type
redefinition:
config NEW_OPTION
bool "New option"
default OLD_OPTION
config OLD_OPTION
bool
transitional
help
Transitional config for OLD_OPTION migration.
This allows seamless migration: olddefconfig processes existing
CONFIG_OLD_OPTION=y settings to enable CONFIG_NEW_OPTION=y, while
CONFIG_OLD_OPTION is omitted from newly generated .config files.
Added positive and negative testing via "testconfig" make target.
Co-developed-by: Vegard Nossum <vegard.nossum@oracle.com>
Signed-off-by: Vegard Nossum <vegard.nossum@oracle.com>
Reviewed-by: Nathan Chancellor <nathan@kernel.org>
Tested-by: Nathan Chancellor <nathan@kernel.org>
Link: https://lore.kernel.org/r/20250923213422.1105654-2-kees@kernel.org
Signed-off-by: Kees Cook <kees@kernel.org>
(From OE-Core rev: 8306d2bdcc48718aaa35dfa56b5364d90ea2a1db)
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
