From: Steve Sakoman <steve@sakoman.com>
To: openembedded-core@lists.openembedded.org
Subject: [OE-core][kirkstone 00/14] Pull request (cover letter only)
Date: Tue, 28 Mar 2023 04:23:06 -1000 [thread overview]
Message-ID: <cover.1680013231.git.steve@sakoman.com> (raw)
The following changes since commit 7df46e003ea76cf7d5b7263f23bd6e6a781bd22c:
base-files: Drop localhost.localdomain from hosts file (2023-03-17 04:52:21 -1000)
are available in the Git repository at:
https://git.openembedded.org/openembedded-core-contrib stable/kirkstone-next
http://cgit.openembedded.org/openembedded-core-contrib/log/?h=stable/kirkstone-next
Alexander Kanavin (1):
devtool/upgrade: do not delete the workspace/recipes directory
Chee Yang Lee (1):
git: ignore CVE-2023-22743
Khem Raj (1):
systemd.bbclass: Add /usr/lib/systemd to searchpaths as well
Martin Jansa (3):
timezone: use 'tz' subdir instead of ${WORKDIR} directly
tzdata: use separate B instead of WORKDIR for zic output
tzcode-native: fix build with gcc-13 on host
Mikko Rapeli (1):
oeqa rtc.py: skip if read-only-rootfs
Pawan Badganchi (1):
curl: Add fix for CVE-2023-23914, CVE-2023-23915
Peter Marko (1):
systemd: fix CVE-2022-4415
Piotr Łobacz (1):
systemd: fix wrong nobody-group assignment
Richard Purdie (1):
pybootchartui: Fix python syntax issue
Romuald Jeanne (1):
image_types: fix multiubi var init
Ross Burton (1):
lib/resulttool: fix typo breaking resulttool log --ptest
Tim Orling (1):
cracklib: update github branch to 'main'
meta/classes/image_types.bbclass | 3 +
meta/classes/systemd.bbclass | 1 +
meta/lib/oeqa/runtime/cases/rtc.py | 8 +-
.../systemd/systemd/CVE-2022-4415-1.patch | 109 +++++
.../systemd/systemd/CVE-2022-4415-2.patch | 391 ++++++++++++++++++
meta/recipes-core/systemd/systemd_250.5.bb | 4 +-
meta/recipes-devtools/git/git_2.35.7.bb | 2 +
.../cracklib/cracklib_2.9.8.bb | 2 +-
meta/recipes-extended/timezone/timezone.inc | 6 +-
.../timezone/tzcode-native.bb | 3 +-
...0001-Fix-C23-related-conformance-bug.patch | 301 ++++++++++++++
meta/recipes-extended/timezone/tzdata.bb | 16 +-
.../curl/curl/CVE-2023-23914_5-1.patch | 280 +++++++++++++
.../curl/curl/CVE-2023-23914_5-2.patch | 23 ++
.../curl/curl/CVE-2023-23914_5-3.patch | 45 ++
.../curl/curl/CVE-2023-23914_5-4.patch | 48 +++
.../curl/curl/CVE-2023-23914_5-5.patch | 118 ++++++
meta/recipes-support/curl/curl_7.82.0.bb | 5 +
scripts/lib/devtool/upgrade.py | 3 -
scripts/lib/resulttool/resultutils.py | 2 +-
.../pybootchartgui/pybootchartgui/parsing.py | 2 +-
21 files changed, 1351 insertions(+), 21 deletions(-)
create mode 100644 meta/recipes-core/systemd/systemd/CVE-2022-4415-1.patch
create mode 100644 meta/recipes-core/systemd/systemd/CVE-2022-4415-2.patch
create mode 100644 meta/recipes-extended/timezone/tzcode/0001-Fix-C23-related-conformance-bug.patch
create mode 100644 meta/recipes-support/curl/curl/CVE-2023-23914_5-1.patch
create mode 100644 meta/recipes-support/curl/curl/CVE-2023-23914_5-2.patch
create mode 100644 meta/recipes-support/curl/curl/CVE-2023-23914_5-3.patch
create mode 100644 meta/recipes-support/curl/curl/CVE-2023-23914_5-4.patch
create mode 100644 meta/recipes-support/curl/curl/CVE-2023-23914_5-5.patch
--
2.34.1
reply other threads:[~2023-03-28 14:23 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=cover.1680013231.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