[PATCH v2 00/12] Updates for upcoming 5.2 release

[PATCH v2 00/12] Updates for upcoming 5.2 release

[Antonin Godard]

First series of patches documents the missing or deprecated bits of
documentation.

The last two patches update the release note and migration guide for
5.2.

Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
---
Changes in v2:
- New patch "ref-manual/variables.rst: document autotools class related
  variables".
- Add an item in the migration guide on recipe inheriting autotools now
  requiring a configure script.
- Add minimum Python version required on the host in the release note.
- Mention that users can choose the NVD database source in the beginning
  of the release note (thanks Marta for the suggestion).
- Various additions to the release note after documenting a bit more
  commits from Poky's master branch.
- Fix some indentation issues in the release note.
- Link to v1: https://lore.kernel.org/r/20250317-release-note-5-2-updates-v1-0-82b0a4182aff@bootlin.com

---
Antonin Godard (12):
      ref-manual/classes.rst: document the ptest-python-pytest class and variables
      ref-manual/variables.rst: WATCHDOG_TIMEOUT: fix recipe name
      ref-manual/variables.rst: document the WATCHDOG_RUNTIME_SEC variable
      ref-manual/variables.rst: document the MOUNT_GROUP variable
      ref-manual/features.rst: drop ld-is-gold
      ref-manual/variables.rst: document the MESON_INSTALL_TAGS
      ref-manual/variables.rst: document the NVD_DB_VERSION variable
      ref-manual/variables.rst: document autotools class related variables
      migration-guides/migration-5.2.rst: add information about autotools changes
      ref-manual/variables.rst: add a link for BB_USE_HOME_NPMRC
      migration-guides/migration-5.2: update for upcoming 5.2 release
      migration-guides/release-notes-5.2: update for upcoming 5.2 release

 documentation/migration-guides/migration-5.2.rst   |  57 ++++
 .../migration-guides/release-notes-5.2.rst         | 354 ++++++++++++++++++---
 documentation/ref-manual/classes.rst               |  15 +
 documentation/ref-manual/features.rst              |   3 -
 documentation/ref-manual/variables.rst             |  60 +++-
 5 files changed, 448 insertions(+), 41 deletions(-)
---
base-commit: ee6b3698da044e290dbc4fbb852f3cc37638e689
change-id: 20250225-release-note-5-2-updates-d32951d23978

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

[PATCH v2 01/12] ref-manual/classes.rst: document the ptest-python-pytest class and variables

[Antonin Godard]

Add documentation for the ptest-python-pytest class, and the
PTEST_PYTEST_DIR variable which can be overriden.

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

diff --git a/documentation/ref-manual/classes.rst b/documentation/ref-manual/classes.rst
index 6797927fe..8b930fe3d 100644
--- a/documentation/ref-manual/classes.rst
+++ b/documentation/ref-manual/classes.rst
@@ -2707,6 +2707,21 @@ For information on setting up and running ptests, see the
 ":ref:`test-manual/ptest:testing packages with ptest`"
 section in the Yocto Project Development Tasks Manual.
 
+.. _ref-classes-ptest-python-pytest:
+
+``ptest-python-pytest``
+=======================
+
+The :ref:`ref-classes-ptest-python-pytest` class can be used in Python-based
+recipes to automatically configure the :ref:`ref-classes-ptest` class for Python
+packages leveraging the `pytest <https://docs.pytest.org>`__ unit test framework.
+
+Within the recipe, the :term:`PTEST_PYTEST_DIR` variable can be overridden to
+specify the path to the directory containing the tests (default value:
+``tests``). Test contained in this directory are installed in :term:`D` by the
+:ref:`ref-tasks-install_ptest_base` task, as well as a specific ``run-ptest``
+script for this task.
+
 .. _ref-classes-python3-dir:
 
 ``python3-dir``
diff --git a/documentation/ref-manual/variables.rst b/documentation/ref-manual/variables.rst
index 41bda5d0d..8e0833bff 100644
--- a/documentation/ref-manual/variables.rst
+++ b/documentation/ref-manual/variables.rst
@@ -7110,6 +7110,16 @@ system and gives an overview of their function and contents.
       at build time should be done by adding "ptest" to (or removing it
       from) :term:`DISTRO_FEATURES`.
 
+   :term:`PTEST_PYTEST_DIR`
+      Within the :ref:`ref-classes-ptest-python-pytest` class, the
+      :term:`PTEST_PYTEST_DIR` variable represents the path within the source
+      tree of a Python package holding the unit tests to be tested with the
+      `pytest <https://docs.pytest.org>`__ framework. The default value for this
+      variable is ``tests``.
+
+      For more information, see
+      the :ref:`ref-classes-ptest-python-pytest` class documentation.
+
    :term:`PV`
       The version of the recipe. The version is normally extracted from the
       recipe filename. For example, if the recipe is named

-- 
2.47.0

Re: [docs] [PATCH v2 01/12] ref-manual/classes.rst: document the ptest-python-pytest class and variables

[Quentin Schulz]

Hi Antonin,

On 3/25/25 10:20 AM, Antonin Godard via lists.yoctoproject.org wrote:
> Add documentation for the ptest-python-pytest class, and the
> PTEST_PYTEST_DIR variable which can be overriden.
> 
> Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
> ---
>   documentation/ref-manual/classes.rst   | 15 +++++++++++++++
>   documentation/ref-manual/variables.rst | 10 ++++++++++
>   2 files changed, 25 insertions(+)
> 
> diff --git a/documentation/ref-manual/classes.rst b/documentation/ref-manual/classes.rst
> index 6797927fe..8b930fe3d 100644
> --- a/documentation/ref-manual/classes.rst
> +++ b/documentation/ref-manual/classes.rst
> @@ -2707,6 +2707,21 @@ For information on setting up and running ptests, see the
>   ":ref:`test-manual/ptest:testing packages with ptest`"
>   section in the Yocto Project Development Tasks Manual.
>   
> +.. _ref-classes-ptest-python-pytest:
> +
> +``ptest-python-pytest``
> +=======================
> +
> +The :ref:`ref-classes-ptest-python-pytest` class can be used in Python-based

s/used/inherited/ ?

> +recipes to automatically configure the :ref:`ref-classes-ptest` class for Python
> +packages leveraging the `pytest <https://docs.pytest.org/>`__ unit test framework.
> +
> +Within the recipe, the :term:`PTEST_PYTEST_DIR` variable can be overridden to
> +specify the path to the directory containing the tests (default value:
> +``tests``). Test contained in this directory are installed in :term:`D` by the

"""
Within the recipe, the :term:`PTEST_PYTEST_DIR` variable specifies the 
path to the directory containing the tests that will be installed in 
:term:`D` by the [...].
"""

1) Try to avoid having a default in multiple locations in the docs, so 
we only need to change it in one place if it ever changes.
2) No need to say overridden, it's a variable, it's implied it can be 
overridden.

> +:ref:`ref-tasks-install_ptest_base` task, as well as a specific ``run-ptest``
> +script for this task.
> +
>   .. _ref-classes-python3-dir:
>   
>   ``python3-dir``
> diff --git a/documentation/ref-manual/variables.rst b/documentation/ref-manual/variables.rst
> index 41bda5d0d..8e0833bff 100644
> --- a/documentation/ref-manual/variables.rst
> +++ b/documentation/ref-manual/variables.rst
> @@ -7110,6 +7110,16 @@ system and gives an overview of their function and contents.
>         at build time should be done by adding "ptest" to (or removing it
>         from) :term:`DISTRO_FEATURES`.
>   
> +   :term:`PTEST_PYTEST_DIR`
> +      Within the :ref:`ref-classes-ptest-python-pytest` class, the
> +      :term:`PTEST_PYTEST_DIR` variable represents the path within the source
> +      tree of a Python package holding the unit tests to be tested with the

s/tested/run/ ?

Looks good otherwise.

Cheers,
Quentin

Re: [docs] [PATCH v2 01/12] ref-manual/classes.rst: document the ptest-python-pytest class and variables

[Antonin Godard]

Hi Quentin,

On Fri Mar 28, 2025 at 2:58 PM CET, Quentin Schulz wrote:
> Hi Antonin,
>
> On 3/25/25 10:20 AM, Antonin Godard via lists.yoctoproject.org wrote:
>> Add documentation for the ptest-python-pytest class, and the
>> PTEST_PYTEST_DIR variable which can be overriden.
>> 
>> Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
>> ---
>>   documentation/ref-manual/classes.rst   | 15 +++++++++++++++
>>   documentation/ref-manual/variables.rst | 10 ++++++++++
>>   2 files changed, 25 insertions(+)
>> 
>> diff --git a/documentation/ref-manual/classes.rst b/documentation/ref-manual/classes.rst
>> index 6797927fe..8b930fe3d 100644
>> --- a/documentation/ref-manual/classes.rst
>> +++ b/documentation/ref-manual/classes.rst
>> @@ -2707,6 +2707,21 @@ For information on setting up and running ptests, see the
>>   ":ref:`test-manual/ptest:testing packages with ptest`"
>>   section in the Yocto Project Development Tasks Manual.
>>   
>> +.. _ref-classes-ptest-python-pytest:
>> +
>> +``ptest-python-pytest``
>> +=======================
>> +
>> +The :ref:`ref-classes-ptest-python-pytest` class can be used in Python-based
>
> s/used/inherited/ ?
>
>> +recipes to automatically configure the :ref:`ref-classes-ptest` class for Python
>> +packages leveraging the `pytest <https://docs.pytest.org/>`__ unit test framework.
>> +
>> +Within the recipe, the :term:`PTEST_PYTEST_DIR` variable can be overridden to
>> +specify the path to the directory containing the tests (default value:
>> +``tests``). Test contained in this directory are installed in :term:`D` by the
>
> """
> Within the recipe, the :term:`PTEST_PYTEST_DIR` variable specifies the 
> path to the directory containing the tests that will be installed in 
> :term:`D` by the [...].
> """
>
> 1) Try to avoid having a default in multiple locations in the docs, so 
> we only need to change it in one place if it ever changes.

Right, I'll remove the default value, thanks.

> 2) No need to say overridden, it's a variable, it's implied it can be 
> overridden.

True, in this context, you can override it after inheriting the class. Some
variables are harder to override when they are assigned with the = operator,
especially for global classes.

Usually, I consider the ones assigned with ?= to be the "overrideable" ones. But
it's true that in this case, it's not super relevant.

>
>> +:ref:`ref-tasks-install_ptest_base` task, as well as a specific ``run-ptest``
>> +script for this task.
>> +
>>   .. _ref-classes-python3-dir:
>>   
>>   ``python3-dir``
>> diff --git a/documentation/ref-manual/variables.rst b/documentation/ref-manual/variables.rst
>> index 41bda5d0d..8e0833bff 100644
>> --- a/documentation/ref-manual/variables.rst
>> +++ b/documentation/ref-manual/variables.rst
>> @@ -7110,6 +7110,16 @@ system and gives an overview of their function and contents.
>>         at build time should be done by adding "ptest" to (or removing it
>>         from) :term:`DISTRO_FEATURES`.
>>   
>> +   :term:`PTEST_PYTEST_DIR`
>> +      Within the :ref:`ref-classes-ptest-python-pytest` class, the
>> +      :term:`PTEST_PYTEST_DIR` variable represents the path within the source
>> +      tree of a Python package holding the unit tests to be tested with the
>
> s/tested/run/ ?

Indeed!

> Looks good otherwise.

Thanks,
Antonin

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

[PATCH v2 02/12] ref-manual/variables.rst: WATCHDOG_TIMEOUT: fix recipe name

[Antonin Godard]

This variable affects the watchdog-config recipe, not the watchdog
recipe.

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

diff --git a/documentation/ref-manual/variables.rst b/documentation/ref-manual/variables.rst
index 8e0833bff..ee7244dc5 100644
--- a/documentation/ref-manual/variables.rst
+++ b/documentation/ref-manual/variables.rst
@@ -10614,8 +10614,8 @@ system and gives an overview of their function and contents.
       ":ref:`ref-classes-insane`" section.
 
    :term:`WATCHDOG_TIMEOUT`
-      Specifies the timeout in seconds used by the ``watchdog`` recipe and
-      also by ``systemd`` during reboot. The default is 60 seconds.
+      Specifies the timeout in seconds used by the ``watchdog-config`` 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

-- 
2.47.0

Re: [docs] [PATCH v2 02/12] ref-manual/variables.rst: WATCHDOG_TIMEOUT: fix recipe name

[Quentin Schulz]

Hi Antonin,

On 3/25/25 10:20 AM, Antonin Godard via lists.yoctoproject.org wrote:
> This variable affects the watchdog-config recipe, not the watchdog
> recipe.
> 

Good catch, this was introduced in 4.1 (langdale) so can be backported 
back to that release.

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

Thanks!
Quentin

[PATCH v2 03/12] ref-manual/variables.rst: document the WATCHDOG_RUNTIME_SEC variable

[Antonin Godard]

This variable controls the RuntimeWatchdogSec option in
/etc/systemd/system.conf.

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

diff --git a/documentation/ref-manual/variables.rst b/documentation/ref-manual/variables.rst
index ee7244dc5..70ed7db4d 100644
--- a/documentation/ref-manual/variables.rst
+++ b/documentation/ref-manual/variables.rst
@@ -10613,6 +10613,11 @@ system and gives an overview of their function and contents.
       can control with this variable, see the
       ":ref:`ref-classes-insane`" section.
 
+   :term:`WATCHDOG_RUNTIME_SEC`
+      For the ``systemd`` recipe, this controls the value of the
+      ``RuntimeWatchdogSec`` option in ``/etc/systemd/system.conf``. The default
+      value is an empty string.
+
    :term:`WATCHDOG_TIMEOUT`
       Specifies the timeout in seconds used by the ``watchdog-config`` recipe
       and also by ``systemd`` during reboot. The default is 60 seconds.

-- 
2.47.0

Re: [docs] [PATCH v2 03/12] ref-manual/variables.rst: document the WATCHDOG_RUNTIME_SEC variable

[Quentin Schulz]

Hi Antonin,

On 3/25/25 10:20 AM, Antonin Godard via lists.yoctoproject.org wrote:
> This variable controls the RuntimeWatchdogSec option in
> /etc/systemd/system.conf.
> 
> Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
> ---
>   documentation/ref-manual/variables.rst | 5 +++++
>   1 file changed, 5 insertions(+)
> 
> diff --git a/documentation/ref-manual/variables.rst b/documentation/ref-manual/variables.rst
> index ee7244dc5..70ed7db4d 100644
> --- a/documentation/ref-manual/variables.rst
> +++ b/documentation/ref-manual/variables.rst
> @@ -10613,6 +10613,11 @@ system and gives an overview of their function and contents.
>         can control with this variable, see the
>         ":ref:`ref-classes-insane`" section.
>   
> +   :term:`WATCHDOG_RUNTIME_SEC`
> +      For the ``systemd`` recipe, this controls the value of the
> +      ``RuntimeWatchdogSec`` option in ``/etc/systemd/system.conf``. The default

How about adding a path to the documentation of that option?

e.g. 
https://www.freedesktop.org/software/systemd/man/latest/systemd-system.conf.html#RuntimeWatchdogSec= 
?

> +      value is an empty string.
> +

meaning it is disabled.

Cheers,
Quentin

[PATCH v2 04/12] ref-manual/variables.rst: document the MOUNT_GROUP variable

[Antonin Godard]

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

diff --git a/documentation/ref-manual/variables.rst b/documentation/ref-manual/variables.rst
index 70ed7db4d..b872d7935 100644
--- a/documentation/ref-manual/variables.rst
+++ b/documentation/ref-manual/variables.rst
@@ -5739,6 +5739,11 @@ system and gives an overview of their function and contents.
       specifies the base directory for auto-mounting filesystems. The
       default value is "/run/media".
 
+   :term:`MOUNT_GROUP`
+      On non-systemd systems (where ``udev-extraconf`` is being used),
+      specifies the mount group for auto-mounting filesystems. The
+      default value is "disk".
+
    :term:`MULTIMACH_TARGET_SYS`
       Uniquely identifies the type of the target system for which packages
       are being built. This variable allows output for different types of

-- 
2.47.0

[PATCH v2 05/12] ref-manual/features.rst: drop ld-is-gold

[Antonin Godard]

Dropped in OE-Core after commit a4addb9ab630 ("recipes: Drop ld-is-gold
support").

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

diff --git a/documentation/ref-manual/features.rst b/documentation/ref-manual/features.rst
index 746d6337e..2c074ab9c 100644
--- a/documentation/ref-manual/features.rst
+++ b/documentation/ref-manual/features.rst
@@ -167,9 +167,6 @@ metadata, as extra layers can define their own:
 -  *multiarch:* Enable building applications with multiple architecture
    support.
 
--  *ld-is-gold:* Use the :wikipedia:`gold <Gold_(linker)>`
-   linker instead of the standard GCC linker (bfd).
-
 -  *ldconfig:* Include support for ldconfig and ``ld.so.conf`` on the
    target.
 

-- 
2.47.0

[PATCH v2 06/12] ref-manual/variables.rst: document the MESON_INSTALL_TAGS

[Antonin Godard]

This variable can be used to add install tags to the 'meson install'
command.

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

diff --git a/documentation/ref-manual/variables.rst b/documentation/ref-manual/variables.rst
index b872d7935..d5fec650c 100644
--- a/documentation/ref-manual/variables.rst
+++ b/documentation/ref-manual/variables.rst
@@ -5601,6 +5601,10 @@ system and gives an overview of their function and contents.
       you to specify the inclusion of debugging symbols and the compiler
       optimizations (none, performance or size).
 
+   :term:`MESON_INSTALL_TAGS`
+      A variable for the :ref:`ref-classes-meson` class, allowing to specify
+      install tags (``--tags`` argument of the ``meson install`` command).
+
    :term:`MESON_TARGET`
       A variable for the :ref:`ref-classes-meson` class, allowing to choose
       a Meson target to build in :ref:`ref-tasks-compile`.  Otherwise, the

-- 
2.47.0

Re: [docs] [PATCH v2 06/12] ref-manual/variables.rst: document the MESON_INSTALL_TAGS

[Quentin Schulz]

Hi Antonin,

On 3/25/25 10:20 AM, Antonin Godard via lists.yoctoproject.org wrote:
> This variable can be used to add install tags to the 'meson install'
> command.
> 
> Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
> ---
>   documentation/ref-manual/variables.rst | 4 ++++
>   1 file changed, 4 insertions(+)
> 
> diff --git a/documentation/ref-manual/variables.rst b/documentation/ref-manual/variables.rst
> index b872d7935..d5fec650c 100644
> --- a/documentation/ref-manual/variables.rst
> +++ b/documentation/ref-manual/variables.rst
> @@ -5601,6 +5601,10 @@ system and gives an overview of their function and contents.
>         you to specify the inclusion of debugging symbols and the compiler
>         optimizations (none, performance or size).
>   
> +   :term:`MESON_INSTALL_TAGS`
> +      A variable for the :ref:`ref-classes-meson` class, allowing to specify
> +      install tags (``--tags`` argument of the ``meson install`` command).
> +

We could provide a link here too, e.g. 
https://mesonbuild.com/Installing.html#installation-tags

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

Thanks!
Quentin

[PATCH v2 07/12] ref-manual/variables.rst: document the NVD_DB_VERSION variable

[Antonin Godard]

This variable allows choosing the CVE feed when using the cve-check
class.

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

diff --git a/documentation/ref-manual/variables.rst b/documentation/ref-manual/variables.rst
index d5fec650c..597b0d031 100644
--- a/documentation/ref-manual/variables.rst
+++ b/documentation/ref-manual/variables.rst
@@ -5853,6 +5853,18 @@ system and gives an overview of their function and contents.
 
          NON_MULTILIB_RECIPES = "grub grub-efi make-mod-scripts ovmf u-boot"
 
+   :term:`NVD_DB_VERSION`
+      The :term:`NVD_DB_VERSION` variable allows choosing the CVE feed when
+      using the :ref:`ref-classes-cve-check` class. It can be one of:
+
+      -  ``NVD2`` (default): the NVD feed with API version 2
+      -  ``FKIE``: the `FKIE-CAD <https://github.com/fkie-cad/nvd-json-data-feeds>`__
+         feed reconstruction
+      -  ``NVD1``: the NVD JSON feed (deprecated)
+
+      In case of a malformed feed name, the ``NVD2`` feed is selected and an
+      error is printed.
+
    :term:`NVDCVE_API_KEY`
       The NVD API key used to retrieve data from the CVE database when
       using :ref:`ref-classes-cve-check`.

-- 
2.47.0

[PATCH v2 08/12] ref-manual/variables.rst: document autotools class related variables

[Antonin Godard]

Document the AUTOTOOLS_SCRIPT_PATH and the CONFIGURE_SCRIPT variables.

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

diff --git a/documentation/ref-manual/variables.rst b/documentation/ref-manual/variables.rst
index 597b0d031..e9e8a6933 100644
--- a/documentation/ref-manual/variables.rst
+++ b/documentation/ref-manual/variables.rst
@@ -224,6 +224,12 @@ system and gives an overview of their function and contents.
       must set this variable in your recipe. The
       :ref:`ref-classes-syslinux` class checks this variable.
 
+   :term:`AUTOTOOLS_SCRIPT_PATH`
+      When using the :ref:`ref-classes-autotools` class, the
+      :term:`AUTOTOOLS_SCRIPT_PATH` variable stores the location of the
+      different scripts used by the Autotools build system. The default
+      value for this variable is :term:`S`.
+
    :term:`AVAILTUNES`
       The list of defined CPU and Application Binary Interface (ABI)
       tunings (i.e. "tunes") available for use by the OpenEmbedded build
@@ -1528,6 +1534,17 @@ system and gives an overview of their function and contents.
    :term:`CONFIGURE_FLAGS`
       The minimal arguments for GNU configure.
 
+   :term:`CONFIGURE_SCRIPT`
+      When using the :ref:`ref-classes-autotools` class, the
+      :term:`CONFIGURE_SCRIPT` variable stores the location of the ``configure``
+      script for the Autotools build system. The default definition for this
+      variable is::
+
+         CONFIGURE_SCRIPT ?= "${AUTOTOOLS_SCRIPT_PATH}/configure"
+
+      Where :term:`AUTOTOOLS_SCRIPT_PATH` is the location of the of the
+      Autotools build system scripts, which defaults to :term:`S`.
+
    :term:`CONFLICT_DISTRO_FEATURES`
       When inheriting the :ref:`ref-classes-features_check`
       class, this variable identifies distribution features that would be

-- 
2.47.0

Re: [docs] [PATCH v2 08/12] ref-manual/variables.rst: document autotools class related variables

[Quentin Schulz]

Hi Antonin,

On 3/25/25 10:20 AM, Antonin Godard via lists.yoctoproject.org wrote:
> Document the AUTOTOOLS_SCRIPT_PATH and the CONFIGURE_SCRIPT variables.
> 
> Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
> ---
>   documentation/ref-manual/variables.rst | 17 +++++++++++++++++
>   1 file changed, 17 insertions(+)
> 
> diff --git a/documentation/ref-manual/variables.rst b/documentation/ref-manual/variables.rst
> index 597b0d031..e9e8a6933 100644
> --- a/documentation/ref-manual/variables.rst
> +++ b/documentation/ref-manual/variables.rst
> @@ -224,6 +224,12 @@ system and gives an overview of their function and contents.
>         must set this variable in your recipe. The
>         :ref:`ref-classes-syslinux` class checks this variable.
>   
> +   :term:`AUTOTOOLS_SCRIPT_PATH`
> +      When using the :ref:`ref-classes-autotools` class, the
> +      :term:`AUTOTOOLS_SCRIPT_PATH` variable stores the location of the
> +      different scripts used by the Autotools build system. The default
> +      value for this variable is :term:`S`.
> +
>      :term:`AVAILTUNES`
>         The list of defined CPU and Application Binary Interface (ABI)
>         tunings (i.e. "tunes") available for use by the OpenEmbedded build
> @@ -1528,6 +1534,17 @@ system and gives an overview of their function and contents.
>      :term:`CONFIGURE_FLAGS`
>         The minimal arguments for GNU configure.
>   
> +   :term:`CONFIGURE_SCRIPT`
> +      When using the :ref:`ref-classes-autotools` class, the
> +      :term:`CONFIGURE_SCRIPT` variable stores the location of the ``configure``
> +      script for the Autotools build system. The default definition for this
> +      variable is::
> +
> +         CONFIGURE_SCRIPT ?= "${AUTOTOOLS_SCRIPT_PATH}/configure"
> +
> +      Where :term:`AUTOTOOLS_SCRIPT_PATH` is the location of the of the
> +      Autotools build system scripts, which defaults to :term:`S`.
> +

I would avoid having multiple locations for the default of a given 
variable, makes it easier to avoid forgetting to update all the locations.

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

Thanks!
Quentin

[PATCH v2 09/12] migration-guides/migration-5.2.rst: add information about autotools changes

[Antonin Godard]

Original patch by Ross Burton:
https://lists.yoctoproject.org/g/docs/message/6466

Moved to the migration manual as it is potentially a breaking change.

Co-developed-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
---
 documentation/migration-guides/migration-5.2.rst | 11 +++++++++++
 1 file changed, 11 insertions(+)

diff --git a/documentation/migration-guides/migration-5.2.rst b/documentation/migration-guides/migration-5.2.rst
index a5ac33d81..c4ee3fadd 100644
--- a/documentation/migration-guides/migration-5.2.rst
+++ b/documentation/migration-guides/migration-5.2.rst
@@ -140,6 +140,17 @@ replacing is not as straightforward. For more examples, see the commit
 c++/binutils)" </openembedded-core/commit/?id=4ccc3bc8266c>` in
 :term:`OpenEmbedded-Core (OE-Core)`.
 
+:ref:`ref-classes-autotools` changes
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+-  Changes to how ``aclocal`` is invoked means that ``ACLOCALDIR`` and
+   ``ACLOCALEXTRAPATH`` are no longer used.
+
+-  Directories containing m4 files are no longer found automatically and
+   passed to ``autoreconf``. If a recipe fails to configure because it cannot
+   find m4 macros, then usually the solution is to set ``EXTRA_AUTORECONF += "-I
+   path/to/m4"`` in the recipe.
+
 Recipe changes
 ~~~~~~~~~~~~~~
 

-- 
2.47.0

[PATCH v2 10/12] ref-manual/variables.rst: add a link for BB_USE_HOME_NPMRC

[Antonin Godard]

Documented in the BitBake manual.

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

diff --git a/documentation/ref-manual/variables.rst b/documentation/ref-manual/variables.rst
index e9e8a6933..dace40f59 100644
--- a/documentation/ref-manual/variables.rst
+++ b/documentation/ref-manual/variables.rst
@@ -711,6 +711,9 @@ system and gives an overview of their function and contents.
    :term:`BB_TASKHASH`
       See :term:`bitbake:BB_TASKHASH` in the BitBake manual.
 
+   :term:`BB_USE_HOME_NPMRC`
+      See :term:`bitbake:BB_USE_HOME_NPMRC` in the BitBake manual.
+
    :term:`BB_VERBOSE_LOGS`
       See :term:`bitbake:BB_VERBOSE_LOGS` in the BitBake manual.
 

-- 
2.47.0

[PATCH v2 11/12] migration-guides/migration-5.2: update for upcoming 5.2 release

[Antonin Godard]

Changes since 87d7341465f8 ("python3-iniparse: remove recipe") up to
9cd6b3ad8b9b ("cronie: Resolve build failure with GCC15") in Poky.

Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
---
 documentation/migration-guides/migration-5.2.rst | 46 ++++++++++++++++++++++++
 1 file changed, 46 insertions(+)

diff --git a/documentation/migration-guides/migration-5.2.rst b/documentation/migration-guides/migration-5.2.rst
index c4ee3fadd..b5df4412e 100644
--- a/documentation/migration-guides/migration-5.2.rst
+++ b/documentation/migration-guides/migration-5.2.rst
@@ -94,6 +94,11 @@ systemd changes
    not for socket files).
    Now all service files must be explicitly added to :term:`FILES`.
 
+-  Add ``create-log-dirs`` back to the configuration options. To enable
+   persistent logging a user can now set the "Storage" option of
+   ``journald.conf`` to "persistent". The ``/var/log/journal`` directory is now
+   used for logging instead of ``/run/log``.
+
 Multiconfig changes
 ~~~~~~~~~~~~~~~~~~~
 
@@ -151,9 +156,32 @@ c++/binutils)" </openembedded-core/commit/?id=4ccc3bc8266c>` in
    find m4 macros, then usually the solution is to set ``EXTRA_AUTORECONF += "-I
    path/to/m4"`` in the recipe.
 
+-  The :ref:`ref-classes-autotools` class now requires any recipe that inherits
+   the class to have a ``configure`` script. The configuration script location
+   is stored in the :term:`CONFIGURE_SCRIPT` variable. The
+   :ref:`ref-tasks-configure` task will fail if the script is missing.
+
+:term:`UBOOT_ENTRYPOINT` changes
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+The :term:`UBOOT_ENTRYPOINT` variable should now be defined with a leading
+``0x`` to its value. For example, consider the following assignment::
+
+   UBOOT_ENTRYPOINT ?= "20008000"
+
+This should now be replaced by::
+
+   UBOOT_ENTRYPOINT ?= "0x20008000"
+
 Recipe changes
 ~~~~~~~~~~~~~~
 
+-  The ``libnss-mdns`` recipe is now renamed to ``avahi-libnss-mdns`` to avoid a
+   conflict with meta-networking.
+
+-  :ref:`ref-classes-ptest` support for the ``valgrind`` recipe was removed, due
+   to regressions occurring after updating Glibc to 2.41.
+
 Removed variables
 ~~~~~~~~~~~~~~~~~
 
@@ -176,10 +204,19 @@ 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>`.
 
+-  ``blktool``: It was created in 2004 as an alternative to hdparm and never
+   updated since (while :wikipedia:`hdparm <Hdparm>` remains in active.
+
+-  ``cargo-c-native``: converted to a target recipe and renamed to ``cargo-c``.
+
+-  ``libnss-mdns``: renamed to ``avahi-libnss-mdns``
+
 Removed classes
 ~~~~~~~~~~~~~~~
 
@@ -188,6 +225,12 @@ The following classes have been removed in this release:
 -  ``migrate_localcount.bbclass``: obsolete class for which code was already
    removed in 2012.
 
+Removed features
+~~~~~~~~~~~~~~~~
+
+-  The ``ld-is-gold`` distro feature was removed from the
+   :term:`DISTRO_FEATURES`.
+
 Miscellaneous changes
 ~~~~~~~~~~~~~~~~~~~~~
 
@@ -201,3 +244,6 @@ Miscellaneous changes
    Therefore, the :term:`UBOOT_ENV` is no longer handled by the
    ``kernel-fitimage.bbclass``. There is a new variable :term:`FIT_UBOOT_ENV`
    which should be used for adding a U-Boot script to a FIT image.
+
+-  The ``devtool ide-sdk`` utility has been removed from the :doc:`eSDK
+   </sdk-manual/extensible>` (but remains available in the BitBake environment).

-- 
2.47.0

Re: [docs] [PATCH v2 11/12] migration-guides/migration-5.2: update for upcoming 5.2 release

[Quentin Schulz]

Hi Antonin,

On 3/25/25 10:20 AM, Antonin Godard via lists.yoctoproject.org wrote:
> Changes since 87d7341465f8 ("python3-iniparse: remove recipe") up to
> 9cd6b3ad8b9b ("cronie: Resolve build failure with GCC15") in Poky.
> 
> Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
> ---
>   documentation/migration-guides/migration-5.2.rst | 46 ++++++++++++++++++++++++
>   1 file changed, 46 insertions(+)
> 
> diff --git a/documentation/migration-guides/migration-5.2.rst b/documentation/migration-guides/migration-5.2.rst
> index c4ee3fadd..b5df4412e 100644
> --- a/documentation/migration-guides/migration-5.2.rst
> +++ b/documentation/migration-guides/migration-5.2.rst
> @@ -94,6 +94,11 @@ systemd changes
>      not for socket files).
>      Now all service files must be explicitly added to :term:`FILES`.
>   
> +-  Add ``create-log-dirs`` back to the configuration options. To enable
> +   persistent logging a user can now set the "Storage" option of
> +   ``journald.conf`` to "persistent". The ``/var/log/journal`` directory is now
> +   used for logging instead of ``/run/log``.
> +
>   Multiconfig changes
>   ~~~~~~~~~~~~~~~~~~~
>   
> @@ -151,9 +156,32 @@ c++/binutils)" </openembedded-core/commit/?id=4ccc3bc8266c>` in
>      find m4 macros, then usually the solution is to set ``EXTRA_AUTORECONF += "-I
>      path/to/m4"`` in the recipe.
>   
> +-  The :ref:`ref-classes-autotools` class now requires any recipe that inherits
> +   the class to have a ``configure`` script. The configuration script location
> +   is stored in the :term:`CONFIGURE_SCRIPT` variable. The
> +   :ref:`ref-tasks-configure` task will fail if the script is missing.
> +
> +:term:`UBOOT_ENTRYPOINT` changes
> +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> +
> +The :term:`UBOOT_ENTRYPOINT` variable should now be defined with a leading
> +``0x`` to its value. For example, consider the following assignment::
> +
> +   UBOOT_ENTRYPOINT ?= "20008000"
> +
> +This should now be replaced by::
> +
> +   UBOOT_ENTRYPOINT ?= "0x20008000"
> +
>   Recipe changes
>   ~~~~~~~~~~~~~~
>   
> +-  The ``libnss-mdns`` recipe is now renamed to ``avahi-libnss-mdns`` to avoid a
> +   conflict with meta-networking.
> +
> +-  :ref:`ref-classes-ptest` support for the ``valgrind`` recipe was removed, due
> +   to regressions occurring after updating Glibc to 2.41.
> +
>   Removed variables
>   ~~~~~~~~~~~~~~~~~
>   
> @@ -176,10 +204,19 @@ 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>`.
>   
> +-  ``blktool``: It was created in 2004 as an alternative to hdparm and never
> +   updated since (while :wikipedia:`hdparm <Hdparm>` remains in active.
> +

Missing closing parenthesis.

Cheers,
Quentin

[PATCH v2 12/12] migration-guides/release-notes-5.2: update for upcoming 5.2 release

[Antonin Godard]

Changes since 87d7341465f8 ("python3-iniparse: remove recipe") up to
9cd6b3ad8b9b ("cronie: Resolve build failure with GCC15") in Poky.

Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
---
 .../migration-guides/release-notes-5.2.rst         | 354 ++++++++++++++++++---
 1 file changed, 318 insertions(+), 36 deletions(-)

diff --git a/documentation/migration-guides/release-notes-5.2.rst b/documentation/migration-guides/release-notes-5.2.rst
index d7115230d..a8e6e2b6e 100644
--- a/documentation/migration-guides/release-notes-5.2.rst
+++ b/documentation/migration-guides/release-notes-5.2.rst
@@ -9,19 +9,40 @@ Release notes for |yocto-ver| (|yocto-codename|)
 New Features / Enhancements in |yocto-ver|
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
--  Linux kernel 6.XXX, gcc 14.XXX, glibc 2.XXX, LLVM 18.1.XXX, and over XXX other
+-  Linux kernel 6.12, gcc 14.2, glibc 2.41, LLVM 19.1.7, and over 300 other
    recipe upgrades.
 
+-  Minimum Python version required on the host: 3.9.
+
 -  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``.
-   -  reproducibility: Add the :term:`OEQA_REPRODUCIBLE_TEST_LEAF_TARGETS`
+
+   -  Reproducibility: Add the :term:`OEQA_REPRODUCIBLE_TEST_LEAF_TARGETS`
       variable which enables a reproducibility test on recipes using
       :ref:`Shared State <overview-manual/concepts:Shared State>` for the
       dependencies. See :doc:`/test-manual/reproducible-builds`.
 
+   -  ``systemd``: Add term:`WATCHDOG_RUNTIME_SEC`: for controlling the
+      ``RuntimeWatchdogSec`` option in ``/etc/systemd/system.conf``.
+
+   -  :term:`FIT_UBOOT_ENV` to allow including a u-boot script as a text in a
+      fit image. See the :ref:`ref-classes-kernel-fitimage` for more information.
+
+   -  :ref:`ref-classes-meson`: :term:`MESON_INSTALL_TAGS` to allow passing
+      install tags (``--tags``) to the ``meson install`` command during the
+      :ref:`ref-tasks-install` task.
+
+   -  :ref:`ref-classes-cve-check`: :term:`NVD_DB_VERSION` to allow choosing the
+      CVE feed when using the :ref:`ref-classes-cve-check` class.
+
+   -  The :term:`BB_USE_HOME_NPMRC` controls whether or not BitBake uses the
+      user's ``.npmrc`` file within their home directory within the npm fetcher.
+      This can be used for authentication of private NPM registries, among other
+      uses.
+
 -  Kernel-related changes:
 
    -  :ref:`ref-classes-cml1`: in :ref:`ref-tasks-diffconfig`, do not override
@@ -38,11 +59,39 @@ New Features / Enhancements in |yocto-ver|
        -  ``qcom-qcm6490-ipa``
        -  ``qcom-x1e80100-audio``
        -  ``qcom-qcs615-adreno``
+       -  ``qcom-aic100``
+       -  ``qcom-qdu100``
+       -  ``qca-qca2066``
+       -  ``qca-qca61x4-serial``
+       -  ``qca-qca61x4-usb``
+       -  ``qca-qca6390``
+       -  ``qca-qca6698``
+       -  ``qca-wcn3950``
+       -  ``qca-wcn3988``
+       -  ``qca-wcn399x``
+       -  ``qca-wcn6750``
+       -  ``qca-wcn7850``
+       -  ``qcom-2-license``
+       -  ``qcom-aic100``
+       -  ``qcom-qcm6490-wifi``
+       -  ``qcom-qdu100``
+       -  ``qcom-sa8775p-audio``
+       -  ``qcom-sa8775p-compute``
+       -  ``qcom-sa8775p-generalpurpose``
+       -  ``qcom-x1e80100-lenovo-t14s-g6-adreno``
+       -  ``qcom-x1e80100-lenovo-t14s-g6-audio``
+       -  ``qcom-x1e80100-lenovo-t14s-g6-compute``
+
+   -  ``linux-firmware``: split ``amgpu``, ``ath10k``, ``ath11k`` and ``ath12k``
+      in separate packages.
 
    -  The :ref:`ref-classes-kernel-yocto` classes now supports in-tree
       configuration fragments. These can be added with the
       :term:`KERNEL_FEATURES` variable.
 
+   -  Kernel configuration audit can now be disabled by setting
+      :term:`KMETA_AUDIT` to 1.
+
    -  The ``kern-tools`` recipe is now able to recognize files ending with
       ``.config`` for :ref:`ref-classes-kernel-yocto`-based Kernel recipes.
 
@@ -50,12 +99,19 @@ New Features / Enhancements in |yocto-ver|
       :ref:`ref-classes-kernel-uboot` class. This can be done by setting the
       variable :term:`FIT_KERNEL_COMP_ALG` to ``lzma``.
 
+   -  :ref:`ref-classes-kernel-yocto`: Reproducibility for commits created by
+      the :ref:`ref-classes-kernel-yocto` class was improved.
+
+   -  ``kernel-arch``: add ``-fmacro-prefix-map`` in ``KERNEL_CC`` to fix a
+      reproducibility issue.
+
 -  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.
+      bootloader, along with associated OEQA test cases. This adds the
+      ``barebox`` and the ``barebox-tools`` recipes.
 
    -  Import ``makedumpfile`` from meta-openembedded, as the ``kexec-tools``
       recipe :term:`RDEPENDS` on it.
@@ -69,6 +125,34 @@ New Features / Enhancements in |yocto-ver|
       </meta-openembedded>`, a recipe for hardware identification and
       configuration data, needed by ``libdisplay-info``.
 
+   -  The ``cve-update-db-native`` was restored from kirkstone and can be used
+      to update the CVE National Vulnerability Database (NVD). Add support for
+      the FKIE-CAD (https://github.com/fkie-cad/nvd-json-data-feeds) CVE source
+      for it.
+
+   -  The ``rpm-sequoia-crypto-policy`` to ship a crypto policy file for the
+      ``rpm-sequoia`` recipe.
+
+   -  The ``libsass`` and ``sassc`` for the C/C++ port of the Sass CSS
+      pre-compiler, required by the ``libadwaita`` recipe.
+
+   -  ``python3-roman-numerals-py``: module providing utilities for working with
+      well-formed Roman numerals. ``python3-sphinx`` relies on this recipe.
+
+   -  The ``fastfloat`` recipe, a header-only library for fast number parsing.
+      This will be a dependency for the ``vte`` recipe in later versions.
+
+   -  The ``avahi-libnss-mdns`` was renamed from ``libnss-mdns``.
+
+   -  The ``cargo-c`` was renamed from ``cargo-c-native``.
+
+   -  The ``tcl8`` recipe was added to support the failing build of ``expect``.
+      The ``tcl`` recipe (version 9) remains the main recipe for this component.
+
+   -  The ``scdoc`` recipe is imported from
+      :oe_layerindex:`/layerindex/branch/master/layer/meta-wayland` to support
+      the generation of the man-pages of ``kdoc``.
+
 -  New core classes:
 
    -  New :ref:`ref-classes-uki` class for building Unified Kernel Images (UKI).
@@ -79,12 +163,23 @@ New Features / Enhancements in |yocto-ver|
       this class. This class also strips potential build paths in the compilation
       output for reproducibility.
 
+   -  New :ref:`ref-classes-ptest-python-pytest` class to automatically
+      configure :ref:`ref-classes-ptest` for Python packages using the `pytest
+      <https://docs.pytest.org>`__ unit test framework.
+
 -  Architecture-specific changes:
 
    -  ``tune-cortexa32``: set tune feature to ``armv8a``.
 
+   -  Add the ``loongarch64`` architecture for the ``grub2`` and ``llvm``
+      recipes. It was also added to build with ``musl`` as the toolchain.
+
 -  QEMU / ``runqemu`` changes:
 
+   -  ``qemu/machine``: change the  ``QEMU_EXTRAOPTIONS_${TUNE_PKGARCH}`` syntax
+      in QEMU machine definitions to ``QEMU_EXTRAOPTIONS:tune-${TUNE_PKGARCH}``
+      to follow the same patterns as other QEMU-related variables.
+
 -  Documentation changes:
 
    -  Use ``rsvg`` as a replacement of ``inkscape`` to convert svg files in the
@@ -93,6 +188,10 @@ New Features / Enhancements in |yocto-ver|
    -  The ``cve`` role was replaced by ``cve_nist`` to avoid a conflict with
       more recent version of Sphinx.
 
+   -  New documentation on the multiconfig feature: :doc:`/dev-manual/multiconfig`.
+
+   -  New documentation on ``bblock``: :doc:`/dev-manual/bblock`.
+
 -  Go changes:
 
    -  The :ref:`ref-classes-go-mod` class now sets an internal variable
@@ -116,6 +215,9 @@ New Features / Enhancements in |yocto-ver|
    -  Add the variable :term:`WIC_SECTOR_SIZE` to control the sector size of Wic
       images.
 
+   -  ``bootimg-efi``: Support "+" symbol in filenames passed in
+      :term:`IMAGE_EFI_BOOT_FILES`.
+
 -  SDK-related changes:
 
    -  Add support for ZST-compression through :term:`SDK_ARCHIVE_TYPE`, by
@@ -126,6 +228,11 @@ New Features / Enhancements in |yocto-ver|
 
    -  Enable ``ipv6``, ``acl``, and ``xattr`` in :term:`DISTRO_FEATURES_NATIVESDK`.
 
+   -  Toolchain SDKs (``meta-toolchain``) now properly supports the ``usrmerge``
+      feature (part of :term:`DISTRO_FEATURES`).
+
+   -  The ``pipefail`` shell option is now added to the SDK installer script.
+
 -  Testing-related changes:
 
    -  ``oeqa/postactions``: Fix archive retrieval from target.
@@ -144,8 +251,12 @@ New Features / Enhancements in |yocto-ver|
 
    -  ``oeqa/selftest``: add a test for bitbake "-e" and "-getvar" difference.
 
+   -  ``oeqa/selftest``: Fix failure when configuration contains ``BBLAYERS:append``
+
    -  ``oeqa/ssh``: improve performance and log sizes when handling large files.
 
+   -  ``oeqa/poisoning``: fix and improve gcc include poisoning tests.
+
 -  Utility script changes:
 
    -  The ``patchreview.py`` script now uses the ``check_upstream_status`` from
@@ -163,7 +274,7 @@ New Features / Enhancements in |yocto-ver|
 
       -  Handle LTP raw logs as well as Ptest.
 
-   -  ``scripts/yocto-check-layer``:
+   -  ``yocto-check-layer``:
 
       -  Check for the presence of a ``SECURITY.md`` file in layers and make it
          mandatory.
@@ -172,19 +283,55 @@ New Features / Enhancements in |yocto-ver|
          :term:`CHECKLAYER_REQUIRED_TESTS` to get the list of QA checks to verify
          when running the ``yocto-check-layer`` script.
 
+   -  New ``oe-image-files-spdx`` script utility directory under
+      ``scripts/contrib`` to that processes the SPDX 3.0.1 output from a build
+      and lists all the files on the root file system with their checksums.
+
+   -  ``install-buildtools``:
+
+      -  Add the ``--downloads-directory`` argument to the script to allow
+         specifying the location of the artifact download directory.
+
+      -  The download URL are now stored next to the download artifacts for
+         traceability.
+
+   -  New ``clean-hashserver-database`` under ``scripts/`` that can be used to
+      clean the hashserver database based on the files available in the sstate
+      directory (see :ref:`overview-manual/concepts:Hash Equivalence` for more
+      information).
+
 -  BitBake changes:
 
-   -  ``fetch2``: do not preserve ownership when unpacking.
+   -  Add a new ``include_all`` directive, which can be used to include multiple
+      files present in the same location in different layers.
+
+   -  Fetcher related changes (``fetch2``):
 
-   -  ``fetch2``: switch from Sqlite ``persist_data`` to a standard cache file
-      for checksums, and drop ``persist_data``.
+      -  Do not preserve ownership when unpacking.
 
-   -  ``fetch2``: add support for GitHub codespaces by adding the
-      ``GITHUB_TOKEN`` to the list of variables exported during ``git``
-      invocations.
+      -  switch from Sqlite ``persist_data`` to a standard cache file
+         for checksums, and drop ``persist_data``.
 
-   -  ``fetch2``: set User-Agent to 'bitbake/version' instead of a "fake
-      mozilla" user agent.
+      -  add support for GitHub codespaces by adding the
+         ``GITHUB_TOKEN`` to the list of variables exported during ``git``
+         invocations.
+
+      -  set User-Agent to 'bitbake/version' instead of a "fake
+         mozilla" user agent.
+
+      -  ``wget``: handle HTTP 308 Permanent Redirect.
+
+      -  ``wget``: increase timeout to 100s from 30s to match CDN worst
+         response time.
+
+      -  Add support for fast initial shallow fetch. The fetcher will prefer an
+         initial shallow clone, but will re-utilize an existing bare clone if
+         there is one. If the remote server does not allow shallow fetches, the
+         fetcher falls back to a bare clone. This improves the data transfer
+         size on the initial fetch of a repository, eliminates the need to use
+         an HTTPS tarball :term:`SRC_URI` to reduce data transfer, and allows
+         SSH-based authentication when using non-public repos, so additional
+         HTTPS tokens may not be required.
 
    -  ``compress``: use ``lz4`` instead of ``lz4c``, as ``lz4c`` as been
       considered deprecrated since 2018.
@@ -192,14 +339,13 @@ New Features / Enhancements in |yocto-ver|
    -  ``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``:
 
-   -  ``bitbake-worker/cooker``: increase the default pipe size from 64KB to
-      512KB for better efficiency when transferring large amounts of data.
+      -  improve bytearray truncation performance when large
+         amounts of data are being transferred from the cooker to the worker.
 
-   -  ``fetch/wget``: increase timeout to 100s from 30s to match CDN worst
-      response time.
+      -  ``cooker``: increase the default pipe size from 64KB to
+         512KB for better efficiency when transferring large amounts of data.
 
    -  ``bitbake-getvar``: catch ``NoProvider`` exception to improve error
       readability when a recipe is not found with ``--recipe``.
@@ -219,6 +365,18 @@ New Features / Enhancements in |yocto-ver|
    -  ``knotty`` now hints the user if :term:`MACHINE` was not set in
       the ``local.conf`` file.
 
+   -  ``utils``: add Go mod h1 checksum support, specific to Go modules. Use
+      with ``goh1``.
+
+   -  The parser now catches empty variable name assignments such as::
+
+         += "value"
+
+      The previous code would have assigned ``value`` to the variable named ``+``.
+
+   -  ``hashserv``: Add the ``gc-mark-stream`` command for batch hash marking.
+
+
 -  Packaging changes:
 
    -  ``systemd``: extract dependencies from ``.note.dlopen`` ELF segments, to
@@ -235,13 +393,18 @@ New Features / Enhancements in |yocto-ver|
 
 -  LLVM related changes:
 
+   -  Set ``LLVM_HOST_TRIPLE`` for cross-compilation, which is recommended when
+      cross-compiling Llvm.
+
 -  SPDX-related changes:
 
-   -  SPDX 3.0: Find local sources when searching for debug sources.
+   -  SPDX 3.0:
 
-   -  SPDX 3.0: Map ``gitsm`` URIs to ``git``.
+      -  Find local sources when searching for debug sources.
 
-   -  SPDX 3.0: Link license and build by alias instead of SPDX ID.
+      -  Map ``gitsm`` URIs to ``git``.
+
+      -  Link license and build by alias instead of SPDX ID.
 
    -  Fix SPDX tasks not running when code changes (use of ``file-checksums``).
 
@@ -256,6 +419,14 @@ New Features / Enhancements in |yocto-ver|
       ``devtool modify my-recipe --debug-build`` followed by
       ``devtool ide-sdk my-recipe my-image``.
 
+   -  ``create-spdx``: support line numbers for :term:`NO_GENERIC_LICENSE`
+      license types.
+
+   -  ``spdx30``: Adds a "contains" relationship that relates the root file
+      system package to the files contained in it. If a package provides a file
+      with a matching hash and path, it will be linked, otherwise a new File
+      element will be created.
+
 -  Patchtest-related changes:
 
    -  Refactor pattern definitions in a ``patterns`` module.
@@ -299,24 +470,77 @@ New Features / Enhancements in |yocto-ver|
       currently prints warning message for every unpatched CVE the
       :ref:`ref-classes-cve-check` class finds.
 
+   -  Users can control the NVD database source using the :term:`NVD_DB_VERSION`
+      variable with possible values ``NVD1``, ``NVD2``, or ``FKIE``.
+
+   -  The default feed for CVEs is now ``FKIE`` instead of ``NVD2`` (see
+      :term:`NVD_DB_VERSION` for more information).
+
 -  New :term:`PACKAGECONFIG` options for individual recipes:
 
-      -  ``perf``: ``zstd``
-      -  ``ppp``: ``pam``, ``openssl``
-      -  ``libpciaccess``: ``zlib``
-      -  ``gdk-pixbuf``: ``gif``, ``others``
-      -  ``libpam``: ``selinux``
-      -  ``libsecret``: ``pam``
-      -  ``rpm``: ``sequoia``
+   -  ``perf``: ``zstd``
+   -  ``ppp``: ``pam``, ``openssl``
+   -  ``libpciaccess``: ``zlib``
+   -  ``gdk-pixbuf``: ``gif``, ``others``
+   -  ``libpam``: ``selinux``
+   -  ``libsecret``: ``pam``
+   -  ``rpm``: ``sequoia``
+   -  ``systemd``: ``apparmor``, ``fido``, ``mountfsd``, ``nsresourced``
+   -  ``ovmf``: ``debug``
+   -  ``webkitgtk``: ``assertions``
 
--  Miscellaneous changes:
+-  Systemd related changes:
 
-   -  ``bluez``: fix mesh build when building with musl.
+   -  ``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.
+
+      -  really disable Predictable Network Interface names if the ``pni-names``
+         feature is not part of :term:`DISTRO_FEATURES`. Previously it was only
+         really disable for QEMU machines.
+
+      -  split ``networkd`` into its own package named ``systemd-networkd``.
 
    -  ``systemd-bootchart``: now supports the 32-bit *riscv* architecture.
 
    -  ``systemd-boot``: now supports the *riscv* architecture.
 
+   -  ``systemd-serialgetty``:
+
+      -  the recipe no longer sets a default value for
+         :term:`SERIAL_CONSOLES`, and uses the one set in ``bitbake.conf``.
+
+      -  the recipe no longer ships a copy of the ``serial-getty@.service`` as
+         it is provided by systemd directly.
+
+      -  Don't set a default :term:`SERIAL_CONSOLES` value in the
+         ``systemd-serialgetty`` recipe and take the global value that should
+         already be set.
+
+      -  Replace custom unit files by existing unit files provided in the
+         systemd source code.
+
+   -  User unit supports was improved. All the user units are now enabled by
+      default.
+
+   -  The custom implementation of ``systemctl`` in :term:`OpenEmbedded-Core
+      (OE-Core)` was removed to use the upstream one. This ``systemctl`` binary
+      is now compiled and used for systemd-related operations.
+
+-  :ref:`ref-classes-sanity` class changes:
+
+   -  Add a sanity check to validate that the C++ toolchain is functional on the
+      host.
+
+   -  Add a sanity check to verify that :term:`TOPDIR` does not contain
+      non-ASCII characters, as it may lead to unexpected build errors.
+
+-  Miscellaneous changes:
+
+   -  ``bluez``: fix mesh build when building with musl.
+
    -  ``python3-pip``: the ``pip`` executable is now left and not deleted, and
       can be used instead of ``pip3`` and ``pip2``.
 
@@ -326,7 +550,8 @@ New Features / Enhancements in |yocto-ver|
    -  :term:`SOLIBSDEV` and :term:`SOLIBS` are now defined for the *mingw32*
       architecture (``.dll``).
 
-   -  :ref:`rootfs-postcommands <ref-classes-rootfs*>`: make opkg status reproducible.
+   -  :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.
@@ -364,13 +589,11 @@ New Features / Enhancements in |yocto-ver|
       ``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``.
+      :term:`CVE_DB_UPDATE_INTERVAL` is not set to ``-1``. Users can control the
+      NVD database source using the :term:`NVD_DB_VERSION` variable with
+      possible values ``NVD1``, ``NVD2``, or ``FKIE``.
 
    -  ``systemtap``: add ``--with-extra-version="oe"`` configure option to
       improve the reproducibility of the recipe.
@@ -398,6 +621,65 @@ New Features / Enhancements in |yocto-ver|
       ``seat`` group to be able to properly establish connection between the
       Weston and the ``seatd`` socket.
 
+   -  ``webkitgtk``:
+
+      -  Fix build on 32bit arches with 64bit ``time_t`` only.
+
+      -  Disable JIT on RISCV64.
+
+   -  :ref:`ref-classes-report-error`: Add :term:`PN` to error report files.
+
+   -  ``initrdscripts``: add UBI support for mounting a live ``ubifs`` rootfs.
+
+   -  ``uboot-extlinux-config.bbclass``: add support for device tree overlays.
+
+   -  ``glibc``: add ``ld.so.conf`` to :term:`CONFFILES`.
+
+   -  ``udev-extraconf``: Allow FAT mount group to be specified with
+      :term:`MOUNT_GROUP`.
+
+   -  New ``bbverbnote`` log utility which can be used to print on the console
+      (equivalent to the ``bb.verbnote`` Python implementation).
+
+   -  :ref:``ref-classes-grub-efi``: Add :term:`GRUB_TITLE` variable to set
+      custom GRUB titles.
+
+   -  ``gawk``: Enable high precision arithmetic support by default (``mpfr``
+      enabled by default in :term:`PACKAGECONFIG`).
+
+   -  ``licenses``: Map the license ``SGIv1`` to ``SGI-OpenGL``, as ``SGIv1`` is
+      not an SPDX license identifier.
+
+   -  Configuration files for the `b4 <https://b4.docs.kernel.org>`__
+      command-line tool was added to the different Yocto Project and OpenEmbedded
+      repositories.
+
+   -  :ref:`ref-classes-kernel-fitimage`: handle :doc:`multiconfig
+      </dev-manual/multiconfig>` dependency when
+      :term:`INITRAMFS_MULTICONFIG` is set.
+
+   -  ``psplash``: when using the ``systemd`` feature from
+      :term:`DISTRO_FEATURES`, start the ``psplash`` service when the
+      ``/dev/fb0`` framebuffer is detected with Udev.
+
+   -  ``gdb``: is now compiled with xz support by default (``--with-lzma``).
+
+   -  ``busybox``: drop net-tools from the default ``defconfig``, since these tools
+      (``ifconfig``, etc.) have been deprecated since `2009
+      <https://lists.debian.org/debian-devel/2009/03/msg00780.html>`__.
+
+   -  ``perf`` is built with ``zstd`` in :term:`PACKAGECONFIG` by default.
+
+   -  ``boost``: add ``charconv`` to built libraries by default.
+
+   -  ``mirrors``: rationalise Debian mirrors to point at the canonical server
+      (deb.debian.org) instead of country specific ones. This server is backed
+      by a :wikipedia:`CDN <Content_delivery_network>` to properly balance the
+      server load.
+
+   -  ``lib: sbom30``: Add action statement for affected VEX statements with
+      "Mitigation action unknown", as these are not tracked by the existing
+      code.
 
 Known Issues in |yocto-ver|
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~

-- 
2.47.0

Re: [docs] [PATCH v2 12/12] migration-guides/release-notes-5.2: update for upcoming 5.2 release

[Enrico Jörns]

Am Dienstag, dem 25.03.2025 um 10:20 +0100 schrieb Antonin Godard via lists.yoctoproject.org:
> --  Miscellaneous changes:
> +-  Systemd related changes:
>  
> -   -  ``bluez``: fix mesh build when building with musl.
> +   -  ``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.
> +
> +      -  really disable Predictable Network Interface names if the ``pni-names``
> +         feature is not part of :term:`DISTRO_FEATURES`. Previously it was only
> +         really disable for QEMU machines.

( s/disable/disabled/ )

Quick question: My understanding (and observation) is that not having 'pni-names' set in
DISTRO_FEATURES (which will be the default for almost everyone) will change the network naming to
'non predictable' now, correct?
For me, this is quite unexpected and requires me to add 'pni-name' to keep the original behavior.
Shouldn't we then at least add this as a hint to the migration notes?

Regards, Enrico

> +      -  split ``networkd`` into its own package named ``systemd-networkd``.
>  
>     -  ``systemd-bootchart``: now supports the 32-bit *riscv* architecture.
>  
>     -  ``systemd-boot``: now supports the *riscv* architecture.
>  
> +   -  ``systemd-serialgetty``:
> +
> +      -  the recipe no longer sets a default value for
> +         :term:`SERIAL_CONSOLES`, and uses the one set in ``bitbake.conf``.
> +
> +      -  the recipe no longer ships a copy of the ``serial-getty@.service`` as
> +         it is provided by systemd directly.
> +
> +      -  Don't set a default :term:`SERIAL_CONSOLES` value in the
> +         ``systemd-serialgetty`` recipe and take the global value that should
> +         already be set.
> +
> +      -  Replace custom unit files by existing unit files provided in the
> +         systemd source code.
> +
> +   -  User unit supports was improved. All the user units are now enabled by
> +      default.
> +
> +   -  The custom implementation of ``systemctl`` in :term:`OpenEmbedded-Core
> +      (OE-Core)` was removed to use the upstream one. This ``systemctl`` binary
> +      is now compiled and used for systemd-related operations.
> +
> +-  :ref:`ref-classes-sanity` class changes:
> +
> +   -  Add a sanity check to validate that the C++ toolchain is functional on the
> +      host.
> +
> +   -  Add a sanity check to verify that :term:`TOPDIR` does not contain
> +      non-ASCII characters, as it may lead to unexpected build errors.
> +
> +-  Miscellaneous changes:
> +
> +   -  ``bluez``: fix mesh build when building with musl.
> +
>     -  ``python3-pip``: the ``pip`` executable is now left and not deleted, and
>        can be used instead of ``pip3`` and ``pip2``.
>  
> @@ -326,7 +550,8 @@ New Features / Enhancements in |yocto-ver|
>     -  :term:`SOLIBSDEV` and :term:`SOLIBS` are now defined for the *mingw32*
>        architecture (``.dll``).
>  
> -   -  :ref:`rootfs-postcommands <ref-classes-rootfs*>`: make opkg status reproducible.
> +   -  :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.
> @@ -364,13 +589,11 @@ New Features / Enhancements in |yocto-ver|
>        ``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``.
> +      :term:`CVE_DB_UPDATE_INTERVAL` is not set to ``-1``. Users can control the
> +      NVD database source using the :term:`NVD_DB_VERSION` variable with
> +      possible values ``NVD1``, ``NVD2``, or ``FKIE``.
>  
>     -  ``systemtap``: add ``--with-extra-version="oe"`` configure option to
>        improve the reproducibility of the recipe.
> @@ -398,6 +621,65 @@ New Features / Enhancements in |yocto-ver|
>        ``seat`` group to be able to properly establish connection between the
>        Weston and the ``seatd`` socket.
>  
> +   -  ``webkitgtk``:
> +
> +      -  Fix build on 32bit arches with 64bit ``time_t`` only.
> +
> +      -  Disable JIT on RISCV64.
> +
> +   -  :ref:`ref-classes-report-error`: Add :term:`PN` to error report files.
> +
> +   -  ``initrdscripts``: add UBI support for mounting a live ``ubifs`` rootfs.
> +
> +   -  ``uboot-extlinux-config.bbclass``: add support for device tree overlays.
> +
> +   -  ``glibc``: add ``ld.so.conf`` to :term:`CONFFILES`.
> +
> +   -  ``udev-extraconf``: Allow FAT mount group to be specified with
> +      :term:`MOUNT_GROUP`.
> +
> +   -  New ``bbverbnote`` log utility which can be used to print on the console
> +      (equivalent to the ``bb.verbnote`` Python implementation).
> +
> +   -  :ref:``ref-classes-grub-efi``: Add :term:`GRUB_TITLE` variable to set
> +      custom GRUB titles.
> +
> +   -  ``gawk``: Enable high precision arithmetic support by default (``mpfr``
> +      enabled by default in :term:`PACKAGECONFIG`).
> +
> +   -  ``licenses``: Map the license ``SGIv1`` to ``SGI-OpenGL``, as ``SGIv1`` is
> +      not an SPDX license identifier.
> +
> +   -  Configuration files for the `b4 <https://b4.docs.kernel.org>`__
> +      command-line tool was added to the different Yocto Project and OpenEmbedded
> +      repositories.
> +
> +   -  :ref:`ref-classes-kernel-fitimage`: handle :doc:`multiconfig
> +      </dev-manual/multiconfig>` dependency when
> +      :term:`INITRAMFS_MULTICONFIG` is set.
> +
> +   -  ``psplash``: when using the ``systemd`` feature from
> +      :term:`DISTRO_FEATURES`, start the ``psplash`` service when the
> +      ``/dev/fb0`` framebuffer is detected with Udev.
> +
> +   -  ``gdb``: is now compiled with xz support by default (``--with-lzma``).
> +
> +   -  ``busybox``: drop net-tools from the default ``defconfig``, since these tools
> +      (``ifconfig``, etc.) have been deprecated since `2009
> +      <https://lists.debian.org/debian-devel/2009/03/msg00780.html>`__.
> +
> +   -  ``perf`` is built with ``zstd`` in :term:`PACKAGECONFIG` by default.
> +
> +   -  ``boost``: add ``charconv`` to built libraries by default.
> +
> +   -  ``mirrors``: rationalise Debian mirrors to point at the canonical server
> +      (deb.debian.org) instead of country specific ones. This server is backed
> +      by a :wikipedia:`CDN <Content_delivery_network>` to properly balance the
> +      server load.
> +
> +   -  ``lib: sbom30``: Add action statement for affected VEX statements with
> +      "Mitigation action unknown", as these are not tracked by the existing
> +      code.
>  
>  Known Issues in |yocto-ver|
>  ~~~~~~~~~~~~~~~~~~~~~~~~~~~
> 
> 
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#6624): https://lists.yoctoproject.org/g/docs/message/6624
> Mute This Topic: https://lists.yoctoproject.org/mt/111893964/3616721
> Group Owner: docs+owner@lists.yoctoproject.org
> Unsubscribe: https://lists.yoctoproject.org/g/docs/unsub [ejo@pengutronix.de]
> -=-=-=-=-=-=-=-=-=-=-=-
> 

-- 
Pengutronix e.K.                           | Enrico Jörns                |
Embedded Linux Consulting & Support        | https://www.pengutronix.de/ |
Steuerwalder Str. 21                       | Phone: +49-5121-206917-180  |
31137 Hildesheim, Germany                  | Fax:   +49-5121-206917-9    |

Re: [docs] [PATCH v2 12/12] migration-guides/release-notes-5.2: update for upcoming 5.2 release

[Antonin Godard]

Hi Enrico,

On Mon Apr 14, 2025 at 1:12 PM CEST, Enrico Jörns wrote:
> Am Dienstag, dem 25.03.2025 um 10:20 +0100 schrieb Antonin Godard via lists.yoctoproject.org:
>> --  Miscellaneous changes:
>> +-  Systemd related changes:
>>  
>> -   -  ``bluez``: fix mesh build when building with musl.
>> +   -  ``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.
>> +
>> +      -  really disable Predictable Network Interface names if the ``pni-names``
>> +         feature is not part of :term:`DISTRO_FEATURES`. Previously it was only
>> +         really disable for QEMU machines.
>
> ( s/disable/disabled/ )

Thanks, I'll fix this.

> Quick question: My understanding (and observation) is that not having 'pni-names' set in
> DISTRO_FEATURES (which will be the default for almost everyone) will change the network naming to
> 'non predictable' now, correct?

Not having the 'pni-names' distro feature prevent the 'pni-names' systemd
package config from being added to PACKAGECONFIG. In turns, it does the
following in do_install as a result:

  if ${@bb.utils.contains('PACKAGECONFIG', 'pni-names', 'true', 'false', d)}; then
    if ! grep -q '^NamePolicy=.*mac' ${D}${nonarch_libdir}/systemd/network/99-default.link; then
      [...]
  else
    # Actively disable Predictable Network Interface Names
    sed -i 's/^NamePolicy=.*/NamePolicy=/;s/^AlternativeNamesPolicy=.*/AlternativeNamesPolicy=/' ${D}${nonarch_libdir}/systemd/network/99-default.link
  fi

> For me, this is quite unexpected and requires me to add 'pni-name' to keep the original behavior.
> Shouldn't we then at least add this as a hint to the migration notes?

So yes I think your understanding is correct, and your point is valid. I'll come
up with something and copy you in.

[For reference, the commit that changes the behavior is 37b98bc93bc4 ("systemd:
actively disable Predictable Network Interface Names if !pni-names") in OE-core]

Thanks a lot!
Antonin

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

Re: [docs] [PATCH v2 12/12] migration-guides/release-notes-5.2: update for upcoming 5.2 release

[Antonin Godard]

On Thu May 15, 2025 at 2:33 PM CEST, Alexander Sverdlin wrote:
> Hi Enrico!
>
> On Mon, 2025-04-14 at 13:12 +0200, Enrico Jörns wrote:
>> > -   -  ``bluez``: fix mesh build when building with musl.
>> > +   -  ``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.
>> > +
>> > +      -  really disable Predictable Network Interface names if the ``pni-names``
>> > +         feature is not part of :term:`DISTRO_FEATURES`. Previously it was only
>> > +         really disable for QEMU machines.
>> 
>> ( s/disable/disabled/ )
>> 
>> Quick question: My understanding (and observation) is that not having 'pni-names' set in
>> DISTRO_FEATURES (which will be the default for almost everyone) will change the network naming to
>> 'non predictable' now, correct?
>> For me, this is quite unexpected and requires me to add 'pni-name' to keep the original behavior.
>> Shouldn't we then at least add this as a hint to the migration notes?
>
> Thanks for pointing this out!
> I'm sorry this came as a surprise! The reason I didn't think about
> preserving the legacy behaviour is that the behaviour itself was inconsistent (QEMU vs the rest).
>
> Do you think we should add "pni-names" to the default systemd PACKAGECONFIG now as a follow-up patch?

Hi Alexander,

I don't have a strong opinion on this, but I think the best way to get an answer
to that question is to send the patch on OE-Core and wait for feedback, as you
won't get much traction on the docs list. :)

Thanks,
Antonin

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