Arch Linux User Repository

Created binary repository on build.opensuse.org

https://build.opensuse.org/project/show/home:el:archphp

For Arch Linux, edit /etc/pacman.conf and add the following (note that the order of repositories in pacman.conf is important, since pacman always downloads the first found package):

[home_el_archphp_Arch]
Server = https://download.opensuse.org/repositories/home:/el:/archphp/Arch/$arch

Then run the following as root

key=$(curl -fsSL https://download.opensuse.org/repositories/home:el:archphp/Arch/$(uname -m)/home_el_archphp_Arch.key)
fingerprint=$(gpg --quiet --with-colons --import-options show-only --import --fingerprint <<< "${key}" | awk -F: '$1 == "fpr" { print $10 }')
pacman-key --init
pacman-key --add - <<< "${key}"
pacman-key --lsign-key "${fingerprint}"

Refresh packages database

pacman -Syy

Now search for php packages you need:

pacman -Ss php56

Install with pacman -S packages you need or all PHP 5.6 packages with:

sudo pacman -S $(pacman -Ssq | grep '^php56')

Read Carefully! Breaking changes in compare with native PHP package

Console version /usr/bin/php56 is installed with php56-cli subpackage, php56 doesn't include it anymore!!!

PEAR and PECL are available as php56-pear and php56-pecl subpackages

All shared modules are respresented as stand-alone subpackages and are not included with php56 package anymore.

No more extensions in php.ini itself!

Separate INI files for each extension are placed in /etc/php56/conf.d

They are loaded in correct order according to priority

PHP 5.6 will stop getting security updates in January 2019. Consider upgrading to PHP 7 now

PLEASE READ : For those who are getting "unknown public key" errors, this is NOT caused by this package. It means GPG is not configured to fetch public keys automatically (which is normal by default)

Please read the instructions at https://wiki.archlinux.org/index.php/Makepkg#Signature_checking

The easiest way to overcome this is to manually import the keys from a keyserver :

$ gpg --keyserver hkp://hkps.pool.sks-keyservers.net:80 --recv-keys C2BF0BC433CFC8B3 FE857D9A90D90EC1

foxxx and I have been working together and this package can now be installed along PHP 7 from the official repos. Everything has been moved into separate directories : Config : /etc/php56 Extensions : /usr/lib/php56/modules Binaries : /usr/bin/php56, /usr/bin/php56-cgi, /usr/bin/phar56, etc. If you were previously using this as a replacement for php7, you'll have to adjust the new configuration files in /etc/php56/ to reflect the current ones in /etc/php/. Apache module (provided by php56-apache) also has a specific configuration and CAN NOT cohabit with php7_module. Use php-fpm, fcgi or cgi if you need both versions. The apache module is installed as libphp56.so, so you should use the following lines your httpd.conf : # Load php 5.6 module LoadModule php5_module modules/libphp56.so # Use it for .php extensions Include conf/extra/php56_module.conf Please let me know if you encounter any problem or have a suggestion.

Need to add -DU_DEFINE_FALSE_AND_TRUE=1 to CPPFLAGS in PKGBUILD to compile.

CPPFLAGS+=' -DU_USING_ICU_NAMESPACE=1 -DU_DEFINE_FALSE_AND_TRUE=1'

Also when using php56-fpm, comment out or change the open_basedir= in php.ini, otherwise keep getting 404 for no reason.

PHP 5.6 will stop working with MariaDB 10.5.7 due to a bug in the php-mysqlnd extension and stricter checking on the MariaDB side. This stricter checking was first introduced in MariaDB 10.2/3 https://jira.mariadb.org/browse/MDEV-24121 and reverted for a later major version (it broke a portion of the internet).

PHP 7.3 has this fixed, basically a byte is sent to the connected database server to say expect some parameters when preparing this query, then for a query without parameters e.g "SELECT * FROM groups" none are sent causing the stricter checking to throw the following error:

Error: SQLSTATE[HY000]: General error: 1835 Malformed communication packet

To fix i would suggest a PKGBUILD patch to the mysqlnd extension code:

https://github.com/centminmod/centminmod/blob/123.09beta01/patches/php/php5640-mysqlnd-fix.patch

Patches for the aur build: https://gist.github.com/Caffe1neAdd1ct/4a9004327390140bf10e3af2f277077f

Fully understand nobody should be on PHP 5.6 but if you are and need to keep using it alongside nice up-to-date versions of everything else this should help.

I'm running into the exact same error as danny below.

Comment date 2019-03-21, me too bug, php not work

=====================================================================

Number of tests : 777 704

Tests skipped : 73 ( 9.4%) --------

Tests warned : 0 ( 0.0%) ( 0.0%)

Tests failed : 1 ( 0.1%) ( 0.1%)

Expected fail : 1 ( 0.1%) ( 0.1%)

Tests passed : 702 ( 90.3%) ( 99.7%)

---

Time taken : 21 seconds

=====================================================================

=====================================================================

EXPECTED FAILED TEST SUMMARY

Test open_basedir configuration [tests/security/open_basedir_linkinfo.phpt] XFAIL REASON: BUG: open_basedir cannot delete symlink to prohibited file. See also bugs 48111 and 52176. =====================================================================

=====================================================================

FAILED TEST SUMMARY

php://input is empty when enable_post_data_reading=Off [tests/basic/bug67198.phpt]

===================================================================== ==> ERROR: A failure occurred in check(). Aborting... Error making: php56

test failed. BUG ?

@mickael9 does not support freetype?

updated to 5.6.40:

The PHP development team announces the immediate availability of PHP 5.6.40. This is a security release. Several security bugs have been fixed in this release. All PHP 5.6 users are encouraged to upgrade to this version.

Please note that according to the PHP version support timelines, PHP 5.6.40 is the last scheduled release of PHP 5.6 branch. There may be additional release if we discover important security issues that warrant it, otherwise this release will be the final one in the PHP 5.6 branch. If your PHP installation is based on PHP 5.6, it may be a good time to start making the plans for the upgrade to PHP 7.1, PHP 7.2 or PHP 7.3.

updated to 5.6.39:

The PHP development team announces the immediate availability of PHP 5.6.39. This is a security release. Several security bugs have been fixed in this release. All PHP 5.6 users are encouraged to upgrade to this version.

This will be the last update for PHP 5.6, thus any potentially existing security vulnerabilities will not be fixed in the future.

Consider upgrading to PHP 7 now.

We will work on moving to 7, but currently 5.6 is still critical as there are still some groupware and server packages that have not been fully ported to 7. Thanks for keeping php56 updated.

PHP 5.6 will stop getting security updates in January 2019. Consider upgrading to PHP 7 now