[PATCH][meta-oe] php: uprev it to 5.5.24

[PATCH][meta-oe] php: uprev it to 5.5.24

[rongqing.li]

From: Roy Li <rongqing.li@windriver.com>

5.5.24 has lots of CVE fixes

Signed-off-by: Roy Li <rongqing.li@windriver.com>
---
 meta-oe/recipes-devtools/php/{php_5.5.21.bb => php_5.5.24.bb} | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)
 rename meta-oe/recipes-devtools/php/{php_5.5.21.bb => php_5.5.24.bb} (97%)

diff --git a/meta-oe/recipes-devtools/php/php_5.5.21.bb b/meta-oe/recipes-devtools/php/php_5.5.24.bb
similarity index 97%
rename from meta-oe/recipes-devtools/php/php_5.5.21.bb
rename to meta-oe/recipes-devtools/php/php_5.5.24.bb
index 4ad198a..76185fb 100644
--- a/meta-oe/recipes-devtools/php/php_5.5.21.bb
+++ b/meta-oe/recipes-devtools/php/php_5.5.24.bb
@@ -3,7 +3,7 @@ HOMEPAGE = "http://www.php.net"
 SECTION = "console/network"
 
 LICENSE = "PHP-3.0"
-LIC_FILES_CHKSUM = "file://LICENSE;md5=52dd90569008fee5bcdbb22d945b1108"
+LIC_FILES_CHKSUM = "file://LICENSE;md5=464ca70af214d2407f6b7d4458158afd"
 
 BBCLASSEXTEND = "native"
 DEPENDS = "zlib bzip2 libxml2 virtual/libiconv php-native lemon-native \
@@ -29,8 +29,8 @@ SRC_URI_append_class-target += " \
             file://70_mod_php5.conf \
           "
 
-SRC_URI[md5sum] = "8fe631ac52a3df9d6429faad81cf2562"
-SRC_URI[sha256sum] = "62e9429975c4ca5d7067a5052d5388fbf2ac8c51eeee581d59b04cc5a8da83fe"
+SRC_URI[md5sum] = "f9a8f3e4bb88b33b087bd63732b1402a"
+SRC_URI[sha256sum] = "801b5cf2e0c01b07314d4ac3c8a7c28d524bdd8263ebdd0e33a99008251316a2"
 
 S = "${WORKDIR}/php-${PV}"
 
-- 
2.1.0

Re: [PATCH][meta-oe] php: uprev it to 5.5.24

[Paul Eggleton]

Hi Roy,

On Thursday 23 April 2015 11:21:13 rongqing.li@windriver.com wrote:
> From: Roy Li <rongqing.li@windriver.com>
> 
> 5.5.24 has lots of CVE fixes

I know it's a bit of a pain, but could you please list all of the CVEs in the 
commit message? Hopefully it should just be a matter of copying them from the 
release notes for the releases since 5.5.21.

Also, I see you've changed LIC_FILES_CHKSUM, please add a note to the commit 
message explaining exactly what changed in the license text to cause this 
(even if it's just a copyright year change as it often is).

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre