From: "akuster" <akuster808@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: [warrior 0/8] Patch review
Date: Tue, 19 May 2020 07:51:07 -0700 [thread overview]
Message-ID: <cover.1589899663.git.akuster808@gmail.com> (raw)
Here are the next set of changes for warrior last dot release.
Please have comments back by Friday.
The following changes since commit ae341aed81be28232cc34daf4684bc0922f17699:
yocto-uninative.inc: version 2.8 updates glibc to 2.31 (2020-03-26 07:04:11 -0700)
are available in the Git repository at:
https://git.openembedded.org/openembedded-core-contrib stable/warrior-nut
http://cgit.openembedded.org//log/?h=stable/warrior-nut
Adrian Bunk (3):
git: Upgrade 2.20.1 -> 2.20.4
python: Upgrade 2.7.17 -> 2.17.18
openssl: Upgrade 1.1.1d -> 1.1.1e
Alexander Kanavin (1):
openssl: update to 1.1.1f
Denys Dmytriyenko (1):
openssl: recommend cryptodev-module for corresponding PACKAGECONFIG
Jan Luebbe (1):
openssl: upgrade 1.1.1f -> 1.1.1g
Lee Chee Yang (1):
cve-check: CPE version '-' as all version
Richard Purdie (1):
openssl: Fix reproducibility issue
meta/classes/cve-check.bbclass | 2 +-
.../openssl/openssl/CVE-2019-1551.patch | 758 ------------------
.../openssl/openssl/reproducible.patch | 32 +
.../{openssl_1.1.1d.bb => openssl_1.1.1g.bb} | 7 +-
.../recipes-core/meta/cve-update-db-native.bb | 2 +-
meta/recipes-devtools/git/git_2.20.1.bb | 11 -
meta/recipes-devtools/git/git_2.20.4.bb | 11 +
...tive_2.7.17.bb => python-native_2.7.18.bb} | 0
meta/recipes-devtools/python/python.inc | 6 +-
.../{python_2.7.17.bb => python_2.7.18.bb} | 0
10 files changed, 51 insertions(+), 778 deletions(-)
delete mode 100644 meta/recipes-connectivity/openssl/openssl/CVE-2019-1551.patch
create mode 100644 meta/recipes-connectivity/openssl/openssl/reproducible.patch
rename meta/recipes-connectivity/openssl/{openssl_1.1.1d.bb => openssl_1.1.1g.bb} (97%)
delete mode 100644 meta/recipes-devtools/git/git_2.20.1.bb
create mode 100644 meta/recipes-devtools/git/git_2.20.4.bb
rename meta/recipes-devtools/python/{python-native_2.7.17.bb => python-native_2.7.18.bb} (100%)
rename meta/recipes-devtools/python/{python_2.7.17.bb => python_2.7.18.bb} (100%)
--
2.17.1
next reply other threads:[~2020-05-19 14:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-19 14:51 akuster [this message]
2020-05-19 14:51 ` [warrior 1/8] git: Upgrade 2.20.1 -> 2.20.4 akuster
2020-05-19 14:51 ` [warrior 2/8] python: Upgrade 2.7.17 -> 2.17.18 akuster
2020-05-19 14:51 ` [warrior 3/8] openssl: Fix reproducibility issue akuster
2020-05-19 14:51 ` [warrior 4/8] openssl: recommend cryptodev-module for corresponding PACKAGECONFIG akuster
2020-05-19 14:51 ` [warrior 5/8] openssl: Upgrade 1.1.1d -> 1.1.1e akuster
2020-05-19 14:51 ` [warrior 6/8] openssl: update to 1.1.1f akuster
2020-05-19 14:51 ` [warrior 7/8] openssl: upgrade 1.1.1f -> 1.1.1g akuster
2020-05-19 14:51 ` [warrior 8/8] cve-check: CPE version '-' as all version akuster
-- strict thread matches above, loose matches on Subject: below --
2019-10-06 15:24 [warrior] 0/8] Patch review Armin Kuster
2019-10-06 16:38 ` Martin Jansa
2019-10-06 17:31 ` akuster808
2019-07-21 14:41 [warrior] 0/8] patch review Armin Kuster
2019-07-21 14:47 ` Khem Raj
2019-09-02 11:47 ` Martin Jansa
2019-09-02 17:49 ` akuster808
2019-09-03 2:40 ` akuster808
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.1589899663.git.akuster808@gmail.com \
--to=akuster808@gmail.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.