Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Armin Kuster <akuster808@gmail.com>
To: akuster@mvista.com, openembedded-devel@lists.openembedded.org
Subject: [PATCH 00/12] Jethro-next pull request
Date: Sun, 18 Sep 2016 15:56:13 -0700	[thread overview]
Message-ID: <cover.1474239076.git.akuster808@gmail.com> (raw)

Please consider these changes for meta-openembedded jethro

The ntp, php and wireshark updates are bug and security fixes. No new features added

The following changes since commit 8ab04afbffb4bc5184cfe0655049de6f44269990:

  python-cryptography: fix compile issue with openssl 1.0.2h (2016-05-31 19:01:26 +0200)

are available in the git repository at:

  git://git.openembedded.org/meta-openembedded-contrib akuster/jethro-next
  http://cgit.openembedded.org/cgit.cgi//log/?h=akuster/jethro-next

Andre McCurdy (1):
  ntp: avoid floating dependency on mdns (aka mDNSResponder)

Armin Kuster (2):
  php: update to 5.6.18 and 6.6.32
  wireshark: update package to 1.12.13 for security fixes.

Derek Straka (2):
  php: check for existance of directory before 'rmdir' in
    do_install_append_class-target
  php: update to 5.6.17 and 5.5.31

Jackie Huang (3):
  php: update to 5.5.37 and 5.6.23
  php: control ipv6 support based on DISTRO_FEATURES
  php: update to 5.5.38 and 5.6.25

Robert Yang (1):
  php: fix aclocal-copy aclocal-copy

fan.xin (3):
  php: Upgrade 5.5.26 -> 5.5.30
  php: Upgrade 5.6.12 -> 5.6.16
  ntp: Security fixes via Upgrade to 4.2.8p8

 .../ntp/{ntp_4.2.8p7.bb => ntp_4.2.8p8.bb}         |  5 +-
 .../{wireshark_1.12.8.bb => wireshark_1.12.13.bb}  | 10 +--
 .../php/php-5.6.12/CVE-2015-7803.patch             | 85 ----------------------
 .../php/php-5.6.12/CVE-2015-7804.patch             | 64 ----------------
 .../php/php-5.6.12/CVE-2016-1903.patch             | 55 --------------
 .../change-AC_TRY_RUN-to-AC_TRY_LINK.patch         |  0
 meta-oe/recipes-devtools/php/php.inc               | 14 ++--
 meta-oe/recipes-devtools/php/php_5.5.26.bb         |  4 -
 meta-oe/recipes-devtools/php/php_5.5.38.bb         |  6 ++
 meta-oe/recipes-devtools/php/php_5.6.12.bb         |  9 ---
 meta-oe/recipes-devtools/php/php_5.6.25.bb         |  7 ++
 11 files changed, 29 insertions(+), 230 deletions(-)
 rename meta-networking/recipes-support/ntp/{ntp_4.2.8p7.bb => ntp_4.2.8p8.bb} (96%)
 rename meta-networking/recipes-support/wireshark/{wireshark_1.12.8.bb => wireshark_1.12.13.bb} (89%)
 delete mode 100644 meta-oe/recipes-devtools/php/php-5.6.12/CVE-2015-7803.patch
 delete mode 100644 meta-oe/recipes-devtools/php/php-5.6.12/CVE-2015-7804.patch
 delete mode 100644 meta-oe/recipes-devtools/php/php-5.6.12/CVE-2016-1903.patch
 rename meta-oe/recipes-devtools/php/{php-5.6.12 => php-5.6.25}/change-AC_TRY_RUN-to-AC_TRY_LINK.patch (100%)
 delete mode 100644 meta-oe/recipes-devtools/php/php_5.5.26.bb
 create mode 100644 meta-oe/recipes-devtools/php/php_5.5.38.bb
 delete mode 100644 meta-oe/recipes-devtools/php/php_5.6.12.bb
 create mode 100644 meta-oe/recipes-devtools/php/php_5.6.25.bb

-- 
2.7.4



                 reply	other threads:[~2016-09-18 22:56 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.1474239076.git.akuster808@gmail.com \
    --to=akuster808@gmail.com \
    --cc=akuster@mvista.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