From: "Anuj Mittal" <anuj.mittal@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [gatesgarth][PATCH 0/7] pull request (cover letter only)
Date: Wed, 5 May 2021 22:46:34 +0800 [thread overview]
Message-ID: <cover.1620225552.git.anuj.mittal@intel.com> (raw)
Final pull request before the final gatesgarth dot release.
Thanks,
Anuj
The following changes since commit 8b0aef3f504d650c3208f11b62a7926aa90967f1:
sanity: Further improve directory sanity tests (2021-04-23 23:20:58 +0800)
are available in the Git repository at:
git://push.openembedded.org/openembedded-core-contrib stable/gatesgarth-next
Changqing Li (2):
cairo: fix CVE-2020-35492
gdk-pixbuf: fix CVE-2021-20240
Chen Qi (1):
rsync: fix CVE-2020-14387
Marek Vasut (1):
linux-firmware: Package RSI 911x WiFi firmware
Mark Hatle (1):
populate_sdk_ext: Avoid copying and producing .pyc files
Richard Purdie (1):
yocto-check-layer: Avoid bug when iterating and autoadding
dependencies
hongxu (1):
deb: apply postinstall on sdk
meta/classes/populate_sdk_ext.bbclass | 4 +-
meta/lib/oe/copy_buildsystem.py | 6 +-
meta/lib/oe/package_manager/deb/sdk.py | 4 +
...-the-hostname-in-the-certificate-whe.patch | 31 +++++
meta/recipes-devtools/rsync/rsync_3.2.3.bb | 1 +
.../gdk-pixbuf/CVE-2021-20240.patch | 40 ++++++
.../gdk-pixbuf/gdk-pixbuf_2.40.0.bb | 1 +
.../cairo/cairo/CVE-2020-35492.patch | 121 ++++++++++++++++++
.../cairo/cairo/bug-image-compositor.ref.png | Bin 0 -> 185 bytes
meta/recipes-graphics/cairo/cairo_1.16.0.bb | 11 ++
.../linux-firmware/linux-firmware_20210208.bb | 11 ++
scripts/yocto-check-layer | 3 +
12 files changed, 229 insertions(+), 4 deletions(-)
create mode 100644 meta/recipes-devtools/rsync/files/0001-rsync-ssl-Verify-the-hostname-in-the-certificate-whe.patch
create mode 100644 meta/recipes-gnome/gdk-pixbuf/gdk-pixbuf/CVE-2021-20240.patch
create mode 100644 meta/recipes-graphics/cairo/cairo/CVE-2020-35492.patch
create mode 100644 meta/recipes-graphics/cairo/cairo/bug-image-compositor.ref.png
--
2.30.2
reply other threads:[~2021-05-05 14:46 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.1620225552.git.anuj.mittal@intel.com \
--to=anuj.mittal@intel.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.