From: Armin Kuster <akuster808@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: [PATCH 0/7] Thud pull request
Date: Tue, 28 May 2019 08:25:21 -0700 [thread overview]
Message-ID: <cover.1559056652.git.akuster808@gmail.com> (raw)
These are good to go for thud.
The following changes since commit 4cd3a39f22a2712bfa8fc657d09fe2c7765a4005:
rtmpdump: Switch to using GNU TLS instead of openssl10 (2019-03-24 18:44:58 -0700)
are available in the git repository at:
git://git.openembedded.org/meta-openembedded thud-next
http://cgit.openembedded.org/meta-openembedded/log/?h=thud-next
Andrej Valek (1):
ntp: upgrade 4.2.8p12 -> 4.2.8p13
Armin Kuster (1):
mariadb: update to 5.5.64
Martin Jansa (1):
ccid: fix SRC_URI
Nicolas Dechesne (1):
cpupower: remove LIC_FILES_CHKSUM
Qi.Chen@windriver.com (1):
netkit-rsh: add tag to CVE patch
Tom Rini (1):
netkit-rsh: don't build under musl
Yi Zhao (1):
netkit-rsh: security fixes
.../CVE-2019-7282-and-CVE-2019-7283.patch | 35 ++++++++++++++++++++++
.../recipes-netkit/netkit-rsh/netkit-rsh_0.17.bb | 3 ++
.../ntp/{ntp_4.2.8p12.bb => ntp_4.2.8p13.bb} | 6 ++--
...b-native_5.5.62.bb => mariadb-native_5.5.64.bb} | 0
meta-oe/recipes-dbs/mysql/mariadb.inc | 4 +--
.../mysql/{mariadb_5.5.62.bb => mariadb_5.5.64.bb} | 0
meta-oe/recipes-kernel/cpupower/cpupower.bb | 1 -
meta-oe/recipes-support/ccid/ccid_1.4.24.bb | 4 +--
8 files changed, 45 insertions(+), 8 deletions(-)
create mode 100644 meta-networking/recipes-netkit/netkit-rsh/netkit-rsh/CVE-2019-7282-and-CVE-2019-7283.patch
rename meta-networking/recipes-support/ntp/{ntp_4.2.8p12.bb => ntp_4.2.8p13.bb} (96%)
rename meta-oe/recipes-dbs/mysql/{mariadb-native_5.5.62.bb => mariadb-native_5.5.64.bb} (100%)
rename meta-oe/recipes-dbs/mysql/{mariadb_5.5.62.bb => mariadb_5.5.64.bb} (100%)
--
2.7.4
reply other threads:[~2019-05-28 15:25 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.1559056652.git.akuster808@gmail.com \
--to=akuster808@gmail.com \
--cc=openembedded-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox