From: Armin Kuster <akuster808@gmail.com>
To: openembedded-core@openembedded.org
Subject: [warrior 00/14] Patch review
Date: Mon, 17 Feb 2020 08:00:38 -0800 [thread overview]
Message-ID: <cover.1581955142.git.akuster808@gmail.com> (raw)
A few more for the 2.7.3 release.
Please have comments back by Wednesday
Passed A-full
The following changes since commit a63d59f64a2d1f450a7639426cae8e0373a2d764:
sanity.bbclass: Move sanity_info from conf to cache (2020-01-25 08:37:48 -0800)
are available in the Git repository at:
git://git.openembedded.org/openembedded-core-contrib stable/warrior-nut
http://cgit.openembedded.org//log/?h=stable/warrior-nut
Anuj Mittal (1):
cpio: fix CVE-2019-14866
Armin Kuster (2):
python2: add ntpath
timezone: update to 2019b
Bruce Ashfield (4):
linux-yocto/4.19: update to v4.19.72
linux-yocto/4.19: update to v4.19.78
linux-yocto/4.19: update to v4.19.84
linux-yocto/4.19: update to v4.19.87
Lee Chee Yang (1):
rsync: whitelist CVE-2017-16548
Oleksandr Kravchuk (2):
linux-firmware: bump to 20190618
linux-firmware: add PE back
Otavio Salvador (1):
linux-firmware: Upgrade 20190618 -> 20190815
Rahul Chauhan (1):
libxml2: Fix CVE-2019-19956
Samuli Piippo (1):
linux-firmware: update packaging for brcm files
Zang Ruochen (1):
timezone:upgrade 2019b -> 2019c
.../libxml/libxml2/fix-CVE-2019-19956.patch | 38 +++
meta/recipes-core/libxml/libxml2_2.9.8.bb | 1 +
.../python/python/python2-manifest.json | 1 +
meta/recipes-devtools/rsync/rsync_3.1.3.bb | 3 +
.../cpio/cpio-2.12/CVE-2019-14866.patch | 316 ++++++++++++++++++
meta/recipes-extended/cpio/cpio_2.12.bb | 1 +
meta/recipes-extended/timezone/timezone.inc | 10 +-
...ware_git.bb => linux-firmware_20190815.bb} | 26 +-
.../linux/linux-yocto-rt_4.19.bb | 6 +-
.../linux/linux-yocto-tiny_4.19.bb | 8 +-
meta/recipes-kernel/linux/linux-yocto_4.19.bb | 20 +-
11 files changed, 397 insertions(+), 33 deletions(-)
create mode 100644 meta/recipes-core/libxml/libxml2/fix-CVE-2019-19956.patch
create mode 100644 meta/recipes-extended/cpio/cpio-2.12/CVE-2019-14866.patch
rename meta/recipes-kernel/linux-firmware/{linux-firmware_git.bb => linux-firmware_20190815.bb} (98%)
--
2.17.1
next reply other threads:[~2020-02-17 16:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-17 16:00 Armin Kuster [this message]
2020-02-17 16:00 ` [warrior 01/14] libxml2: Fix CVE-2019-19956 Armin Kuster
2020-02-17 16:00 ` [warrior 02/14] rsync: whitelist CVE-2017-16548 Armin Kuster
2020-02-17 16:00 ` [warrior 03/14] cpio: fix CVE-2019-14866 Armin Kuster
2020-02-17 16:00 ` [warrior 04/14] linux-yocto/4.19: update to v4.19.72 Armin Kuster
2020-02-17 16:00 ` [warrior 05/14] linux-yocto/4.19: update to v4.19.78 Armin Kuster
2020-02-17 16:00 ` [warrior 06/14] linux-yocto/4.19: update to v4.19.84 Armin Kuster
2020-02-17 16:00 ` [warrior 07/14] linux-yocto/4.19: update to v4.19.87 Armin Kuster
2020-02-17 16:00 ` [warrior 08/14] python2: add ntpath Armin Kuster
2020-02-17 16:00 ` [warrior 09/14] timezone: update to 2019b Armin Kuster
2020-02-17 16:00 ` [warrior 10/14] timezone:upgrade 2019b -> 2019c Armin Kuster
2020-02-17 16:00 ` [warrior 11/14] linux-firmware: bump to 20190618 Armin Kuster
2020-02-17 16:00 ` [warrior 12/14] linux-firmware: add PE back Armin Kuster
2020-02-17 16:00 ` [warrior 13/14] linux-firmware: Upgrade 20190618 -> 20190815 Armin Kuster
2020-02-17 16:00 ` [warrior 14/14] linux-firmware: update packaging for brcm files Armin Kuster
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.1581955142.git.akuster808@gmail.com \
--to=akuster808@gmail.com \
--cc=openembedded-core@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