From: michael.opdenacker@bootlin.com
To: docs@lists.yoctoproject.org
Cc: Michael Opdenacker <michael.opdenacker@bootlin.com>,
Ross Burton <ross.burton@arm.com>
Subject: [PATCH] migration-guides: add known issues for 4.1
Date: Mon, 17 Oct 2022 19:06:13 +0200 [thread overview]
Message-ID: <20221017170613.244775-1-michael.opdenacker@bootlin.com> (raw)
From: Michael Opdenacker <michael.opdenacker@bootlin.com>
From: Ross Burton <ross.burton@arm.com>
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
---
documentation/migration-guides/release-notes-4.1.rst | 12 +++++++++++-
1 file changed, 11 insertions(+), 1 deletion(-)
diff --git a/documentation/migration-guides/release-notes-4.1.rst b/documentation/migration-guides/release-notes-4.1.rst
index 4639d04cb4..be722356d1 100644
--- a/documentation/migration-guides/release-notes-4.1.rst
+++ b/documentation/migration-guides/release-notes-4.1.rst
@@ -187,7 +187,17 @@ New Features / Enhancements in 4.1
Known Issues in 4.1
~~~~~~~~~~~~~~~~~~~
-
+- The change to :ref:`migration-4.1-complementary-deps` means that images
+ built with the ``ptest-pkgs`` :term:`IMAGE_FEATURES` don’t automatically
+ install ``ptest-runner``, as that package is a recommendation of the
+ individual ``-ptest`` packages. This will be resolved in the next point
+ release, and can be worked around by explicitly installing ``ptest-runner``
+ into the image. Filed as :yocto_bugs:`bug 14928 </show_bug.cgi?id=14928>`.
+
+- There is a known issue with eSDKs where sstate objects may be missing,
+ resulting in packages being unavailable to install in the sysroot. This is
+ under investigation and appears to be related to hash equivalence. Filed as
+ :yocto_bugs:`bug 14626 </show_bug.cgi?id=14626>`.
Recipe License changes in 4.1
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
--
2.34.1
reply other threads:[~2022-10-17 17:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20221017170613.244775-1-michael.opdenacker@bootlin.com \
--to=michael.opdenacker@bootlin.com \
--cc=docs@lists.yoctoproject.org \
--cc=ross.burton@arm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox