From: Steve Sakoman <steve@sakoman.com>
To: openembedded-core@lists.openembedded.org
Subject: [OE-core][styhead 00/12] Patch review
Date: Fri, 7 Feb 2025 14:06:41 -0800 [thread overview]
Message-ID: <cover.1738965898.git.steve@sakoman.com> (raw)
Please review this set of changes for styhead and have comments back by
end of day Tuesday, February 11
Passed a-full on autobuilder:
https://autobuilder.yoctoproject.org/valkyrie/#/builders/29/builds/976
The following changes since commit a5e7ff4424a68335fc768e49a232a58011a5b160:
devtool: ide-sdk remove the plugin from eSDK installer (2025-01-29 06:42:16 -0800)
are available in the Git repository at:
https://git.openembedded.org/openembedded-core-contrib stable/styhead-nut
https://git.openembedded.org/openembedded-core-contrib/log/?h=stable/styhead-nut
Alexander Kanavin (2):
enchant2: correct SRC_URI and other uris
libxml-parser-perl: correct SRC_URI
Bruce Ashfield (3):
linux-yocto/6.6: update to v6.6.71
linux-yocto/6.6: update to v6.6.72
linux-yocto/6.6: update to v6.6.74
Mikko Rapeli (1):
systemd: set CVE_PRODUCT
Peter Marko (2):
cve-check: restore CVE_CHECK_SHOW_WARNINGS functionality
cve-check: fix cvesInRecord
Richard Purdie (2):
resulttool/store: Fix permissions of logarchive
oeqa/gitarchive: Fix syntax warning
Ross Burton (2):
libnsl2: set CVE_PRODUCT
lrzsz: update SRC_URI to avoid redirect
meta/classes/cve-check.bbclass | 16 +++++++----
meta/lib/oeqa/utils/gitarchive.py | 2 +-
meta/recipes-bsp/lrzsz/lrzsz_0.12.20.bb | 6 ++--
meta/recipes-core/systemd/systemd.inc | 2 ++
.../perl/libxml-parser-perl_2.47.bb | 2 +-
meta/recipes-extended/libnsl/libnsl2_git.bb | 2 ++
.../linux/linux-yocto-rt_6.6.bb | 6 ++--
.../linux/linux-yocto-tiny_6.6.bb | 6 ++--
meta/recipes-kernel/linux/linux-yocto_6.6.bb | 28 +++++++++----------
.../recipes-support/enchant/enchant2_2.8.2.bb | 6 ++--
scripts/lib/resulttool/store.py | 1 +
11 files changed, 44 insertions(+), 33 deletions(-)
--
2.43.0
next reply other threads:[~2025-02-07 22:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-07 22:06 Steve Sakoman [this message]
2025-02-07 22:06 ` [OE-core][styhead 01/12] libnsl2: set CVE_PRODUCT Steve Sakoman
2025-02-07 22:06 ` [OE-core][styhead 02/12] cve-check: restore CVE_CHECK_SHOW_WARNINGS functionality Steve Sakoman
2025-02-07 22:06 ` [OE-core][styhead 03/12] cve-check: fix cvesInRecord Steve Sakoman
2025-02-07 22:06 ` [OE-core][styhead 04/12] systemd: set CVE_PRODUCT Steve Sakoman
2025-02-07 22:06 ` [OE-core][styhead 05/12] linux-yocto/6.6: update to v6.6.71 Steve Sakoman
2025-02-07 22:06 ` [OE-core][styhead 06/12] linux-yocto/6.6: update to v6.6.72 Steve Sakoman
2025-02-07 22:06 ` [OE-core][styhead 07/12] linux-yocto/6.6: update to v6.6.74 Steve Sakoman
2025-02-07 22:06 ` [OE-core][styhead 08/12] resulttool/store: Fix permissions of logarchive Steve Sakoman
2025-02-07 22:06 ` [OE-core][styhead 09/12] enchant2: correct SRC_URI and other uris Steve Sakoman
2025-02-07 22:06 ` [OE-core][styhead 10/12] libxml-parser-perl: correct SRC_URI Steve Sakoman
2025-02-07 22:06 ` [OE-core][styhead 11/12] oeqa/gitarchive: Fix syntax warning Steve Sakoman
2025-02-07 22:06 ` [OE-core][styhead 12/12] lrzsz: update SRC_URI to avoid redirect Steve Sakoman
-- strict thread matches above, loose matches on Subject: below --
2024-12-12 14:07 [OE-core][styhead 00/12] Patch review Steve Sakoman
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=cover.1738965898.git.steve@sakoman.com \
--to=steve@sakoman.com \
--cc=openembedded-core@lists.openembedded.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