From: chee.yang.lee@intel.com
To: docs@lists.yoctoproject.org
Subject: [PATCH] release-notes-5.0: update recipes changes
Date: Wed, 24 Apr 2024 12:41:54 +0800 [thread overview]
Message-ID: <20240424044154.4712-1-chee.yang.lee@intel.com> (raw)
From: Lee Chee Yang <chee.yang.lee@intel.com>
update recipes changes in 5.0 rc4.
update new recipes, license changes, patched cve and recipes version
changes.
Signed-off-by: Lee Chee Yang <chee.yang.lee@intel.com>
---
documentation/migration-guides/release-notes-5.0.rst | 10 +++++++---
1 file changed, 7 insertions(+), 3 deletions(-)
diff --git a/documentation/migration-guides/release-notes-5.0.rst b/documentation/migration-guides/release-notes-5.0.rst
index 2501acdaf..884a66771 100644
--- a/documentation/migration-guides/release-notes-5.0.rst
+++ b/documentation/migration-guides/release-notes-5.0.rst
@@ -88,6 +88,9 @@ New Features / Enhancements in 5.0
a Sphinx extension to include jQuery on newer Sphinx releases. Recent
versions of ``python3-sphinx-rtd-theme`` depend on it.
+ - `python3-websockets <https://pypi.org/project/websockets/>`__: a
+ library for building WebSocket servers and clients in Python.
+
- `python3-yamllint <https://github.com/adrienverge/yamllint>`__: a linter
for YAML files. In U-Boot, the ``binman`` tool uses this linter to verify the
configurations at compile time.
@@ -346,6 +349,7 @@ The following corrections have been made to the :term:`LICENSE` values set by re
- ``elfutils``: split license for libraries & backend and utilities.
- ``ghostscript``: correct :term:`LICENSE` to ``AGPL-3.0-or-later``.
+- ``kbd``: update license for consolefont and keymaps.
- ``libsystemd``: set its own :term:`LICENSE` value (``LGPL-2.1-or-later``) to add more granularity.
- ``libtest-warnings-perl``: update :term:`LICENSE` ``Artistic-1.0`` to ``Artistic-1.0-Perl``.
- ``linux-firmware``: set package :term:`LICENSE` appropriately for ``carl9170``, ``rockchip`` and ``powerpr``.
@@ -378,7 +382,7 @@ Security Fixes in 5.0
- libxml2: :cve:`2023-45322` (ignored)
- linux-yocto/6.6: :cve:`2020-16119`
- openssh: :cve:`2023-48795`, :cve:`2023-51384`, :cve:`2023-51385`
-- openssl: :cve:`2023-5363`, :cve:`2023-5678`, :cve:`2023-6129`, :cve_mitre:`2023-6237`, :cve:`2024-0727`
+- openssl: :cve:`2023-5363`, :cve:`2023-5678`, :cve:`2023-6129`, :cve_mitre:`2023-6237`, :cve:`2024-0727`, :cve:`2024-2511`
- perl: :cve:`2023-47100`
- pixman: :cve:`2023-37769` (ignored)
- python3-cryptography{-vectors}: :cve:`2023-49083`, :cve:`2024-26130`
@@ -554,7 +558,7 @@ Recipe Upgrades in 5.0
- linux-yocto-dev 6.6+git -> 6.9+git
- linux-yocto-rt 6.1.78+git, 6.5.13+git -> 6.6.23+git
- linux-yocto-tiny 6.1.78+git, 6.5.13+git -> 6.6.23+git
-- llvm 17.0.3 -> 18.1.2
+- llvm 17.0.3 -> 18.1.3
- lsof 4.98.0 -> 4.99.3
- ltp 20230516 -> 20240129
- lttng-modules 2.13.10 -> 2.13.12
@@ -590,7 +594,7 @@ Recipe Upgrades in 5.0
- ptest-runner 2.4.2+git -> 2.4.3+git
- pulseaudio 16.1 -> 17.0
- puzzles 0.0+git (2d9e414ee316…) -> 0.0+git (80aac3104096…)
-- python3 3.11.5 -> 3.12.2
+- python3 3.11.5 -> 3.12.3
- python3-alabaster 0.7.13 -> 0.7.16
- python3-attrs 23.1.0 -> 23.2.0
- python3-babel 2.12.1 -> 2.14.0
--
2.34.1
next reply other threads:[~2024-04-24 4:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-24 4:41 chee.yang.lee [this message]
2024-04-24 13:10 ` [docs] [PATCH] release-notes-5.0: update recipes changes Michael Opdenacker
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=20240424044154.4712-1-chee.yang.lee@intel.com \
--to=chee.yang.lee@intel.com \
--cc=docs@lists.yoctoproject.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).