[yocto-docs PATCH 00/14] Updates from recent core changes

[yocto-docs PATCH 00/14] Updates from recent core changes

[Antonin Godard]

This series updates the documentation for the changes applied to master
in openembedded-core, bitbake, meta-poky and the docs itself.

First part of the series are documentation updates (new/removed
features), while the last commit update the release note/migration
guide only.

Precisely, this represents changes between 8149e74258 and 87d7341465 in
poky.

Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
---
Antonin Godard (14):
      ref-manual/variables: document the KERNEL_CONSOLE variable
      ref-manual/classes: drop the migrate_localcount class
      ref-manual/variables: document the FIRMWARE_COMPRESSION variable
      ref-manual/variables: add missing entries to SDK_ARCHIVE_TYPE
      ref-manual/variables: document the WIC_SECTOR_SIZE variable
      ref-manual/variable: remove obsolete SETUPTOOLS_INSTALL_ARGS
      ref-manual/classes: document the cython class
      Remove debug-tweaks references
      Drop support for BB_DANGLINGAPPENDS_WARNONLY
      ref-manual/variables: document the CHECKLAYER_REQUIRED_TESTS variable
      ref-manual/classes: document the yocto-check-layer class
      ref-manual/variables: document the CARGO_INSTALL_LIBRARIES variable
      ref-manual/variables: document the PREFERRED_RPROVIDER variable
      migration-guides: update the release notes for 5.2

 documentation/dev-manual/build-quality.rst         |   2 +-
 documentation/dev-manual/customizing-images.rst    |   3 +-
 documentation/dev-manual/layers.rst                |  15 +-
 documentation/dev-manual/securing-images.rst       |  12 +-
 documentation/migration-guides/migration-5.2.rst   |  50 +++
 .../migration-guides/release-notes-5.2.rst         | 345 ++++++++++++++++++++-
 documentation/profile-manual/intro.rst             |   4 +-
 documentation/profile-manual/usage.rst             |   2 +-
 documentation/ref-manual/classes.rst               |  39 ++-
 documentation/ref-manual/features.rst              |  19 +-
 documentation/ref-manual/variables.rst             |  94 ++++--
 documentation/sdk-manual/extensible.rst            |   5 +-
 12 files changed, 522 insertions(+), 68 deletions(-)
---
base-commit: 02c090718ac602f7d4760dd28dadbf0631668d49
change-id: 20241211-release-note-5-2-updates-015cdcfbb7d8

Best regards,
-- 
Antonin Godard <antonin.godard@bootlin.com>

[yocto-docs PATCH 01/14] ref-manual/variables: document the KERNEL_CONSOLE variable

[Antonin Godard]

This variables holds the value of the `console` kernel command line
parameter.

Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
---
 documentation/ref-manual/variables.rst | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/documentation/ref-manual/variables.rst b/documentation/ref-manual/variables.rst
index 1eee617d59ccddc9af0ffb95ea3635a707718152..c6d3d1bba9961704fca25921b346d5282e118db4 100644
--- a/documentation/ref-manual/variables.rst
+++ b/documentation/ref-manual/variables.rst
@@ -4579,6 +4579,12 @@ system and gives an overview of their function and contents.
       You can register custom kernel image types with the
       :ref:`ref-classes-kernel` class using this variable.
 
+   :term:`KERNEL_CONSOLE`
+     The :term:`KERNEL_CONSOLE` variable holds the value of the ``console``
+     parameter of the kernel command line and can be used in places such as a
+     ``wks`` description file for :ref:`Wic images <dev-manual/wic:creating
+     partitioned images using wic>`.
+
    :term:`KERNEL_DANGLING_FEATURES_WARN_ONLY`
       When kernel configuration fragments are missing for some
       :term:`KERNEL_FEATURES` specified by layers or BSPs,

-- 
2.47.1

Re: [docs] [yocto-docs PATCH 01/14] ref-manual/variables: document the KERNEL_CONSOLE variable

[Quentin Schulz]

Hi Antonin,

On 12/17/24 10:27 AM, Antonin Godard via lists.yoctoproject.org wrote:
> This variables holds the value of the `console` kernel command line
> parameter.
> 
> Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
> ---
>   documentation/ref-manual/variables.rst | 6 ++++++
>   1 file changed, 6 insertions(+)
> 
> diff --git a/documentation/ref-manual/variables.rst b/documentation/ref-manual/variables.rst
> index 1eee617d59ccddc9af0ffb95ea3635a707718152..c6d3d1bba9961704fca25921b346d5282e118db4 100644
> --- a/documentation/ref-manual/variables.rst
> +++ b/documentation/ref-manual/variables.rst
> @@ -4579,6 +4579,12 @@ system and gives an overview of their function and contents.
>         You can register custom kernel image types with the
>         :ref:`ref-classes-kernel` class using this variable.
>   
> +   :term:`KERNEL_CONSOLE`
> +     The :term:`KERNEL_CONSOLE` variable holds the value of the ``console``
> +     parameter of the kernel command line and can be used in places such as a
> +     ``wks`` description file for :ref:`Wic images <dev-manual/wic:creating
> +     partitioned images using wic>`.
> +

We could provide a link to the kernel command line documentation 
(https://www.kernel.org/doc/html/v6.12/admin-guide/kernel-parameters.html) 
and possibly specify the default value (it's in 
meta/conf/distro/include/default-distrovars.inc; essentially the first 
console device and its setting from SERIAL_CONSOLES if any set, 
otherwise ttyS0,115200).

In any case,

Reviewed-by: Quentin Schulz <quentin.schulz@cherry.de>

Thanks!
Quentin

[yocto-docs PATCH 02/14] ref-manual/classes: drop the migrate_localcount class

[Antonin Godard]

This class is obsolete and was removed from openembedded-core.

Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
---
 documentation/ref-manual/classes.rst | 8 --------
 1 file changed, 8 deletions(-)

diff --git a/documentation/ref-manual/classes.rst b/documentation/ref-manual/classes.rst
index e5fe44052d4b05bf1b2b3acfaf2fd368f66fb261..3d61d8d7a00b21fcff82a771f9718013fae36694 100644
--- a/documentation/ref-manual/classes.rst
+++ b/documentation/ref-manual/classes.rst
@@ -1877,14 +1877,6 @@ each layer before starting every build. The :ref:`ref-classes-metadata_scm`
 class is enabled by default because it is inherited by the
 :ref:`ref-classes-base` class.
 
-.. _ref-classes-migrate_localcount:
-
-``migrate_localcount``
-======================
-
-The :ref:`ref-classes-migrate_localcount` class verifies a recipe's localcount data and
-increments it appropriately.
-
 .. _ref-classes-mime:
 
 ``mime``

-- 
2.47.1

Re: [docs] [yocto-docs PATCH 02/14] ref-manual/classes: drop the migrate_localcount class

[Quentin Schulz]

Hi Antonin,

On 12/17/24 10:27 AM, Antonin Godard via lists.yoctoproject.org wrote:
> This class is obsolete and was removed from openembedded-core.
> 

Since when? This would help to know if we should backport it or not. (I 
know you're the maintainer :) ).

OE-Core fca25fc4d7721f85f64c942307ebe7ba9f2fad3e so only in master.

Its removal should probably also be mentioned in the migration manual of 
the next release?

Reviewed-by: Quentin Schulz <quentin.schulz@cherry.de>

Thanks!
Quentin

[yocto-docs PATCH 03/14] ref-manual/variables: document the FIRMWARE_COMPRESSION variable

[Antonin Godard]

Added in oecore after the 20241017 update.

Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
---
 documentation/ref-manual/variables.rst | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/documentation/ref-manual/variables.rst b/documentation/ref-manual/variables.rst
index c6d3d1bba9961704fca25921b346d5282e118db4..5875ee3e7c554ffedf4af86e61c207d10aa46ad9 100644
--- a/documentation/ref-manual/variables.rst
+++ b/documentation/ref-manual/variables.rst
@@ -3039,6 +3039,12 @@ system and gives an overview of their function and contents.
       tables, examine the existing ``fs-perms.txt``,
       ``fs-perms-volatile-log.txt`` and ``fs-perms-volatile-tmp.txt`` files.
 
+   :term:`FIRMWARE_COMPRESSION`
+      The :term:`FIRMWARE_COMPRESSION` allows compressing the firmware provided
+      by the ``linux-firmare`` recipe. The default value of this variable is an
+      empty string (no compression), and the possible values it can take are
+      ``xz`` and ``zst``. This can allow significant disk space savings.
+
    :term:`FIT_ADDRESS_CELLS`
       Specifies the value of the ``#address-cells`` value for the
       description of the FIT image.

-- 
2.47.1

Re: [docs] [yocto-docs PATCH 03/14] ref-manual/variables: document the FIRMWARE_COMPRESSION variable

[Quentin Schulz]

Hi Antonin,

On 12/17/24 10:27 AM, Antonin Godard via lists.yoctoproject.org wrote:
> Added in oecore after the 20241017 update.
> 
> Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
> ---
>   documentation/ref-manual/variables.rst | 6 ++++++
>   1 file changed, 6 insertions(+)
> 
> diff --git a/documentation/ref-manual/variables.rst b/documentation/ref-manual/variables.rst
> index c6d3d1bba9961704fca25921b346d5282e118db4..5875ee3e7c554ffedf4af86e61c207d10aa46ad9 100644
> --- a/documentation/ref-manual/variables.rst
> +++ b/documentation/ref-manual/variables.rst
> @@ -3039,6 +3039,12 @@ system and gives an overview of their function and contents.
>         tables, examine the existing ``fs-perms.txt``,
>         ``fs-perms-volatile-log.txt`` and ``fs-perms-volatile-tmp.txt`` files.
>   
> +   :term:`FIRMWARE_COMPRESSION`
> +      The :term:`FIRMWARE_COMPRESSION` allows compressing the firmware provided
> +      by the ``linux-firmare`` recipe. The default value of this variable is an

s/linux-firmare/linux-firmware/

> +      empty string (no compression), and the possible values it can take are
> +      ``xz`` and ``zst``. This can allow significant disk space savings.
> +

I believe it'd be good to state that the kernel needs to be configured 
such that it can make use of those compressed firmware files.

I believe the config options are FW_LOADER_COMPRESS_XZ and 
FW_LOADER_COMPRESS_ZSTD?

Cheers,
Quentin

[yocto-docs PATCH 04/14] ref-manual/variables: add missing entries to SDK_ARCHIVE_TYPE

[Antonin Godard]

Both added recently in oecore.

Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
---
 documentation/ref-manual/variables.rst | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/documentation/ref-manual/variables.rst b/documentation/ref-manual/variables.rst
index 5875ee3e7c554ffedf4af86e61c207d10aa46ad9..ada761045e9bf37cb294c0b66007a9faab995ec3 100644
--- a/documentation/ref-manual/variables.rst
+++ b/documentation/ref-manual/variables.rst
@@ -7515,6 +7515,8 @@ system and gives an overview of their function and contents.
       Specifies the type of archive to create for the SDK. Valid values:
 
       - ``tar.xz`` (default)
+      - ``tar.zst``
+      - ``7zip``
       - ``zip``
 
       Only one archive type can be specified.

-- 
2.47.1

Re: [docs] [yocto-docs PATCH 04/14] ref-manual/variables: add missing entries to SDK_ARCHIVE_TYPE

[Quentin Schulz]

Hi Antonin,

On 12/17/24 10:27 AM, Antonin Godard via lists.yoctoproject.org wrote:
> Both added recently in oecore.
> 
> Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>

Reviewed-by: Quentin Schulz <quentin.schulz@cherry.de>

Thanks!
Quentin

[yocto-docs PATCH 05/14] ref-manual/variables: document the WIC_SECTOR_SIZE variable

[Antonin Godard]

Added recently in oecore to control the sector size of wic images.

Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
---
 documentation/ref-manual/variables.rst | 11 +++++++++++
 1 file changed, 11 insertions(+)

diff --git a/documentation/ref-manual/variables.rst b/documentation/ref-manual/variables.rst
index ada761045e9bf37cb294c0b66007a9faab995ec3..bce8a1c7ed3af7115655f51aa0a6c558478d8c86 100644
--- a/documentation/ref-manual/variables.rst
+++ b/documentation/ref-manual/variables.rst
@@ -10194,6 +10194,17 @@ system and gives an overview of their function and contents.
       Specifies the timeout in seconds used by the ``watchdog`` recipe and
       also by ``systemd`` during reboot. The default is 60 seconds.
 
+   :term:`WIC_SECTOR_SIZE`
+      The variable :term:`WIC_SECTOR_SIZE` controls the sector size of Wic
+      images. In the background, this controls the value of the
+      ``PARTED_SECTOR_SIZE`` environment variable passed to the ``parted``
+      command-line utility, used to generated the images. The default value is
+      ``512``.
+
+      For more information on how to create Wic images, see the
+      ":ref:`dev-manual/wic:creating partitioned images using wic`" section in
+      the Yocto Project Development Tasks Manual.
+
    :term:`WIRELESS_DAEMON`
       For ``connman`` and ``packagegroup-base``, specifies the wireless
       daemon to use. The default is "wpa-supplicant" (note that the value

-- 
2.47.1

Re: [docs] [yocto-docs PATCH 05/14] ref-manual/variables: document the WIC_SECTOR_SIZE variable

[Quentin Schulz]

Hi Antonin,

On 12/17/24 10:27 AM, Antonin Godard via lists.yoctoproject.org wrote:
> Added recently in oecore to control the sector size of wic images.
> 
> Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>

Reviewed-by: Quentin Schulz <quentin.schulz@cherry.de>

Thanks!
Quentin

[yocto-docs PATCH 06/14] ref-manual/variable: remove obsolete SETUPTOOLS_INSTALL_ARGS

[Antonin Godard]

Remove in oecore by commit b4bdfc78e8e1cb8b86221bc55d80d601ea1a065f
("python3-cython: remove obsolete SETUPTOOLS_INSTALL_ARGS").

Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
---
 documentation/ref-manual/variables.rst | 5 -----
 1 file changed, 5 deletions(-)

diff --git a/documentation/ref-manual/variables.rst b/documentation/ref-manual/variables.rst
index bce8a1c7ed3af7115655f51aa0a6c558478d8c86..2c2226dd16c25ebb5cdefce9a657a124e51ab143 100644
--- a/documentation/ref-manual/variables.rst
+++ b/documentation/ref-manual/variables.rst
@@ -7841,11 +7841,6 @@ system and gives an overview of their function and contents.
       class, this variable can be used to specify additional arguments to be
       passed to ``setup.py build`` in the ``setuptools3_do_compile()`` task.
 
-   :term:`SETUPTOOLS_INSTALL_ARGS`
-      When used by recipes that inherit the :ref:`ref-classes-setuptools3`
-      class, this variable can be used to specify additional arguments to be
-      passed to ``setup.py install`` in the ``setuptools3_do_install()`` task.
-
    :term:`SETUPTOOLS_SETUP_PATH`
       When used by recipes that inherit the :ref:`ref-classes-setuptools3`
       class, this variable should be used to specify the directory in which

-- 
2.47.1

Re: [docs] [yocto-docs PATCH 06/14] ref-manual/variable: remove obsolete SETUPTOOLS_INSTALL_ARGS

[Quentin Schulz]

Hi Antonin,

On 12/17/24 10:27 AM, Antonin Godard via lists.yoctoproject.org wrote:
> Remove in oecore by commit b4bdfc78e8e1cb8b86221bc55d80d601ea1a065f
> ("python3-cython: remove obsolete SETUPTOOLS_INSTALL_ARGS").
> 

But actually unused since 57c477ca13e352b6f9b21385abbfaad9778c6398, i.e. 
from Kirkstone. So I believe this should be backported (and added to 
migration manuals).

Reviewed-by: Quentin Schulz <quentin.schulz@cherry.de>

Thanks!
Quentin

[yocto-docs PATCH 07/14] ref-manual/classes: document the cython class

[Antonin Godard]

Small class added in oecore by commit
64b6e8580842949be58f97f4dff91d1f097c4020 ("classes-recipe: add cython
class").

Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
---
 documentation/ref-manual/classes.rst | 11 +++++++++++
 1 file changed, 11 insertions(+)

diff --git a/documentation/ref-manual/classes.rst b/documentation/ref-manual/classes.rst
index 3d61d8d7a00b21fcff82a771f9718013fae36694..47f049c7435a989f30c033b7b12d86482686ac77 100644
--- a/documentation/ref-manual/classes.rst
+++ b/documentation/ref-manual/classes.rst
@@ -614,6 +614,17 @@ You will find some more details in the
 ":ref:`dev-manual/vulnerabilities:checking for vulnerabilities`"
 section in the Development Tasks Manual.
 
+.. _ref-classes-cython:
+
+``cython``
+==========
+
+The :ref:`ref-classes-cython` class can be used by Python recipes that require
+:oe_git:`Cython </openembedded-core/tree/meta/recipes-devtools/python/python3-cython_3.0.11.bb>`
+as part of their build dependencies (:term:`DEPENDS`). It also improves
+reproducibility for these recipes by stripping potential leftovers build paths
+in compilation outputs.
+
 .. _ref-classes-debian:
 
 ``debian``

-- 
2.47.1

Re: [docs] [yocto-docs PATCH 07/14] ref-manual/classes: document the cython class

[Quentin Schulz]

Hi Antonin,

On 12/17/24 10:27 AM, Antonin Godard via lists.yoctoproject.org wrote:
> Small class added in oecore by commit
> 64b6e8580842949be58f97f4dff91d1f097c4020 ("classes-recipe: add cython
> class").
> 
> Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
> ---
>   documentation/ref-manual/classes.rst | 11 +++++++++++
>   1 file changed, 11 insertions(+)
> 
> diff --git a/documentation/ref-manual/classes.rst b/documentation/ref-manual/classes.rst
> index 3d61d8d7a00b21fcff82a771f9718013fae36694..47f049c7435a989f30c033b7b12d86482686ac77 100644
> --- a/documentation/ref-manual/classes.rst
> +++ b/documentation/ref-manual/classes.rst
> @@ -614,6 +614,17 @@ You will find some more details in the
>   ":ref:`dev-manual/vulnerabilities:checking for vulnerabilities`"
>   section in the Development Tasks Manual.
>   
> +.. _ref-classes-cython:
> +
> +``cython``
> +==========
> +
> +The :ref:`ref-classes-cython` class can be used by Python recipes that require
> +:oe_git:`Cython </openembedded-core/tree/meta/recipes-devtools/python/python3-cython_3.0.11.bb>`

I'm not entirely sure this is a good idea. This will eventually change 
during a version upgrade and the recipe at that version disappear and 
this link be useless. Two options: no link or a link from a specific 
commit so it is always there.

I am not entirely sure pointing to the Cython recipe provides anything 
meaningful here so I would vote for removing the link (could be a link 
to the Cython project instead?).

> +as part of their build dependencies (:term:`DEPENDS`). It also improves
> +reproducibility for these recipes by stripping potential leftovers build paths
> +in compilation outputs.
> +

I'm not sure the reproducibility improvement need to be mentioned here. 
It seems to me like this could be interpreted as "if you want improved 
reproducibility you can include this class even if the recipe doesn't 
need Cython". If it needs Cython, I assume the leftover issues for 
reproducibility are coming from Cython so it's expected we fix those? 
Not sure it's very clear what I'm trying to convey here?

Cheers,
Quentin

Re: [docs] [yocto-docs PATCH 07/14] ref-manual/classes: document the cython class

[Antonin Godard]

Hi Quentin,

On Tue Dec 17, 2024 at 11:48 AM CET, Quentin Schulz wrote:
> Hi Antonin,
>
> On 12/17/24 10:27 AM, Antonin Godard via lists.yoctoproject.org wrote:
>> Small class added in oecore by commit
>> 64b6e8580842949be58f97f4dff91d1f097c4020 ("classes-recipe: add cython
>> class").
>> 
>> Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
>> ---
>>   documentation/ref-manual/classes.rst | 11 +++++++++++
>>   1 file changed, 11 insertions(+)
>> 
>> diff --git a/documentation/ref-manual/classes.rst b/documentation/ref-manual/classes.rst
>> index 3d61d8d7a00b21fcff82a771f9718013fae36694..47f049c7435a989f30c033b7b12d86482686ac77 100644
>> --- a/documentation/ref-manual/classes.rst
>> +++ b/documentation/ref-manual/classes.rst
>> @@ -614,6 +614,17 @@ You will find some more details in the
>>   ":ref:`dev-manual/vulnerabilities:checking for vulnerabilities`"
>>   section in the Development Tasks Manual.
>>   
>> +.. _ref-classes-cython:
>> +
>> +``cython``
>> +==========
>> +
>> +The :ref:`ref-classes-cython` class can be used by Python recipes that require
>> +:oe_git:`Cython </openembedded-core/tree/meta/recipes-devtools/python/python3-cython_3.0.11.bb>`
>
> I'm not entirely sure this is a good idea. This will eventually change 
> during a version upgrade and the recipe at that version disappear and 
> this link be useless. Two options: no link or a link from a specific 
> commit so it is always there.
>
> I am not entirely sure pointing to the Cython recipe provides anything 
> meaningful here so I would vote for removing the link (could be a link 
> to the Cython project instead?).

Of course, I forgot about this.
I will link the Cython project instead.

>> +as part of their build dependencies (:term:`DEPENDS`). It also improves
>> +reproducibility for these recipes by stripping potential leftovers build paths
>> +in compilation outputs.
>> +
>
> I'm not sure the reproducibility improvement need to be mentioned here. 
> It seems to me like this could be interpreted as "if you want improved 
> reproducibility you can include this class even if the recipe doesn't 
> need Cython". If it needs Cython, I assume the leftover issues for 
> reproducibility are coming from Cython so it's expected we fix those? 
> Not sure it's very clear what I'm trying to convey here?

Yes, and there must other places where reproducibility is improved and the docs
doesn't mention it. I'll remove this.


Thanks!
Antonin

-- 
Antonin Godard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

[yocto-docs PATCH 08/14] Remove debug-tweaks references

[Antonin Godard]

We no longer provide this feature, so remove documentation for it. In
most cases, we can replace occurrences of "debug-tweaks" by
"allow-empty-password empty-root-password allow-root-login
post-install-logging" to achieve what this feature previously enabled.

Subtle, but the default local.conf does not include
post-install-logging, so in parts where there is mention of the default
local.conf file, adjust the documentation to only mention the first
three above.

In the intro manual, instead of providing instructions that replace
EXTRA_IMAGE_FEATURES entirely, provide ones that append
EXTRA_IMAGE_FEATURES.

Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
---
 documentation/dev-manual/build-quality.rst      |  2 +-
 documentation/dev-manual/customizing-images.rst |  3 +--
 documentation/dev-manual/securing-images.rst    | 12 ++++++------
 documentation/profile-manual/intro.rst          |  4 ++--
 documentation/profile-manual/usage.rst          |  2 +-
 documentation/ref-manual/features.rst           | 19 ++++++-------------
 documentation/ref-manual/variables.rst          | 12 ++++++++----
 documentation/sdk-manual/extensible.rst         |  5 ++++-
 8 files changed, 29 insertions(+), 30 deletions(-)

diff --git a/documentation/dev-manual/build-quality.rst b/documentation/dev-manual/build-quality.rst
index 713ea3a48e53ce42634c89325edc3e95987d0aaa..fbe5fb6f0bb34df440b06bc51123eb36c33bba23 100644
--- a/documentation/dev-manual/build-quality.rst
+++ b/documentation/dev-manual/build-quality.rst
@@ -236,7 +236,7 @@ Here is an example of ``image-info.txt``:
    DISTRO_VERSION = 3.4+snapshot-a0245d7be08f3d24ea1875e9f8872aa6bbff93be
    USER_CLASSES = buildstats
    IMAGE_CLASSES = qemuboot qemuboot license_image
-   IMAGE_FEATURES = debug-tweaks
+   IMAGE_FEATURES = allow-empty-password empty-root-password allow-root-login post-install-logging
    IMAGE_LINGUAS =
    IMAGE_INSTALL = packagegroup-core-boot speex speexdsp
    BAD_RECOMMENDATIONS =
diff --git a/documentation/dev-manual/customizing-images.rst b/documentation/dev-manual/customizing-images.rst
index 5b18958adec38945a163940faa778a597bc961ad..63482594465112aaf33fa2741e98b69830d8a48f 100644
--- a/documentation/dev-manual/customizing-images.rst
+++ b/documentation/dev-manual/customizing-images.rst
@@ -62,8 +62,7 @@ To understand how these features work, the best reference is
 :ref:`meta/classes-recipe/image.bbclass <ref-classes-image>`.
 This class lists out the available
 :term:`IMAGE_FEATURES` of which most map to package groups while some, such
-as ``debug-tweaks`` and ``read-only-rootfs``, resolve as general
-configuration settings.
+as ``read-only-rootfs``, resolve as general configuration settings.
 
 In summary, the file looks at the contents of the :term:`IMAGE_FEATURES`
 variable and then maps or configures the feature accordingly. Based on
diff --git a/documentation/dev-manual/securing-images.rst b/documentation/dev-manual/securing-images.rst
index e5791d3d6df463a3d35665686dc2a53a3711e3fb..f4b528e559088b0021aab78bfc613640c493ff0a 100644
--- a/documentation/dev-manual/securing-images.rst
+++ b/documentation/dev-manual/securing-images.rst
@@ -107,18 +107,18 @@ Considerations Specific to the OpenEmbedded Build System
 You can take some steps that are specific to the OpenEmbedded build
 system to make your images more secure:
 
--  Ensure "debug-tweaks" is not one of your selected
-   :term:`IMAGE_FEATURES`.
+-  Ensure that "allow-empty-password", "allow-root-login", or
+   "empty-root-password" are not one of your selected :term:`IMAGE_FEATURES`.
    When creating a new project, the default is to provide you with an
-   initial ``local.conf`` file that enables this feature using the
+   initial ``local.conf`` file that enables these features using the
    :term:`EXTRA_IMAGE_FEATURES`
    variable with the line::
 
-      EXTRA_IMAGE_FEATURES = "debug-tweaks"
+      EXTRA_IMAGE_FEATURES = "allow-empty-password empty-root-password allow-root-login"
 
-   To disable that feature, simply comment out that line in your
+   To disable these features, simply comment out that line in your
    ``local.conf`` file, or make sure :term:`IMAGE_FEATURES` does not contain
-   "debug-tweaks" before producing your final image. Among other things,
+   any of these features before producing your final image. Among other things,
    leaving this in place sets the root password as blank, which makes
    logging in for debugging or inspection easy during development but
    also means anyone can easily log in during production.
diff --git a/documentation/profile-manual/intro.rst b/documentation/profile-manual/intro.rst
index 86310cf318411e8995e88ee2b71031887c9ab097..31791255246ec6335d9a957b4514a1a43c72a30f 100644
--- a/documentation/profile-manual/intro.rst
+++ b/documentation/profile-manual/intro.rst
@@ -43,7 +43,7 @@ an ``sdk`` image, perhaps one of::
 Alternatively,  you can add ``tools-profile`` to the :term:`EXTRA_IMAGE_FEATURES` line in
 your ``local.conf`` file::
 
-   EXTRA_IMAGE_FEATURES = "debug-tweaks tools-profile"
+   EXTRA_IMAGE_FEATURES:append = " tools-profile"
 
 If you use the ``tools-profile`` method, you don't need to build an sdk image ---
 the tracing and profiling tools will be included in non-sdk images as well e.g.::
@@ -69,7 +69,7 @@ packages (xxx-dbg) which you can manually install as needed.
 To generate debug info for packages, you can add ``dbg-pkgs`` to
 :term:`EXTRA_IMAGE_FEATURES` in ``local.conf``. For example::
 
-   EXTRA_IMAGE_FEATURES = "debug-tweaks tools-profile dbg-pkgs"
+   EXTRA_IMAGE_FEATURES:append = " dbg-pkgs"
 
 Additionally, in order to generate the right type of debug info, we also need to
 set :term:`PACKAGE_DEBUG_SPLIT_STYLE` in the ``local.conf`` file::
diff --git a/documentation/profile-manual/usage.rst b/documentation/profile-manual/usage.rst
index 17be149580341366f950d74f0c1a21e0ccd971ed..d17b256d0f649a6d11481a9aebaec54f3d753f94 100644
--- a/documentation/profile-manual/usage.rst
+++ b/documentation/profile-manual/usage.rst
@@ -308,7 +308,7 @@ install the debugging information for the BusyBox package.
 To generate the debug info for the packages in the image, we can add
 ``dbg-pkgs`` to :term:`EXTRA_IMAGE_FEATURES` in ``local.conf``. For example::
 
-   EXTRA_IMAGE_FEATURES = "debug-tweaks tools-profile dbg-pkgs"
+   EXTRA_IMAGE_FEATURES:append = " dbg-pkgs"
 
 Additionally, in order to generate the type of debugging information that perf
 understands, we also need to set :term:`PACKAGE_DEBUG_SPLIT_STYLE`
diff --git a/documentation/ref-manual/features.rst b/documentation/ref-manual/features.rst
index 6e52dfce17b9e06bdb8ad67a5fc8d7304a0f479d..4d327f1a7dca93010b932636dab1f229d667d1cd 100644
--- a/documentation/ref-manual/features.rst
+++ b/documentation/ref-manual/features.rst
@@ -285,31 +285,24 @@ The image features available for all images are:
 -  *dbg-pkgs:* Installs debug symbol packages for all packages installed
    in a given image.
 
--  *debug-tweaks:* Makes an image suitable for development (e.g. allows
-   root logins, logins without passwords ---including root ones, and enables
-   post-installation logging). See the ``allow-empty-password``,
-   ``allow-root-login``, ``empty-root-password``, and ``post-install-logging``
-   features in this list for additional information.
-
 -  *dev-pkgs:* Installs development packages (headers and extra library
    links) for all packages installed in a given image.
 
 -  *doc-pkgs:* Installs documentation packages for all packages
    installed in a given image.
 
--  *empty-root-password:* This feature or ``debug-tweaks`` is required if
-   you want to allow root login with an empty password. If these features
-   are not present in :term:`IMAGE_FEATURES`, a non-empty password is
-   forced in ``/etc/passwd`` and ``/etc/shadow`` if such files exist.
+-  *empty-root-password:* This feature can be used if you want to allow root
+   login with an empty password. If this feature is not present in
+   :term:`IMAGE_FEATURES`, a non-empty password is forced in ``/etc/passwd`` and
+   ``/etc/shadow`` if such files exist.
 
    .. note::
        ``empty-root-password`` doesn't set an empty root password by itself.
        You get an initial empty root password thanks to the
        :oe_git:`base-passwd </openembedded-core/tree/meta/recipes-core/base-passwd/>`
        and :oe_git:`shadow </openembedded-core/tree/meta/recipes-extended/shadow/>`
-       recipes, and the presence of ``empty-root-password`` or ``debug-tweaks``
-       just disables the mechanism which forces an non-empty password for the
-       root user.
+       recipes, and the presence of ``empty-root-password`` just disables the
+       mechanism which forces an non-empty password for the root user.
 
 -  *lic-pkgs:* Installs license packages for all packages installed in a
    given image.
diff --git a/documentation/ref-manual/variables.rst b/documentation/ref-manual/variables.rst
index 2c2226dd16c25ebb5cdefce9a657a124e51ab143..08fb0f4d5666b80be153f39310826a7e1b9022fe 100644
--- a/documentation/ref-manual/variables.rst
+++ b/documentation/ref-manual/variables.rst
@@ -2605,10 +2605,14 @@ system and gives an overview of their function and contents.
         - "dbg-pkgs" --- adds -dbg packages for all installed packages including
           symbol information for debugging and profiling.
 
-        - "debug-tweaks" --- makes an image suitable for debugging. For example, allows root logins without passwords and
-          enables post-installation logging. See the 'allow-empty-password' and
-          'post-install-logging' features in the ":ref:`ref-features-image`"
-          section for more information.
+        - "empty-root-password" --- This feature can be used if you want to
+          allow root login with an empty password.
+        - "allow-empty-password" --- Allows Dropbear and OpenSSH to accept
+          logins from accounts having an empty password string.
+        - "allow-root-login" --- Allows Dropbear and OpenSSH to accept root logins.
+        - "post-install-logging" --- Enables logging postinstall script runs to
+          the ``/var/log/postinstall.log`` file on first boot of the image on
+          the target system.
         - "dev-pkgs" --- adds -dev packages for all installed packages. This is
           useful if you want to develop against the libraries in the image.
         - "read-only-rootfs" --- creates an image whose root filesystem is
diff --git a/documentation/sdk-manual/extensible.rst b/documentation/sdk-manual/extensible.rst
index 3f6a754d8818cdf3b718c359ef68238dea34b655..9a50d7fc54c280441958890730eea94a5fee8940 100644
--- a/documentation/sdk-manual/extensible.rst
+++ b/documentation/sdk-manual/extensible.rst
@@ -655,7 +655,10 @@ The extensible SDK supports two different development modes.
       # SSH is mandatory, no password simplifies the usage
       EXTRA_IMAGE_FEATURES += "\
          ssh-server-openssh \
-         debug-tweaks \
+         allow-empty-password \
+         allow-root-login \
+         empty-root-password \
+         post-install-logging \
       "
 
       # Remote debugging needs gdbserver on the target device

-- 
2.47.1

[yocto-docs PATCH 09/14] Drop support for BB_DANGLINGAPPENDS_WARNONLY

[Antonin Godard]

Support for this variable was dropped in BitBake, see commit
fca9c9e3cb6f8e9f99bf51dc5e8a8d83f4c84c69 ("cooker: Drop support for
BB_DANGLINGAPPENDS_WARNONLY").

Drop this variable here as well and rewrite the "Appending Other Layers
Metadata With Your Layer" section to advise to rename the recipe and
check if the bbappend is still relevant - otherwise to use BBWARN.

Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
---
 documentation/dev-manual/layers.rst    | 15 ++++++++++-----
 documentation/ref-manual/variables.rst | 18 ------------------
 2 files changed, 10 insertions(+), 23 deletions(-)

diff --git a/documentation/dev-manual/layers.rst b/documentation/dev-manual/layers.rst
index 89c84669337c9ecdc90110fdf34b7949459a1b9f..365991c225159d051f6dc4122625616b81f01ee3 100644
--- a/documentation/dev-manual/layers.rst
+++ b/documentation/dev-manual/layers.rst
@@ -470,11 +470,16 @@ corresponding recipe file. For example, the append file
 means the original recipe and append filenames are version
 number-specific. If the corresponding recipe is renamed to update to a
 newer version, you must also rename and possibly update the
-corresponding ``.bbappend`` as well. During the build process, BitBake
-displays an error on starting if it detects a ``.bbappend`` file that
-does not have a corresponding recipe with a matching name. See the
-:term:`BB_DANGLINGAPPENDS_WARNONLY`
-variable for information on how to handle this error.
+corresponding ``.bbappend`` as well.
+
+During the build process, BitBake displays an error on startup if it detects a
+``.bbappend`` file that does not have a corresponding recipe with a matching
+name. To handle these errors, the better practice is to rename the ``.bbappend``
+to match the original recipe version. This also gives you the opportunity to see
+if the ``.bbappend`` is still relevant for the new version of the recipe.
+
+Another method to deal with these errors is to use the variable :term:`BBMASK`,
+especially in cases where modifying the ``.bbappend`` is not possible.
 
 Overlaying a File Using Your Layer
 ----------------------------------
diff --git a/documentation/ref-manual/variables.rst b/documentation/ref-manual/variables.rst
index 08fb0f4d5666b80be153f39310826a7e1b9022fe..d54e1365fcf3dabd3868aa80089afda727b1415a 100644
--- a/documentation/ref-manual/variables.rst
+++ b/documentation/ref-manual/variables.rst
@@ -362,24 +362,6 @@ system and gives an overview of their function and contents.
    :term:`BB_CURRENTTASK`
       See :term:`bitbake:BB_CURRENTTASK` in the BitBake manual.
 
-   :term:`BB_DANGLINGAPPENDS_WARNONLY`
-      Defines how BitBake handles situations where an append file
-      (``.bbappend``) has no corresponding recipe file (``.bb``). This
-      condition often occurs when layers get out of sync (e.g. ``oe-core``
-      bumps a recipe version and the old recipe no longer exists and the
-      other layer has not been updated to the new version of the recipe
-      yet).
-
-      The default fatal behavior is safest because it is the sane reaction
-      given something is out of sync. It is important to realize when your
-      changes are no longer being applied.
-
-      You can change the default behavior by setting this variable to "1",
-      "yes", or "true" in your ``local.conf`` file, which is located in the
-      :term:`Build Directory`: Here is an example::
-
-         BB_DANGLINGAPPENDS_WARNONLY = "1"
-
    :term:`BB_DEFAULT_TASK`
       See :term:`bitbake:BB_DEFAULT_TASK` in the BitBake manual.
 

-- 
2.47.1

Re: [docs] [yocto-docs PATCH 09/14] Drop support for BB_DANGLINGAPPENDS_WARNONLY

[Quentin Schulz]

Hi Antonin,

On 12/17/24 10:27 AM, Antonin Godard via lists.yoctoproject.org wrote:
> Support for this variable was dropped in BitBake, see commit
> fca9c9e3cb6f8e9f99bf51dc5e8a8d83f4c84c69 ("cooker: Drop support for
> BB_DANGLINGAPPENDS_WARNONLY").
> 
> Drop this variable here as well and rewrite the "Appending Other Layers
> Metadata With Your Layer" section to advise to rename the recipe and
> check if the bbappend is still relevant - otherwise to use BBWARN.
> 
> Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
> ---
>   documentation/dev-manual/layers.rst    | 15 ++++++++++-----
>   documentation/ref-manual/variables.rst | 18 ------------------
>   2 files changed, 10 insertions(+), 23 deletions(-)
> 
> diff --git a/documentation/dev-manual/layers.rst b/documentation/dev-manual/layers.rst
> index 89c84669337c9ecdc90110fdf34b7949459a1b9f..365991c225159d051f6dc4122625616b81f01ee3 100644
> --- a/documentation/dev-manual/layers.rst
> +++ b/documentation/dev-manual/layers.rst
> @@ -470,11 +470,16 @@ corresponding recipe file. For example, the append file
>   means the original recipe and append filenames are version
>   number-specific. If the corresponding recipe is renamed to update to a
>   newer version, you must also rename and possibly update the
> -corresponding ``.bbappend`` as well. During the build process, BitBake
> -displays an error on starting if it detects a ``.bbappend`` file that
> -does not have a corresponding recipe with a matching name. See the
> -:term:`BB_DANGLINGAPPENDS_WARNONLY`
> -variable for information on how to handle this error.
> +corresponding ``.bbappend`` as well.
> +
> +During the build process, BitBake displays an error on startup if it detects a
> +``.bbappend`` file that does not have a corresponding recipe with a matching
> +name. To handle these errors, the better practice is to rename the ``.bbappend``

We usually say best practice in the docs (haven't found one occurrence 
of better practice with a naive grep search). Did you mean best practice 
maybe?

> +to match the original recipe version. This also gives you the opportunity to see
> +if the ``.bbappend`` is still relevant for the new version of the recipe.
> +
> +Another method to deal with these errors is to use the variable :term:`BBMASK`,
> +especially in cases where modifying the ``.bbappend`` is not possible.
>   

And another method is to make use of the % character in the filename 
where possible? E.g. for minor updates (I still like my gstreamer 
bbappend example since it continues to happen to me during rebases :) ), 
one could use someapp_3.%.bbappend.

Otherwise looks good to me, should be part of the migration manual I 
believe?

Cheers,
Quentin

Re: [docs] [yocto-docs PATCH 09/14] Drop support for BB_DANGLINGAPPENDS_WARNONLY

[Antonin Godard]

Hi Quentin,

On Tue Dec 17, 2024 at 3:08 PM CET, Quentin Schulz wrote:
> Hi Antonin,
>
> On 12/17/24 10:27 AM, Antonin Godard via lists.yoctoproject.org wrote:
>> Support for this variable was dropped in BitBake, see commit
>> fca9c9e3cb6f8e9f99bf51dc5e8a8d83f4c84c69 ("cooker: Drop support for
>> BB_DANGLINGAPPENDS_WARNONLY").
>> 
>> Drop this variable here as well and rewrite the "Appending Other Layers
>> Metadata With Your Layer" section to advise to rename the recipe and
>> check if the bbappend is still relevant - otherwise to use BBWARN.
>> 
>> Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
>> ---
>>   documentation/dev-manual/layers.rst    | 15 ++++++++++-----
>>   documentation/ref-manual/variables.rst | 18 ------------------
>>   2 files changed, 10 insertions(+), 23 deletions(-)
>> 
>> diff --git a/documentation/dev-manual/layers.rst b/documentation/dev-manual/layers.rst
>> index 89c84669337c9ecdc90110fdf34b7949459a1b9f..365991c225159d051f6dc4122625616b81f01ee3 100644
>> --- a/documentation/dev-manual/layers.rst
>> +++ b/documentation/dev-manual/layers.rst
>> @@ -470,11 +470,16 @@ corresponding recipe file. For example, the append file
>>   means the original recipe and append filenames are version
>>   number-specific. If the corresponding recipe is renamed to update to a
>>   newer version, you must also rename and possibly update the
>> -corresponding ``.bbappend`` as well. During the build process, BitBake
>> -displays an error on starting if it detects a ``.bbappend`` file that
>> -does not have a corresponding recipe with a matching name. See the
>> -:term:`BB_DANGLINGAPPENDS_WARNONLY`
>> -variable for information on how to handle this error.
>> +corresponding ``.bbappend`` as well.
>> +
>> +During the build process, BitBake displays an error on startup if it detects a
>> +``.bbappend`` file that does not have a corresponding recipe with a matching
>> +name. To handle these errors, the better practice is to rename the ``.bbappend``
>
> We usually say best practice in the docs (haven't found one occurrence 
> of better practice with a naive grep search). Did you mean best practice 
> maybe?

Oops, "best" it is yes :)

>> +to match the original recipe version. This also gives you the opportunity to see
>> +if the ``.bbappend`` is still relevant for the new version of the recipe.
>> +
>> +Another method to deal with these errors is to use the variable :term:`BBMASK`,
>> +especially in cases where modifying the ``.bbappend`` is not possible.
>>   
>
> And another method is to make use of the % character in the filename 
> where possible? E.g. for minor updates (I still like my gstreamer 
> bbappend example since it continues to happen to me during rebases :) ), 
> one could use someapp_3.%.bbappend.

Yes, that's right, I will also add this method. I'll mention matching the minor
version only if possible, not the entire version, to avoid masking too much when
updating. It's good to take a look at a bbappend every once and a while. :)

> Otherwise looks good to me, should be part of the migration manual I
> believe?

Yes absolutely, thanks!

Antonin

-- 
Antonin Godard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

[yocto-docs PATCH 10/14] ref-manual/variables: document the CHECKLAYER_REQUIRED_TESTS variable

[Antonin Godard]

This was introduced in oecore by commit
ce2e42ace2d15fb6745437cf0a7f07d28398ca12 ("insane: Split ERROR_QA into
CHECKLAYER_REQUIRED_TESTS").

Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
---
 documentation/ref-manual/variables.rst | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/documentation/ref-manual/variables.rst b/documentation/ref-manual/variables.rst
index d54e1365fcf3dabd3868aa80089afda727b1415a..66ecece8b2658b304e17c9c4a1492e42a8a313d4 100644
--- a/documentation/ref-manual/variables.rst
+++ b/documentation/ref-manual/variables.rst
@@ -1251,6 +1251,13 @@ system and gives an overview of their function and contents.
       -  :term:`BUILDSDK_CFLAGS` when building for
          an SDK (i.e. ``nativesdk-``)
 
+   :term:`CHECKLAYER_REQUIRED_TESTS`
+      The :term:`CHECKLAYER_REQUIRED_TESTS` variable lists the QA tests that are
+      required to be enabled to pass the Yocto Project Compatible status for a
+      layer. For more information on the Yocto Project Compatible status, see
+      the :ref:`dev-manual/layers:Making Sure Your Layer is Compatible With
+      Yocto Project` section of the Yocto Project Development Manual.
+
    :term:`CLASSOVERRIDE`
       An internal variable specifying the special class override that
       should currently apply (e.g. "class-target", "class-native", and so

-- 
2.47.1

Re: [docs] [yocto-docs PATCH 10/14] ref-manual/variables: document the CHECKLAYER_REQUIRED_TESTS variable

[Quentin Schulz]

Hi Antonin,

On 12/17/24 10:27 AM, Antonin Godard via lists.yoctoproject.org wrote:
> This was introduced in oecore by commit
> ce2e42ace2d15fb6745437cf0a7f07d28398ca12 ("insane: Split ERROR_QA into
> CHECKLAYER_REQUIRED_TESTS").
> 
> Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
> ---
>   documentation/ref-manual/variables.rst | 7 +++++++
>   1 file changed, 7 insertions(+)
> 
> diff --git a/documentation/ref-manual/variables.rst b/documentation/ref-manual/variables.rst
> index d54e1365fcf3dabd3868aa80089afda727b1415a..66ecece8b2658b304e17c9c4a1492e42a8a313d4 100644
> --- a/documentation/ref-manual/variables.rst
> +++ b/documentation/ref-manual/variables.rst
> @@ -1251,6 +1251,13 @@ system and gives an overview of their function and contents.
>         -  :term:`BUILDSDK_CFLAGS` when building for
>            an SDK (i.e. ``nativesdk-``)
>   
> +   :term:`CHECKLAYER_REQUIRED_TESTS`
> +      The :term:`CHECKLAYER_REQUIRED_TESTS` variable lists the QA tests that are
> +      required to be enabled to pass the Yocto Project Compatible status for a
> +      layer. For more information on the Yocto Project Compatible status, see
> +      the :ref:`dev-manual/layers:Making Sure Your Layer is Compatible With
> +      Yocto Project` section of the Yocto Project Development Manual.
> +

I don't think anything prevents us from modifying this variable to 
"pass" the test. Maybe we should say that this is meant to be a 
read-only variable essentially? And that modifications to the variable 
may only be done with approval from Yocto TSC?

Otherwise, looks good to me.

Cheers,
Quentin

[yocto-docs PATCH 11/14] ref-manual/classes: document the yocto-check-layer class

[Antonin Godard]

This class is used by the yocto-check-layer script to check if a layer
complies to the Yocto Project Compatible status.

Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
---
 documentation/ref-manual/classes.rst | 20 ++++++++++++++++++++
 1 file changed, 20 insertions(+)

diff --git a/documentation/ref-manual/classes.rst b/documentation/ref-manual/classes.rst
index 47f049c7435a989f30c033b7b12d86482686ac77..2480b4e221ff1d83585eb277c01d716e6bfa5a00 100644
--- a/documentation/ref-manual/classes.rst
+++ b/documentation/ref-manual/classes.rst
@@ -3604,3 +3604,23 @@ the Waf build system. You can use the
 :term:`PACKAGECONFIG_CONFARGS` variables
 to specify additional configuration options to be passed on the Waf
 command line.
+
+.. _ref-classes-yocto-check-layer:
+
+``yocto-check-layer``
+=====================
+
+The :ref:`ref-classes-yocto-check-layer` class is used by the
+:oe_git:`yocto-check-layer </openembedded-core/tree/scripts/yocto-check-layer>`
+script to ensure that packages from Yocto Project Compatible layers don't skip
+required QA checks listed in :term:`CHECKLAYER_REQUIRED_TESTS` defined by the
+:ref:`ref-classes-insane` class.
+
+It adds an anonymous python function with extra processing to all recipes,
+and globally inheriting this class with :term:`INHERIT` is not advised. Instead
+the ``yocto-check-layer`` script should be used as it handles usage of this
+class.
+
+For more information on the Yocto Project
+Compatible layers, see the :ref:`dev-manual/layers:Making Sure Your Layer is
+Compatible With Yocto Project` section of the Yocto Project Development Manual.

-- 
2.47.1

Re: [docs] [yocto-docs PATCH 11/14] ref-manual/classes: document the yocto-check-layer class

[Quentin Schulz]

Hi Antonin,

On 12/17/24 10:27 AM, Antonin Godard via lists.yoctoproject.org wrote:
> This class is used by the yocto-check-layer script to check if a layer
> complies to the Yocto Project Compatible status.
> 
> Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>

Reviewed-by: Quentin Schulz <quentin.schulz@cherry.de>

Thanks!
Quentin

[yocto-docs PATCH 12/14] ref-manual/variables: document the CARGO_INSTALL_LIBRARIES variable

[Antonin Godard]

This variable controls whether libraries compiled by recipes inheriting
cargo are installed or not.

Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
---
 documentation/ref-manual/variables.rst | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/documentation/ref-manual/variables.rst b/documentation/ref-manual/variables.rst
index 66ecece8b2658b304e17c9c4a1492e42a8a313d4..50cd8948b35f381414837acc9b9e925dc5110779 100644
--- a/documentation/ref-manual/variables.rst
+++ b/documentation/ref-manual/variables.rst
@@ -1231,6 +1231,14 @@ system and gives an overview of their function and contents.
       :term:`Metadata` so it does not need to be parsed every time
       BitBake is started.
 
+   :term:`CARGO_INSTALL_LIBRARIES`
+      When inheriting the :ref:`ref-classes-cargo` class, the variable
+      :term:`CARGO_INSTALL_LIBRARIES` can be set to a non-empty value by
+      individual recipes to enable or disable installation of the libraries the
+      recipe has built in ``${B}/target`` (files ending with ``.so`` or
+      ``.rlib``). By default this variable is not defined and libraries are not
+      installed, to replicate the behavior of the ``cargo install`` command.
+
    :term:`CC`
       The minimal command and arguments used to run the C compiler.
 

-- 
2.47.1

Re: [docs] [yocto-docs PATCH 12/14] ref-manual/variables: document the CARGO_INSTALL_LIBRARIES variable

[Quentin Schulz]

Hi Antonin,

On 12/17/24 10:27 AM, Antonin Godard via lists.yoctoproject.org wrote:
> This variable controls whether libraries compiled by recipes inheriting
> cargo are installed or not.
> 
> Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
> ---
>   documentation/ref-manual/variables.rst | 8 ++++++++
>   1 file changed, 8 insertions(+)
> 
> diff --git a/documentation/ref-manual/variables.rst b/documentation/ref-manual/variables.rst
> index 66ecece8b2658b304e17c9c4a1492e42a8a313d4..50cd8948b35f381414837acc9b9e925dc5110779 100644
> --- a/documentation/ref-manual/variables.rst
> +++ b/documentation/ref-manual/variables.rst
> @@ -1231,6 +1231,14 @@ system and gives an overview of their function and contents.
>         :term:`Metadata` so it does not need to be parsed every time
>         BitBake is started.
>   
> +   :term:`CARGO_INSTALL_LIBRARIES`
> +      When inheriting the :ref:`ref-classes-cargo` class, the variable
> +      :term:`CARGO_INSTALL_LIBRARIES` can be set to a non-empty value by
> +      individual recipes to enable or disable installation of the libraries the

If I understood correctly the code, any non-empty value will enable the 
installation, so I suggest to remove "or disable" here.

> +      recipe has built in ``${B}/target`` (files ending with ``.so`` or

actually in ${B}/target/${CARGO_TARGET_SUBDIR} according to the code?

> +      ``.rlib``). By default this variable is not defined and libraries are not
> +      installed, to replicate the behavior of the ``cargo install`` command.
> +

Otherwise, looks good to me.

Cheers,
Quentin

[yocto-docs PATCH 13/14] ref-manual/variables: document the PREFERRED_RPROVIDER variable

[Antonin Godard]

This variable is similar to the PREFERRED_PROVIDER variable but it
denotes a runtime provider specifically.

Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
---
 documentation/ref-manual/variables.rst | 19 +++++++++++++++++++
 1 file changed, 19 insertions(+)

diff --git a/documentation/ref-manual/variables.rst b/documentation/ref-manual/variables.rst
index 50cd8948b35f381414837acc9b9e925dc5110779..e0b87c0e5ff8cf7bd2598cbbb184f9aada19d326 100644
--- a/documentation/ref-manual/variables.rst
+++ b/documentation/ref-manual/variables.rst
@@ -6711,6 +6711,25 @@ system and gives an overview of their function and contents.
    :term:`PREFERRED_PROVIDERS`
       See :term:`bitbake:PREFERRED_PROVIDERS` in the BitBake manual.
 
+   :term:`PREFERRED_RPROVIDER`
+      The :term:`PREFERRED_RPROVIDER` variable works like the
+      :term:`PREFERRED_PROVIDER` variable, but it denotes recipes that provide a
+      *runtime* component. Runtime providers are declared by recipes that set
+      the :term:`RPROVIDES` variable. For example::
+
+        PREFERRED_RPROVIDER_virtual-x-terminal-emulator = "rxvt-unicode"
+
+      This statement sets the runtime provider for the X terminal emulator to
+      ``rxvt-unicode``. The ``rxvt-unicode`` recipe is a runtime provider of
+      this component because it contains the following :term:`RPROVIDES`
+      definition::
+
+        RPROVIDES:${PN} = "virtual-x-terminal-emulator"
+
+      For more information on virtual providers, see the
+      ":ref:`dev-manual/new-recipe:using virtual providers`" section in the
+      Yocto Project Development Tasks Manual.
+
    :term:`PREFERRED_VERSION`
       If there are multiple versions of a recipe available, this variable
       determines which version should be given preference. You must always

-- 
2.47.1

Re: [docs] [yocto-docs PATCH 13/14] ref-manual/variables: document the PREFERRED_RPROVIDER variable

[Quentin Schulz]

Hi Antonin,

On 12/17/24 10:27 AM, Antonin Godard via lists.yoctoproject.org wrote:
> This variable is similar to the PREFERRED_PROVIDER variable but it
> denotes a runtime provider specifically.
> 
> Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
> ---
>   documentation/ref-manual/variables.rst | 19 +++++++++++++++++++
>   1 file changed, 19 insertions(+)
> 
> diff --git a/documentation/ref-manual/variables.rst b/documentation/ref-manual/variables.rst
> index 50cd8948b35f381414837acc9b9e925dc5110779..e0b87c0e5ff8cf7bd2598cbbb184f9aada19d326 100644
> --- a/documentation/ref-manual/variables.rst
> +++ b/documentation/ref-manual/variables.rst
> @@ -6711,6 +6711,25 @@ system and gives an overview of their function and contents.
>      :term:`PREFERRED_PROVIDERS`
>         See :term:`bitbake:PREFERRED_PROVIDERS` in the BitBake manual.
>   
> +   :term:`PREFERRED_RPROVIDER`
> +      The :term:`PREFERRED_RPROVIDER` variable works like the
> +      :term:`PREFERRED_PROVIDER` variable, but it denotes recipes that provide a
> +      *runtime* component. Runtime providers are declared by recipes that set
> +      the :term:`RPROVIDES` variable. For example::
> +
> +        PREFERRED_RPROVIDER_virtual-x-terminal-emulator = "rxvt-unicode"

Missing a whitespace for the alignment I believe (I believe we're 
three-whitespace aligned usually?). Ditto for the other code blocks below.

> +
> +      This statement sets the runtime provider for the X terminal emulator to
> +      ``rxvt-unicode``. The ``rxvt-unicode`` recipe is a runtime provider of
> +      this component because it contains the following :term:`RPROVIDES`
> +      definition::
> +
> +        RPROVIDES:${PN} = "virtual-x-terminal-emulator"
> +

We have to be very careful with the word recipe here. Above, it's the 
``rxvt-unicode`` package that is a runtime provider of 
virtual-x-terminal-emulator, because of the :${PN} override.

I assume PREFERRED_RPROVIDER_virtual-x-terminal-emulator should also 
contain the name of the package and not the recipe? That I am not 
entirely sure of though, haven't looked into the implementation of it.

Cheers,
Quentin

Re: [docs] [yocto-docs PATCH 13/14] ref-manual/variables: document the PREFERRED_RPROVIDER variable

[Antonin Godard]

Hi Quentin,

On Tue Dec 17, 2024 at 3:43 PM CET, Quentin Schulz wrote:
> Hi Antonin,
>
> On 12/17/24 10:27 AM, Antonin Godard via lists.yoctoproject.org wrote:
>> This variable is similar to the PREFERRED_PROVIDER variable but it
>> denotes a runtime provider specifically.
>> 
>> Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
>> ---
>>   documentation/ref-manual/variables.rst | 19 +++++++++++++++++++
>>   1 file changed, 19 insertions(+)
>> 
>> diff --git a/documentation/ref-manual/variables.rst b/documentation/ref-manual/variables.rst
>> index 50cd8948b35f381414837acc9b9e925dc5110779..e0b87c0e5ff8cf7bd2598cbbb184f9aada19d326 100644
>> --- a/documentation/ref-manual/variables.rst
>> +++ b/documentation/ref-manual/variables.rst
>> @@ -6711,6 +6711,25 @@ system and gives an overview of their function and contents.
>>      :term:`PREFERRED_PROVIDERS`
>>         See :term:`bitbake:PREFERRED_PROVIDERS` in the BitBake manual.
>>   
>> +   :term:`PREFERRED_RPROVIDER`
>> +      The :term:`PREFERRED_RPROVIDER` variable works like the
>> +      :term:`PREFERRED_PROVIDER` variable, but it denotes recipes that provide a
>> +      *runtime* component. Runtime providers are declared by recipes that set
>> +      the :term:`RPROVIDES` variable. For example::
>> +
>> +        PREFERRED_RPROVIDER_virtual-x-terminal-emulator = "rxvt-unicode"
>
> Missing a whitespace for the alignment I believe (I believe we're 
> three-whitespace aligned usually?). Ditto for the other code blocks below.
>
>> +
>> +      This statement sets the runtime provider for the X terminal emulator to
>> +      ``rxvt-unicode``. The ``rxvt-unicode`` recipe is a runtime provider of
>> +      this component because it contains the following :term:`RPROVIDES`
>> +      definition::
>> +
>> +        RPROVIDES:${PN} = "virtual-x-terminal-emulator"
>> +
>
> We have to be very careful with the word recipe here. Above, it's the 
> ``rxvt-unicode`` package that is a runtime provider of 
> virtual-x-terminal-emulator, because of the :${PN} override.
>
> I assume PREFERRED_RPROVIDER_virtual-x-terminal-emulator should also 
> contain the name of the package and not the recipe? That I am not 
> entirely sure of though, haven't looked into the implementation of it.

Well... the doc for PREFERRED_PROVIDER _and_ the code refers to these as neither
"packages" or "recipes", but "items". See the doc for PREFERRED_PROVIDER and
https://git.openembedded.org/bitbake/tree/lib/bb/providers.py#n323.

But as you said, the :${PN} override implies that a _package_ RPROVIDES
something, so we understand it the same way.

I will be more precise about this in the v2.


Antonin

-- 
Antonin Godard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

[yocto-docs PATCH 14/14] migration-guides: update the release notes for 5.2

[Antonin Godard]

Update the release note and migration guide for the 5.2 release. This
release is not due until April 2025, but this catches up what has
already been applied since 5.1.

Precisely, this tracks the important changes between commits
8149e74258 and 87d7341465 in poky.

Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
---
 documentation/migration-guides/migration-5.2.rst   |  50 +++
 .../migration-guides/release-notes-5.2.rst         | 345 ++++++++++++++++++++-
 2 files changed, 393 insertions(+), 2 deletions(-)

diff --git a/documentation/migration-guides/migration-5.2.rst b/documentation/migration-guides/migration-5.2.rst
index 7b35e7721fa74f51617fb5530987f62e9c74fed9..532f3942e4ac678c8afc2887b83f9296d1d26438 100644
--- a/documentation/migration-guides/migration-5.2.rst
+++ b/documentation/migration-guides/migration-5.2.rst
@@ -14,6 +14,28 @@ Migration notes for |yocto-ver| (|yocto-codename|)
 This section provides migration information for moving to the Yocto
 Project |yocto-ver| Release (codename "|yocto-codename|") from the prior release.
 
+``debug-tweaks`` removed from :term:`IMAGE_FEATURES`
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+The ``debug-tweaks`` image feature is now removed because it was too vague about
+what it achieved: an image on which the ``root`` user can login without a
+password.
+
+To achieve the same result, the features previously added by ``debug-tweaks``
+should be manually added to the :term:`IMAGE_FEATURES` variable. These are:
+
+-  ``allow-empty-password``
+-  ``allow-root-login``
+-  ``empty-root-password``
+-  ``post-install-logging``
+
+Such a statement would be::
+
+   IMAGE_FEATURES += "allow-empty-password allow-root-login empty-root-password post-install-logging"
+
+See the list of available image features in the :ref:`ref-features-image`
+section of the Yocto Project Reference Manual.
+
 Supported kernel versions
 ~~~~~~~~~~~~~~~~~~~~~~~~~
 
@@ -34,9 +56,24 @@ See :ref:`all supported distributions <system-requirements-supported-distros>`.
 Go language changes
 ~~~~~~~~~~~~~~~~~~~
 
+Rust language changes
+~~~~~~~~~~~~~~~~~~~~~
+
+-  Recipes inheriting the :ref:`ref-classes-cargo` do not install libraries by
+   default anymore. This behavior can be controlled by the
+   :term:`CARGO_INSTALL_LIBRARIES` variable.
+
 systemd changes
 ~~~~~~~~~~~~~~~
 
+-  Support for ``split-usr`` and ``unmerged-usr`` are now removed after Systemd
+   was updated to version 255. This option allowed installing Systemd in a
+   system where directories such as ``/lib``, ``/sbin`` or ``/bin`` are *not*
+   merged into ``/usr``.
+
+   As a consequence, the ``systemd`` recipe no longer contains the ``usrmerge``
+   :term:`PACKAGECONFIG` option as it is now implied by default.
+
 Recipe changes
 ~~~~~~~~~~~~~~
 
@@ -45,16 +82,29 @@ Removed variables
 
 The following variables have been removed:
 
+-  ``PACKAGE_SNAP_LIB_SYMLINKS``: related to an unmaintained and obsolete
+   "micro" :term:`distro <DISTRO>`.
+
+-  ``SETUPTOOLS_INSTALL_ARGS``: obsolete and unused variable.
+
 Removed recipes
 ~~~~~~~~~~~~~~~
 
 The following recipes have been removed in this release:
 
+-  ``liburi-perl``: moved to :oe_git:`meta-perl </meta-openembedded/tree/meta-perl>`.
+-  ``python3-isodate``: moved to :oe_git:`meta-python </meta-openembedded/tree/meta-python>`.
+-  ``python3-iniparse``: removed as there are no consumers of this recipe in
+   :oe_git:`openembedded-core </openembedded-core>` or :oe_git:`meta-openembedded </meta-openembedded>`.
+
 Removed classes
 ~~~~~~~~~~~~~~~
 
 The following classes have been removed in this release:
 
+-  ``migrate_localcount.bbclass``: obsolete class for which code was already
+   removed in 2012.
+
 Miscellaneous changes
 ~~~~~~~~~~~~~~~~~~~~~
 
diff --git a/documentation/migration-guides/release-notes-5.2.rst b/documentation/migration-guides/release-notes-5.2.rst
index d03ed7a3b07936fc3c2d15177f350b5507ecb5d4..0eef448330df0b3b3ec8a2c77cdb042a36e240c1 100644
--- a/documentation/migration-guides/release-notes-5.2.rst
+++ b/documentation/migration-guides/release-notes-5.2.rst
@@ -14,36 +14,377 @@ New Features / Enhancements in |yocto-ver|
 
 -  New variables:
 
+   -  ``linux-firmware``: Add the :term:`FIRMWARE_COMPRESSION` variable which
+      allows compression the firmwares provided by the ``linux-firmware`` recipe.
+      Possible values are ``xz`` and ``zst``.
+
 -  Kernel-related changes:
 
+   -  :ref:`ref-classes-cml1`: in :ref:`ref-tasks-diffconfig`, do not override
+      ``.config`` with ``.config.orig``. This applies to other recipes using the
+      class :ref:`ref-classes-cml1`.
+
+   -  ``linux-firmware``: add following new firmware packages:
+
+       -  ``qcom-qcm6490-audio``
+       -  ``qcom-qcm6490-compute``
+       -  ``qcom-adreno-a663``
+       -  ``qcom-qcm6490-adreno``
+       -  ``qcom-sa8775p-adreno``
+       -  ``qcom-qcm6490-ipa``
+       -  ``qcom-x1e80100-audio``
+       -  ``qcom-qcs615-adreno``
+
+   -  The :ref:`ref-classes-kernel-yocto` classes now supports in-tree
+      configuration fragments. These can be added with the
+      :term:`KERNEL_FEATURES` variable.
+
+   -  The ``kern-tools`` recipe is now able to recognize files ending with
+      ``.config`` for :ref:`ref-classes-kernel-yocto`-based Kernel recipes.
+
+   -  Support the LZMA compression algorithm in the
+      :ref:`ref-classes-kernel-uboot` class. This can be done by setting the
+      variable :term:`FIT_KERNEL_COMP_ALG` to ``lzma``.
+
 -  New core recipes:
 
+   -  ``python3-pefile``: required for the :ref:`ref-classes-uki` class.
+
+   -  Add initial support for the `Barebox <https://www.barebox.org>`__
+      bootloader, along with associated OEQA test cases.
+
+   -  Import ``makedumpfile`` from meta-openembedded, as the ``kexec-tools``
+      recipe :term:`RDEPENDS` on it.
+
+   -  The ``tcl-8`` recipe was added back to support the build of ``expect``.
+
+   -  Add the ``libdisplay-info`` recipe, an EDID and DisplayID library,
+      required for Weston 14.0.1 and newer.
+
+   -  The ``hwdata`` recipe was imported from :oe_git:`meta-openembedded
+      </meta-openembedded>`, a recipe for hardware identification and
+      configuration data, needed by ``libdisplay-info``.
+
+-  New core classes:
+
+   -  New :ref:`ref-classes-uki` class for building Unified Kernel Images (UKI).
+      Associated OEQA tests were also added for this class.
+
+   -  New :ref:`ref-classes-cython` class for python recipes that require Cython
+      for their compilation. Existing recipes depending on Cython now inherit
+      this class. This class also strips potential build paths in the compilation
+      output for reproducibility.
+
+-  Architecture-specific changes:
+
+   -  ``tune-cortexa32``: set tune feature to ``armv8a``.
+
 -  QEMU / ``runqemu`` changes:
 
+-  Documentation changes:
+
+   -  Use ``rsvg`` as a replacement of ``inkscape`` to convert svg files in the
+      documentation.
+
+   -  The ``cve`` role was replaced by ``cve_nist`` to avoid a conflict with
+      more recent version of Sphinx.
+
 -  Go changes:
 
+   -  The :ref:`ref-classes-go-mod` class now sets an internal variable
+      ``GO_MOD_CACHE_DIR`` to enable the use of the Go module fetchers for
+      downloading and unpacking module dependencies to the module cache.
+
+   -  Make the :ref:`ref-tasks-compile` task run before
+      :ref:`ref-tasks-populate_lic` in the :ref:`ref-classes-go-mod` class so
+      license files are found by :ref:`ref-tasks-populate_lic` after the ``go
+      install`` command is run in :ref:`ref-tasks-compile`.
+
 -  Rust changes:
 
--  wic Image Creator changes:
+   -  ``rust-target-config``: Update the data layout for the *x86-64* target, as
+      it was different in Rust from LLVM, which produced a data layout error.
+
+-  Wic Image Creator changes:
+
+   -  Allow the ``--exclude-path`` option to exclude symlinks.
+
+   -  Add the variable :term:`WIC_SECTOR_SIZE` to control the sector size of Wic
+      images.
 
 -  SDK-related changes:
 
+   -  Add support for ZST-compression through :term:`SDK_ARCHIVE_TYPE`, by
+      setting its value to ``tar.zst``.
+
+   -  The ``debug-tweaks`` features were removed from ``-sdk`` images
+      (``core-image-*-sdk.bb``).
+
+   -  Enable ``ipv6``, ``acl``, and ``xattr`` in :term:`DISTRO_FEATURES_NATIVESDK`.
+
 -  Testing-related changes:
 
+   -  ``oeqa/postactions``: Fix archive retrieval from target.
+
+   -  ``oeqa/selftest/gcc``: Fix kex exchange identification error.
+
+   -  ``oeqa/utils/qemurunner``: support ignoring vt100 escape sequences.
+
+   -  ``oeqa``: support passing custom boot patterns to runqemu.
+
+   -  ``oeqa/selftest/cases``: add basic U-boot and Barebox tests.
+
+   -  ``oeqa/selftest/rust``: skip on all MIPS platforms.
+
+   -  Lots of changes and improvements to the :term:`Toaster` OEQA tests.
+
+   -  ``oeqa/selftest``: add a test for bitbake "-e" and "-getvar" difference.
+
+   -  ``oeqa/ssh``: improve performance and log sizes when handling large files.
+
 -  Utility script changes:
 
+   -  The ``patchreview.py`` script now uses the ``check_upstream_status`` from
+      ``oe.qa`` to get patch statuses.
+
+   -  ``resulttool``:
+
+      -  Allow store to filter to specific revisions (``--revision`` flag).
+
+      -  Use single space indentation in JSON output, to save disk
+         space.
+
+      -  Add ``--logfile-archive`` option to store and archive log files
+         separately.
+
+      -  Handle LTP raw logs as well as Ptest.
+
+   -  ``scripts/yocto-check-layer``:
+
+      -  Check for the presence of a ``SECURITY.md`` file in layers and make it
+         mandatory.
+
+      -  The :ref:`ref-classes-yocto-check-layer` class now uses
+         :term:`CHECKLAYER_REQUIRED_TESTS` to get the list of QA checks to verify
+         when running the ``yocto-check-layer`` script.
+
 -  BitBake changes:
 
+   -  ``fetch2``: do not preserve ownership when unpacking.
+
+   -  ``fetch2``: switch from Sqlite ``persist_data`` to a standard cache file
+      for checksums, and drop ``persist_data``.
+
+   -  ``fetch2``: add support for GitHub codespaces by adding the
+      ``GITHUB_TOKEN`` to the list of variables exported during ``git``
+      invocations.
+
+   -  ``fetch2``: set User-Agent to 'bitbake/version' instead of a "fake
+      mozilla" user agent.
+
+   -  ``compress``: use ``lz4`` instead of ``lz4c``, as ``lz4c`` as been
+      considered deprecrated since 2018.
+
+   -  ``server/process``: decrease idle/main loop frequency, as it is idle and
+      main loops have socket select calls to know when to execute.
+
+   -  ``bitbake-worker``: improve bytearray truncation performance when large
+       amounts of data are being transferred from the cooker to the worker.
+
+   -  ``bitbake-worker/cooker``: increase the default pipe size from 64KB to
+      512KB for better efficiency when transferring large amounts of data.
+
+   -  ``fetch/wget``: increase timeout to 100s from 30s to match CDN worst
+      response time.
+
+   -  ``bitbake-getvar``: catch ``NoProvider`` exception to improve error
+      readability when a recipe is not found with ``--recipe``.
+
+   -  ``bb/build``: add a function ``bb.build.listtasks()`` to list the tasks in
+      a datastore.
+
+   -  Remove custom exception backtrace formatting, and replace occurences of
+      ``bb.exception.format_exception()`` by ``traceback.format_exception()``.
+
+   -  ``runqueue``: various performance optimizations including:
+
+      -  Fix performance of multiconfigs with large overlap.
+      -  Optimise ``setscene`` loop processing by starting where it
+         was left off in the previous execution.
+
+   -  ``knotty`` now hints the user if :term:`MACHINE` was not set in
+      the ``local.conf`` file.
+
 -  Packaging changes:
 
--  Security changes:
+   -  ``systemd``: extract dependencies from ``.note.dlopen`` ELF segments, to
+      better detect dynamically linked libraries at runtime.
+
+   -  ``package_rpm``: use ZSTD's default compression level from the variable
+      :term:`ZSTD_COMPRESSION_LEVEL`.
+
+   -  ``package_rpm``: restrict RPM packaging to 4 threads to improve
+      the compression speed.
 
 -  LLVM related changes:
 
 -  SPDX-related changes:
 
+   -  SPDX 3.0: Find local sources when searching for debug sources.
+
+   -  SPDX 3.0: Map ``gitsm`` URIs to ``git``.
+
+   -  SPDX 3.0: Link license and build by alias instead of SPDX ID.
+
+   -  Fix SPDX tasks not running when code changes (use of ``file-checksums``).
+
+-  ``devtool`` changes:
+
+   -  Remove the "S = WORKDIR" workaround as now :term:`S` cannot be equal to
+      :term:`WORKDIR`.
+
+-  Patchtest-related changes:
+
+   -  Refactor pattern definitions in a ``patterns`` module.
+
+   -  Refactor and improve the ``mbox`` module.
+
+   -  Split out result messages.
+
+   -  Add a check for user name tags in patches (for example "fix added by
+      @username").
+
+-  :ref:`ref-classes-insane` class related changes:
+
+   -  Only parse ELF if they are files and not symlinks.
+
+   -  Check for ``RUNPATH`` in addition to ``RPATH`` in binaries.
+
+   -  Ensure :ref:`ref-classes-insane` tasks of dependencies run in builds when
+      expected.
+
+-  Security changes:
+
+   -  The ``PIE`` gcc flag is now passed for the *powerpc* architecture after a
+      bugfix in gcc (https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81170).
+
+   -  ``openssh``: be more restrictive on private key file permissions by
+      setting them from the :ref:`ref-tasks-install` task.
+
+-  :ref:`ref-classes-cve-check` changes:
+
+   -  Update the :term:`DL_DIR` database location name
+      (``${DL_DIR}/CVE_CHECK2``).
+
+   -  Add the field "modified" to the JSON report (from "NVD-modified").
+
+   -  Add support for CVSS v4.0.
+
+   -  Fix malformed cve status description with ``:`` characters.
+
+   -  Restore the :term:`CVE_CHECK_SHOW_WARNINGS` variable and functionality. It
+      currently prints warning message for every unpatched CVE the
+      :ref:`ref-classes-cve-check` class finds.
+
+-  New :term:`PACKAGECONFIG` options for individual recipes:
+
+      -  ``perf``: ``zstd``
+      -  ``ppp``: ``pam``, ``openssl``
+      -  ``libpciaccess``: ``zlib``
+      -  ``gdk-pixbuf``: ``gif``, ``others``
+      -  ``libpam``: ``selinux``
+      -  ``libsecret``: ``pam``
+
 -  Miscellaneous changes:
 
+   -  ``bluez``: fix mesh build when building with musl.
+
+   -  ``systemd-bootchart``: now supports the 32-bit *riscv* architecture.
+
+   -  ``systemd-boot``: now supports the *riscv* architecture.
+
+   -  ``python3-pip``: the ``pip`` executable is now left and not deleted, and
+      can be used instead of ``pip3`` and ``pip2``.
+
+   -  ``tar`` image types are now more reproducible as the :term:`IMAGE_CMD` for
+      ``tar`` now strips ``atime`` and ``ctime`` from the archive content.
+
+   -  :term:`SOLIBSDEV` and :term:`SOLIBS` are now defined for the *mingw32*
+      architecture (``.dll``).
+
+   -  :ref:`rootfs-postcommands <ref-classes-rootfs*>`: make opkg status reproducible.
+
+   -  The default :term:`KERNEL_CONSOLE` value is no longer ``ttyS0`` but the
+      first entry from the :term:`SERIAL_CONSOLES` variable.
+
+   -  ``virglrenderer``: add a patch to fix ``-int-conversion`` build issue.
+
+   -  ``ffmpeg``: disable asm optimizations for the *x86* architecture as PIC is
+      required and *x86* ASM code is not PIC.
+
+   -  ``udev-extraconf``: fix the ``network.sh`` script that did not configure
+      hotplugged interfaces.
+
+   -  ``classes-global/license``: move several functions and logic to library
+      code in :oe_git:`meta/lib/oe/license.py </openembedded-core/tree/meta/lib/oe/license.py>`.
+
+   -  The recipe ``cairo`` now disables the features ``symbol-lookup``,
+      ``spectre`, and ``tests`` by default.
+
+   -  The recipe ``glib-2.0`` now disables the feature ``sysprof`` by default.
+
+   -  The recipe ``gstreamer1.0-libav`` now disables the feature ``doc`` by default.
+
+   -  ``rxvt-unicode``: change ``virtual/x-terminal-emulator`` from
+      :term:`PROVIDES` to :term:`RPROVIDES` as ``virtual-x-terminal-emulator``.
+      Also make this recipe depend on the ``x11`` distro features with
+      :term:`REQUIRED_DISTRO_FEATURES`.
+
+   -  ``rxvt-unicode.inc``: disable the ``terminfo`` installation by setting
+      ``TIC`` to ``:`` in :term:`EXTRA_OECONF`, to avoid host contamination.
+
+   -  ``matchbox-terminal``: add ``x-terminal-emulator`` as :term:`RPROVIDES`
+      and set :term:`ALTERNATIVE` for the recipe.
+
+   -  ``default-providers.conf``: set ``rxvt-unicode`` as the default
+      ``virtual-x-terminal-emulator`` runtime provider with
+      :term:`PREFERRED_RPROVIDER`.
+
+   -  ``systemd``: set better sane time at startup by creating the
+      ``clock-epoch`` file in ``${libdir}`` if the ``set-time-epoch``
+      :term:`PACKAGECONFIG` config is set.
+
+   -  ``cve-update-nvd2-native``: updating the database will now result in an
+      error if :term:`BB_NO_NETWORK` is enabled and
+      :term:`CVE_DB_UPDATE_INTERVAL` is not set to ``-1``.
+
+   -  ``systemtap``: add ``--with-extra-version="oe"`` configure option to
+      improve the reproducibility of the recipe.
+
+   -  ``python3``: package ``tkinter``'s shared objects separately in the
+      ``python3-tkinter`` package.
+
+   -  ``init-manager``: set the variable ``VIRTUAL-RUNTIME_dev_manager`` to
+      ``udev`` by default in
+      :oe_git:`meta/conf/distro/include/init-manager-none.inc
+      </openembedded-core/tree/meta/conf/distro/include/init-manager-none.inc>`
+      and :oe_git:`meta/conf/distro/include/init-manager-sysvinit.inc
+      </openembedded-core/tree/meta/conf/distro/include/init-manager-sysvinit.inc>`,
+      instead of :oe_git:`meta/recipes-core/packagegroups/packagegroup-core-boot.bb
+      </openembedded-core/tree/meta/recipes-core/packagegroups/packagegroup-core-boot.bb>`
+      only.
+
+      Likewise, the same is done for ``VIRTUAL-RUNTIME_keymaps`` with
+      ``keymaps`` as its default value.
+
+   -  ``seatd``: Create a ``seat`` group and package the systemd service
+      ``seatd.service`` with correct permissions.
+
+      That way, the ``weston`` user in ``weston-init.bb`` was added to the
+      ``seat`` group to be able to properly establish connection between the
+      Weston and the ``seatd`` socket.
+
+
 Known Issues in |yocto-ver|
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~
 

-- 
2.47.1