From 90e4af3effd8b62e52f4f8746d9768bbcf61cfd2 Mon Sep 17 00:00:00 2001 From: Antonin Godard Date: Mon, 7 Apr 2025 10:59:20 +0200 Subject: migration-guides/{migration,release-note}-5.2: update for 5.2 release Document changes between 1c3020f17370 ("expat: Upgrade 2.7.0 -> 2.7.1") up to e894acce6ede ("build-appliance-image: Update to master head revision") in Poky: - Add a note on the devtool upgrade-status change. - Be more precise about the usage of multiple repositories in SRC_URI, mention that it makes sense for bare clones only. As the walnascar branch has now frozen and is up for QA, these should be the one of the last changes to these documents. (From yocto-docs rev: 322355ead2be9e267368ca47d805f41ae10ad6cc) Signed-off-by: Antonin Godard Signed-off-by: Richard Purdie --- documentation/migration-guides/migration-5.2.rst | 16 +++++++++------- documentation/migration-guides/release-notes-5.2.rst | 4 ++++ 2 files changed, 13 insertions(+), 7 deletions(-) diff --git a/documentation/migration-guides/migration-5.2.rst b/documentation/migration-guides/migration-5.2.rst index 4dd8cd20f8..6b7d02d656 100644 --- a/documentation/migration-guides/migration-5.2.rst +++ b/documentation/migration-guides/migration-5.2.rst @@ -186,18 +186,20 @@ The support for having multiple Git revisions per URL in :term:`SRC_URI` was removed from BitBake, which means the following syntax is not supported anymore:: - SRC_URI = "git://some.host/somepath;branch=branchX,branchY;name=nameX,nameY" + SRC_URI = "git://some.host/somepath;bareclone=1;branch=branchX,branchY;name=nameX,nameY" SRCREV_nameX = "xxxxxxxxxxxxxxxxxxxx" SRCREV_nameY = "yyyyyyyyyyyyyyyyyyyy" -This was rarely used in the core repositories, and this removal simplifies the -code logic in several places. +This was rarely used in the core repositories because it would only ever make +sense for bare clones (the ``bareclone=1`` :term:`SRC_URI` option) where recipes +take care of the Git checkout. This removal simplifies the code logic in several +places. -If one of your recipes is still using this mechanism, you can split the -code source fetching into two separate entries:: +If one of your recipes is using this mechanism, you can split the code source +fetching into two separate entries:: - SRC_URI = "git://some.host/somepath;branch=branchX;name=nameX \ - git://some.host/somepath;branch=branchY;name=nameY" + SRC_URI = "git://some.host/somepath;bareclone=1;branch=branchX;name=nameX \ + git://some.host/somepath;bareclone=1;branch=branchY;name=nameY" SRCREV_nameX = "xxxxxxxxxxxxxxxxxxxx" SRCREV_nameY = "yyyyyyyyyyyyyyyyyyyy" diff --git a/documentation/migration-guides/release-notes-5.2.rst b/documentation/migration-guides/release-notes-5.2.rst index 2ad4414494..ac9c6319a4 100644 --- a/documentation/migration-guides/release-notes-5.2.rst +++ b/documentation/migration-guides/release-notes-5.2.rst @@ -447,6 +447,10 @@ New Features / Enhancements in |yocto-ver| with a matching hash and path, it will be linked, otherwise a new File element will be created. + - The output of :ref:`devtool upgrade-status + ` + is now sorted by recipe name. + - Patchtest-related changes: - Refactor pattern definitions in a ``patterns`` module. -- cgit v1.2.3-54-g00ecf