From: Steve Sakoman <steve@sakoman.com>
To: openembedded-core@lists.openembedded.org
Subject: [OE-core][dunfell 00/17] Pull request (cover letter only)
Date: Wed, 8 Dec 2021 05:08:53 -1000 [thread overview]
Message-ID: <cover.1638976040.git.steve@sakoman.com> (raw)
The following changes since commit f61fcb6e176f19f1e768ce63a693f238713c8887:
openssh: remove redundant BSD license (2021-12-02 05:11:21 -1000)
are available in the Git repository at:
git://git.openembedded.org/openembedded-core-contrib stable/dunfell-next
http://cgit.openembedded.org/openembedded-core-contrib/log/?h=stable/dunfell-next
Dhruva Gole (1):
scripts/checklayer/common.py: Fixed a minor grammatical error
Eero Aaltonen (1):
cmake: FindGTest: Add target for gmock library
Jate Sujjavanich (2):
libdnf: Backport bugfix for upgrade calc
dnf: Backport bugfix for upgrade
Khem Raj (1):
libunwind: Backport a fix for -fno-common option to compile
Neetika Singh (1):
glib-2.0: Add security fixes
Pavel Zhukov (2):
busybox: Fix for CVE-2021-42374
busybox: Fix for CVE-2021-42376
Quentin Schulz (1):
README.OE-Core.md: update URLs
Ranjitsinh Rathod (2):
ncurses: Fix for CVE-2021-39537
libsolv: update tag for missing CVEs
Richard Purdie (2):
buildhistory: Fix srcrevs output
oeqa/parselogs: Fix quoting
Ross Burton (1):
vim: fix CVE-2021-3968 and CVE-2021-3973
Steve Sakoman (3):
bind: update to 9.11.33
bind: update to 9.11.34
bind: update to 9.11.35
README.OE-Core | 10 +-
meta/classes/buildhistory.bbclass | 30 +-
meta/lib/oeqa/runtime/cases/parselogs.py | 14 +-
.../bind/{bind_9.11.32.bb => bind_9.11.35.bb} | 2 +-
.../busybox/busybox/CVE-2021-42374.patch | 53 +++
.../busybox/busybox/CVE-2021-42376.patch | 138 ++++++
meta/recipes-core/busybox/busybox_1.31.1.bb | 2 +
.../glib-2.0/glib-2.0/CVE-2021-27218.patch | 129 ++++++
.../glib-2.0/glib-2.0/CVE-2021-27219-01.patch | 170 +++++++
.../glib-2.0/glib-2.0/CVE-2021-27219-02.patch | 249 +++++++++++
.../glib-2.0/glib-2.0/CVE-2021-27219-03.patch | 131 ++++++
.../glib-2.0/glib-2.0/CVE-2021-27219-04.patch | 298 +++++++++++++
.../glib-2.0/glib-2.0/CVE-2021-27219-05.patch | 54 +++
.../glib-2.0/glib-2.0/CVE-2021-27219-06.patch | 101 +++++
.../glib-2.0/glib-2.0/CVE-2021-27219-07.patch | 76 ++++
.../glib-2.0/glib-2.0/CVE-2021-27219-08.patch | 101 +++++
.../glib-2.0/glib-2.0/CVE-2021-27219-09.patch | 100 +++++
.../glib-2.0/glib-2.0/CVE-2021-27219-10.patch | 59 +++
.../glib-2.0/glib-2.0/CVE-2021-27219-11.patch | 63 +++
.../glib-2.0/CVE-2021-27219-reg1-1.patch | 36 ++
.../glib-2.0/CVE-2021-27219-reg1-2.patch | 38 ++
.../glib-2.0/CVE-2021-27219-reg1-4.patch | 38 ++
.../glib-2.0/CVE-2021-27219-reg1-5.patch | 100 +++++
.../glib-2.0/CVE-2021-27219-reg2-1.patch | 49 ++
.../glib-2.0/CVE-2021-27219-reg2-2.patch | 43 ++
.../glib-2.0/CVE-2021-27219-reg2-3.patch | 232 ++++++++++
.../glib-2.0/glib-2.0/CVE-2021-28153-1.patch | 27 ++
.../glib-2.0/glib-2.0/CVE-2021-28153-2.patch | 42 ++
.../glib-2.0/glib-2.0/CVE-2021-28153-3.patch | 57 +++
.../glib-2.0/glib-2.0/CVE-2021-28153-4.patch | 265 +++++++++++
.../glib-2.0/glib-2.0/CVE-2021-28153-5.patch | 55 +++
meta/recipes-core/glib-2.0/glib-2.0_2.62.6.bb | 24 +
.../ncurses/files/CVE-2021-39537.patch | 30 ++
meta/recipes-core/ncurses/ncurses_6.2.bb | 1 +
.../cmake/cmake-native_3.16.5.bb | 1 +
...ndGTest-Add-target-for-gmock-library.patch | 255 +++++++++++
...ackages-in-upgrade-job-RhBug-1728252.patch | 60 +++
meta/recipes-devtools/dnf/dnf_4.2.2.bb | 1 +
...job-goal.upgrade-with-sltr-as-target.patch | 58 +++
meta/recipes-devtools/libdnf/libdnf_0.28.1.bb | 1 +
.../libsolv/files/CVE-2021-3200.patch | 9 +-
...0001-Fix-compilation-with-fno-common.patch | 420 ++++++++++++++++++
.../libunwind/libunwind_1.3.1.bb | 1 +
...rash-when-using-CTRL-W-f-without-fin.patch | 92 ++++
meta/recipes-support/vim/vim.inc | 4 +
scripts/lib/checklayer/cases/common.py | 2 +-
46 files changed, 3688 insertions(+), 33 deletions(-)
rename meta/recipes-connectivity/bind/{bind_9.11.32.bb => bind_9.11.35.bb} (98%)
create mode 100644 meta/recipes-core/busybox/busybox/CVE-2021-42374.patch
create mode 100644 meta/recipes-core/busybox/busybox/CVE-2021-42376.patch
create mode 100644 meta/recipes-core/glib-2.0/glib-2.0/CVE-2021-27218.patch
create mode 100644 meta/recipes-core/glib-2.0/glib-2.0/CVE-2021-27219-01.patch
create mode 100644 meta/recipes-core/glib-2.0/glib-2.0/CVE-2021-27219-02.patch
create mode 100644 meta/recipes-core/glib-2.0/glib-2.0/CVE-2021-27219-03.patch
create mode 100644 meta/recipes-core/glib-2.0/glib-2.0/CVE-2021-27219-04.patch
create mode 100644 meta/recipes-core/glib-2.0/glib-2.0/CVE-2021-27219-05.patch
create mode 100644 meta/recipes-core/glib-2.0/glib-2.0/CVE-2021-27219-06.patch
create mode 100644 meta/recipes-core/glib-2.0/glib-2.0/CVE-2021-27219-07.patch
create mode 100644 meta/recipes-core/glib-2.0/glib-2.0/CVE-2021-27219-08.patch
create mode 100644 meta/recipes-core/glib-2.0/glib-2.0/CVE-2021-27219-09.patch
create mode 100644 meta/recipes-core/glib-2.0/glib-2.0/CVE-2021-27219-10.patch
create mode 100644 meta/recipes-core/glib-2.0/glib-2.0/CVE-2021-27219-11.patch
create mode 100644 meta/recipes-core/glib-2.0/glib-2.0/CVE-2021-27219-reg1-1.patch
create mode 100644 meta/recipes-core/glib-2.0/glib-2.0/CVE-2021-27219-reg1-2.patch
create mode 100644 meta/recipes-core/glib-2.0/glib-2.0/CVE-2021-27219-reg1-4.patch
create mode 100644 meta/recipes-core/glib-2.0/glib-2.0/CVE-2021-27219-reg1-5.patch
create mode 100644 meta/recipes-core/glib-2.0/glib-2.0/CVE-2021-27219-reg2-1.patch
create mode 100644 meta/recipes-core/glib-2.0/glib-2.0/CVE-2021-27219-reg2-2.patch
create mode 100644 meta/recipes-core/glib-2.0/glib-2.0/CVE-2021-27219-reg2-3.patch
create mode 100644 meta/recipes-core/glib-2.0/glib-2.0/CVE-2021-28153-1.patch
create mode 100644 meta/recipes-core/glib-2.0/glib-2.0/CVE-2021-28153-2.patch
create mode 100644 meta/recipes-core/glib-2.0/glib-2.0/CVE-2021-28153-3.patch
create mode 100644 meta/recipes-core/glib-2.0/glib-2.0/CVE-2021-28153-4.patch
create mode 100644 meta/recipes-core/glib-2.0/glib-2.0/CVE-2021-28153-5.patch
create mode 100644 meta/recipes-core/ncurses/files/CVE-2021-39537.patch
create mode 100644 meta/recipes-devtools/cmake/cmake/0006-cmake-FindGTest-Add-target-for-gmock-library.patch
create mode 100644 meta/recipes-devtools/dnf/dnf/0040-Keep-installed-packages-in-upgrade-job-RhBug-1728252.patch
create mode 100644 meta/recipes-devtools/libdnf/libdnf/0040-Mark-job-goal.upgrade-with-sltr-as-target.patch
create mode 100644 meta/recipes-support/libunwind/libunwind/0001-Fix-compilation-with-fno-common.patch
create mode 100644 meta/recipes-support/vim/files/0002-patch-8.2.3611-crash-when-using-CTRL-W-f-without-fin.patch
--
2.25.1
next reply other threads:[~2021-12-08 15:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-08 15:08 Steve Sakoman [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-04-01 0:32 [OE-core][dunfell 00/17] Pull request (cover letter only) Steve Sakoman
2021-02-17 23:51 Steve Sakoman
2020-07-30 3:42 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.1638976040.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.