Posted by & filed under PHP.

On January 22nd 2015, the PHP group released PHP 5.5.21.

This release fixes several bugs as well as CVE-2015-0231, CVE-2014-9427 and CVE-2015-0232. All PHP 5.5 users are encouraged to upgrade to this version.

PHP 5.5.21 packages are now available on Dotdeb for Debian 7.7 “Wheezy”, on both amd64 and i386 architectures.

The following modules have been packaged too :

  • apcu 4.0.7
  • gearman 0.8.3
  • geoip 1.0.8
  • imagick 3.1.2
  • memcache 3.0.8
  • memcached 2.2.0
  • mongo 1.6.0
  • pecl_http 1.7.6
  • pinba (master)
  • redis 2.2.5
  • spplus 1.1
  • ssh2 0.12
  • xcache 3.2.0
  • xdebug 2.2.7
  • xhprof 0.9.4

Please read the Changelog and the migration guide (be aware of the backward incompatible changes) before upgrading.

3 Responses to “PHP 5.5.21 for Wheezy”

  1. Ed

    Hi,

    Thanks for your excellent work. COuld you please comment on hhvm.com? I work mostly with drupal 7 and soon 8, and the BOA hosting / optimization platform that uses php5-fpm and mariadb 10.x (soon their cluster), and they have recently introduced hhvm. I know it is a php interpreter/compiler that has major memory and cpu improvements. I think I understand that hhvm is used INSTEAD OF php-fpm, and not in addition to it. Could you please comment on this hhvm and let us know if you think that is the way forward for optimal performance and value for websites and web apps that need to use php5? Thank you for your response.

  2. Guillaume Plessis

    Hi,

    HHVM is a good initiative and it has the benefit to make the PHP Group think about lots of improvements and features for PHP 7 🙂

    I haven’t taken a look at HHVM recently, but what I saw in the past is that you had to make some deep modifications to your code to your code before making it work with HHVM. Given the upcoming changes in PHP, I’m not sure if it worths it.

    Maybe you can get feedbacks from the Drupal community as well. You have so many other rooms for improvement around Drupal (objects caching with Memcached/Redis, search via Solr/ElasticSearch, HTTP caching, ESI and prefetching with Varnish…), I’m not sure about the priority of changing the PHP Engine.