From: Steve Sakoman <steve@sakoman.com>
To: openembedded-core@lists.openembedded.org
Subject: [OE-core][dunfell 0/8] Pull request (cover letter only)
Date: Fri, 13 Jan 2023 04:40:53 -1000 [thread overview]
Message-ID: <cover.1673620619.git.steve@sakoman.com> (raw)
This is the final pull request for the 3.1.22 release build on Monday.
The following changes since commit deb919a693e4371ace649680ca06ca6b6e3da4e2:
lib/buildstats: fix parsing of trees with reduced_proc_pressure directories (2023-01-06 17:34:50 +0000)
are available in the Git repository at:
https://git.openembedded.org/openembedded-core-contrib stable/dunfell-next
http://cgit.openembedded.org/openembedded-core-contrib/log/?h=stable/dunfell-next
Changqing Li (1):
base.bbclass: Fix way to check ccache path
Chee Yang Lee (1):
libksba: fix CVE-2022-47629
Hitendra Prajapati (1):
grub2: Fix CVE-2022-2601 & CVE-2022-3775
Luis (1):
rm_work.bbclass: use HOSTTOOLS 'rm' binary exclusively
Pavel Zhukov (1):
oeqa/rpm.py: Increase timeout and add debug output
Steve Sakoman (3):
ovmf: fix gcc12 warning in GenFfs
ovmf: fix gcc12 warning in LzmaEnc
ovmf: fix gcc12 warning for device path handling
meta/classes/base.bbclass | 2 +-
meta/classes/rm_work.bbclass | 15 ++-
meta/lib/oeqa/runtime/cases/rpm.py | 23 ++--
.../grub/files/CVE-2022-2601.patch | 87 +++++++++++++
.../grub/files/CVE-2022-3775.patch | 97 +++++++++++++++
...erflow-in-grub_font_get_glyph_intern.patch | 117 ++++++++++++++++++
meta/recipes-bsp/grub/grub2.inc | 3 +
...1-Basetools-genffs-fix-gcc12-warning.patch | 49 ++++++++
...-Basetools-lzmaenc-fix-gcc12-warning.patch | 53 ++++++++
...001-Basetools-turn-off-gcc12-warning.patch | 41 ++++++
meta/recipes-core/ovmf/ovmf_git.bb | 3 +
.../libksba/libksba/CVE-2022-47629.patch | 69 +++++++++++
meta/recipes-support/libksba/libksba_1.3.5.bb | 4 +-
13 files changed, 545 insertions(+), 18 deletions(-)
create mode 100644 meta/recipes-bsp/grub/files/CVE-2022-2601.patch
create mode 100644 meta/recipes-bsp/grub/files/CVE-2022-3775.patch
create mode 100644 meta/recipes-bsp/grub/files/font-Fix-size-overflow-in-grub_font_get_glyph_intern.patch
create mode 100644 meta/recipes-core/ovmf/ovmf/0001-Basetools-genffs-fix-gcc12-warning.patch
create mode 100644 meta/recipes-core/ovmf/ovmf/0001-Basetools-lzmaenc-fix-gcc12-warning.patch
create mode 100644 meta/recipes-core/ovmf/ovmf/0001-Basetools-turn-off-gcc12-warning.patch
create mode 100644 meta/recipes-support/libksba/libksba/CVE-2022-47629.patch
--
2.25.1
next reply other threads:[~2023-01-13 14:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-13 14:40 Steve Sakoman [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-11-09 2:24 [OE-core][dunfell 0/8] Pull request (cover letter only) Steve Sakoman
2022-05-04 22:59 Steve Sakoman
2022-04-06 16:37 Steve Sakoman
2020-05-14 15:40 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.1673620619.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