From: "Anuj Mittal" <anuj.mittal@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [zeus][PATCH 0/4] zeus review request
Date: Mon, 10 Aug 2020 22:52:43 +0800 [thread overview]
Message-ID: <cover.1597071024.git.anuj.mittal@intel.com> (raw)
Last set of changes before last zeus dot release. Please review.
Thanks,
Anuj
The following changes since commit 74e22d0d2b61d0014f408972725469bb7a024622:
gstreamer1.0: fix builds with make 4.3 (2020-07-28 16:16:52 +0800)
are available in the Git repository at:
git://push.openembedded.org/openembedded-core-contrib anujm/zeus
Konrad Weihmann (1):
pypi.bbclass: mind package suffix on version check
Li Zhou (1):
go: Security Advisory - go - CVE-2020-15586
Rahul Taya (1):
libpcre: Add fix for CVE-2020-14155
Tim Orling (1):
pypi.bbclass: use new pypi UPSTREAM_CHECK_URI
meta/classes/pypi.bbclass | 4 +-
meta/recipes-devtools/go/go-1.12.inc | 1 +
.../go/go-1.12/CVE-2020-15586.patch | 131 ++++++++++++++++++
.../libpcre/libpcre/CVE-2020-14155.patch | 41 ++++++
meta/recipes-support/libpcre/libpcre_8.43.bb | 1 +
5 files changed, 176 insertions(+), 2 deletions(-)
create mode 100644 meta/recipes-devtools/go/go-1.12/CVE-2020-15586.patch
create mode 100644 meta/recipes-support/libpcre/libpcre/CVE-2020-14155.patch
--
2.26.2
next reply other threads:[~2020-08-10 14:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-10 14:52 Anuj Mittal [this message]
2020-08-10 14:52 ` [zeus][PATCH 1/4] pypi.bbclass: mind package suffix on version check Anuj Mittal
2020-08-10 14:52 ` [zeus][PATCH 2/4] pypi.bbclass: use new pypi UPSTREAM_CHECK_URI Anuj Mittal
2020-08-10 14:52 ` [zeus][PATCH 3/4] go: Security Advisory - go - CVE-2020-15586 Anuj Mittal
2020-08-10 14:52 ` [zeus][PATCH 4/4] libpcre: Add fix for CVE-2020-14155 Anuj Mittal
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.1597071024.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.