From: Steve Sakoman <steve@sakoman.com>
To: openembedded-core@lists.openembedded.org
Subject: [OE-core][kirkstone 0/6] Patch review
Date: Tue, 4 Apr 2023 16:29:28 -1000 [thread overview]
Message-ID: <cover.1680661617.git.steve@sakoman.com> (raw)
Please review this final set of patches for the kirkstone 4.0.9 release and
have comments back by end of day Thursday.
Passed a-full on autobuilder:
https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/5147
The following changes since commit 3eeab90fd45a1e8de6d9d16dfdec79c72639614b:
rsync: Turn on -pedantic-errors at the end of 'configure' (2023-03-30 08:29:50 -1000)
are available in the Git repository at:
https://git.openembedded.org/openembedded-core-contrib stable/kirkstone-nut
http://cgit.openembedded.org/openembedded-core-contrib/log/?h=stable/kirkstone-nut
Alexander Kanavin (1):
patchelf: replace a rejected patch with an equivalent
uninative.bbclass tweak
Michael Halstead (2):
uninative: Upgrade to 3.8.1 to include libgcc
uninative: Upgrade to 3.9 to include glibc 2.37
Shubham Kulkarni (1):
go-runtime: Security fix for CVE-2022-41723
Simone Weiss (1):
json-c: Add ptest for json-c
pawan (1):
curl: Add fix for CVE-2023-23916
meta/classes/uninative.bbclass | 2 +
.../distro/include/ptest-packagelists.inc | 1 +
meta/conf/distro/include/yocto-uninative.inc | 10 +-
meta/recipes-devtools/go/go-1.17.13.inc | 1 +
.../go/go-1.18/CVE-2022-41723.patch | 156 +++++++++++++
meta/recipes-devtools/json-c/json-c/run-ptest | 20 ++
meta/recipes-devtools/json-c/json-c_0.15.bb | 16 +-
.../patchelf/handle-read-only-files.patch | 65 ------
.../patchelf/patchelf_0.14.5.bb | 1 -
.../curl/curl/CVE-2023-23916.patch | 219 ++++++++++++++++++
meta/recipes-support/curl/curl_7.82.0.bb | 1 +
11 files changed, 419 insertions(+), 73 deletions(-)
create mode 100644 meta/recipes-devtools/go/go-1.18/CVE-2022-41723.patch
create mode 100644 meta/recipes-devtools/json-c/json-c/run-ptest
delete mode 100644 meta/recipes-devtools/patchelf/patchelf/handle-read-only-files.patch
create mode 100644 meta/recipes-support/curl/curl/CVE-2023-23916.patch
--
2.34.1
next reply other threads:[~2023-04-05 2:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-05 2:29 Steve Sakoman [this message]
2023-04-05 2:29 ` [OE-core][kirkstone 1/6] go-runtime: Security fix for CVE-2022-41723 Steve Sakoman
2023-04-05 2:29 ` [OE-core][kirkstone 2/6] curl: Add fix for CVE-2023-23916 Steve Sakoman
2023-04-05 2:29 ` [OE-core][kirkstone 3/6] json-c: Add ptest for json-c Steve Sakoman
2023-04-05 2:29 ` [OE-core][kirkstone 4/6] patchelf: replace a rejected patch with an equivalent uninative.bbclass tweak Steve Sakoman
2023-04-05 2:29 ` [OE-core][kirkstone 5/6] uninative: Upgrade to 3.8.1 to include libgcc Steve Sakoman
2023-04-05 2:29 ` [OE-core][kirkstone 6/6] uninative: Upgrade to 3.9 to include glibc 2.37 Steve Sakoman
-- strict thread matches above, loose matches on Subject: below --
2023-10-21 15:28 [OE-core][kirkstone 0/6] Patch review Steve Sakoman
2024-01-08 16:14 Steve Sakoman
2024-01-21 18:57 Steve Sakoman
2024-05-13 12:18 Steve Sakoman
2024-07-20 12:42 Steve Sakoman
2024-08-25 18:49 Steve Sakoman
2024-09-05 12:40 Steve Sakoman
2025-03-10 13:36 Steve Sakoman
2025-03-24 19:36 Steve Sakoman
2025-05-09 16:16 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.1680661617.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