From: Joshua Lock <joshua.g.lock@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/4] Fido pull request
Date: Tue, 16 Feb 2016 14:30:50 +0000 [thread overview]
Message-ID: <cover.1455631402.git.joshua.g.lock@intel.com> (raw)
Please consider the following fixes for inclusion in the Fido branch.
- libpcre security fix not required in jethro or master because the newer
version they carry isn't affected
- backport a fix for some memory leaks in rpmresolve
- backport a fix for kernel.bbclass which already exists in jethro & master
- remove a stray tzdata file, this change isn't required for jethro or master as
the file isn't present in those branches
The following changes since commit 4dea3e7b9a0041e7359981e68c561e7de8ad3ae5:
dpkg: Security fix CVE-2015-0860 (2016-02-07 17:22:53 +0000)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib joshuagl/fido-next
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=joshuagl/fido-next
Armin Kuster (1):
libpcre: Security fixes and package update.
Mariano Lopez (1):
rpmresolve.c: Fix unfreed pointers that keep DB opened
Markus Lehtonen (1):
kernel.bbclass: do not mv/link sources when externalsrc enabled
Martin Jansa (1):
tzdata: remove 2015d version
meta/classes/kernel.bbclass | 10 +++++++---
meta/recipes-devtools/rpm/rpmresolve/rpmresolve.c | 10 ++++++----
meta/recipes-extended/tzdata/tzdata_2015d.bb | 6 ------
.../libpcre/{libpcre_8.36.bb => libpcre_8.38.bb} | 7 +++----
4 files changed, 16 insertions(+), 17 deletions(-)
delete mode 100644 meta/recipes-extended/tzdata/tzdata_2015d.bb
rename meta/recipes-support/libpcre/{libpcre_8.36.bb => libpcre_8.38.bb} (91%)
--
2.5.0
next reply other threads:[~2016-02-16 14:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-16 14:30 Joshua Lock [this message]
2016-02-18 11:04 ` [PATCH 0/4] Fido pull request Joshua G Lock
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.1455631402.git.joshua.g.lock@intel.com \
--to=joshua.g.lock@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox