Yocto Blacksail released, Bootlin contributions inside

Yocto ProjectYocto Blacksail 6.1 is now released. This is the new stable release of the Yocto Project and will be maintained until April 2027. Bootlin is a very active contributor to the Yocto Project, most notably with Antonin Godard being the official Yocto Project documentation maintainer, and Mathieu Dubois-Briand being a core member of the Yocto SWAT team, but also with other Bootlin engineers who use and deploy Yocto to create optimized and long-term maintainable Linux systems for the embedded devices of our customers. This 6.1 release was no exception, and we were again very active in this release cycle, with over 200 commits authored by Bootlin engineers.

Looking at our contributions more closely, the main areas of work have been:

  • On openembedded-core, the core layer of the Yocto Project:
    • Antonin Godard updated Sphinx-related Python recipes, improved the built-in configuration fragments (harmonizing their descriptions and adding a disk-space monitoring fragment), and fixed several issues in the oe-depends-dot script. He also removed references to inactive sources.openembedded.org mirror URLs.
    • Benjamin Robin continued maintaining the sbom-cve-check recipes and vulnerability databases, enabling offline operation and excluding the database recipes from rm_work. He also simplified the SPDX source handling, fixed package debug source information, improved sstate-cache-management, and backported fixes for CVEs affecting glib-2.0 and python3.
    • João Marcos Costa cleaned up the U-Boot tools recipes, added and fixed Clang/LLVM toolchain support (including for OVMF and WebKitGTK on ARM), disabled problematic ptests on RISC-V, and simplified various recipe and class constructs using bb.utils.filter.
    • Mathieu Dubois-Briand carried out a large number of recipe upgrades covering GStreamer, Python, Go, CMake and many other components. He also fixed devtool workflows and added selftest coverage, improved QA checks related to hardcoded home paths, imported and fixed the libfaketime recipe, added fake-time support to reproducibility tests, and removed the obsolete libclc recipe.
    • Thomas Perrot fixed issues in build scripts and oe-pkgdata-util, corrected a typo in the CVE check mapping configuration, and upgraded the OpenSBI recipe to version 1.9.
  • On bitbake, the core task scheduler of the Yocto Project:
    • Antonin Godard made various documentation improvements, enhanced the setversions.py tooling, updated the instructions for installing bitbake-setup, and enabled the new disk-space monitoring fragment in the default registry.
    • João Marcos Costa fixed an unbound variable issue in the layer index REST API client.
    • Thomas Perrot improved the Crate fetcher, notably by skipping yanked versions and reworking URL dispatch, and re-enabled the npm and npmsw fetchers with restored and extended test coverage.
  • On yocto-docs, the official Yocto Project documentation:
    • Antonin Godard was active in his role of documentation maintainer, with a large number of changes: this included writing the 6.0 and 6.1 release notes and migration guides, documenting the removal of cve-check and the new SBOM CVE checking features, documenting new variables and classes, refreshing the WIC documentation, adding shared-state mirror and shared-state signing documentation, fixing broken links, converting diagrams to SVG, and updating the list of supported distributions.
  • On meta-openembedded, a community set of layers supporting many kinds of software packages:
    • João Marcos Costa fixed a build-path QA issue in the bpftrace recipe.
    • Kory Maincent changed the libspdm recipe to skip unsupported architectures instead of failing.
    • Thomas Bonnefille added support for a command-line property in the fitimage class.
  • On meta-yocto, the layer providing the Poky reference distribution, Mathieu Dubois-Briand updated the list of distributions tested by the sanity checks, removing Fedora 42 and refreshing the supported entries.

Below is a detailed breakdown of individual contributions:

 

Leave a Reply