I have nextcloud running alongside with web service in need of php56. Until recently, I managed this with two parallel php installations (plain php from pacman and php56 via AUR). Now, nextcloud needs php71, while the main version alrady went up to 7.2. Apparently, a php71 package was created to deal with this requirement. However, it breaks parallel installation with php56:
pacman -Suy :: Synchronizing package databases... core is up to date extra is up to date community is up to date multilib is up to date repo-ck is up to date :: Starting full system upgrade... resolving dependencies... looking for conflicting packages... warning: removing 'php' from target list because it conflicts with 'php71' warning: removing 'php-gd' from target list because it conflicts with 'php71-gd' :: php71 and php are in conflict. Remove php? [y/N] y :: php71 and php56 are in conflict (php). Remove php56? [y/N] y :: php71-gd and php-gd are in conflict. Remove php-gd? [y/N] y :: php71-gd and php56-gd are in conflict (php-gd). Remove php56-gd? [y/N] y error: failed to prepare transaction (could not satisfy dependencies) :: php56-apache: removing php56 breaks dependency 'php56' :: php56-cgi: removing php56 breaks dependency 'php56' :: php56-dblib: removing php56 breaks dependency 'php56' :: php56-embed: removing php56 breaks dependency 'php56' :: php56-enchant: removing php56 breaks dependency 'php56' :: php56-fpm: removing php56 breaks dependency 'php56' :: php56-imap: removing php56 breaks dependency 'php56' :: php56-intl: removing php56 breaks dependency 'php56' :: php56-ldap: removing php56 breaks dependency 'php56' :: php56-mcrypt: removing php56 breaks dependency 'php56' :: php56-mssql: removing php56 breaks dependency 'php56' :: php56-odbc: removing php56 breaks dependency 'php56' :: php56-pear: removing php56 breaks dependency 'php56' :: php56-pgsql: removing php56 breaks dependency 'php56' :: php56-phpdbg: removing php56 breaks dependency 'php56' :: php56-pspell: removing php56 breaks dependency 'php56' :: php56-snmp: removing php56 breaks dependency 'php56' :: php56-sqlite: removing php56 breaks dependency 'php56' :: php56-tidy: removing php56 breaks dependency 'php56' :: php56-xsl: removing php56 breaks dependency 'php56'
Additional info: package version(s) config and/or log files etc.
Maybe you are already aware of this. For now, this is a showstopper for me. I have to wait for nextcloud 13. Before release, I will not be able to update the system anymore... :/
Pinned Comments
el_aur commented on 2023-03-01 21:07 (UTC)
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):
Then run the following as root
Refresh packages database
Now search for php packages you need:
Install with
pacman -S
packages you need or all PHP 5.6 packages with:el_aur commented on 2023-02-22 16:02 (UTC)
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
mickael9 commented on 2018-10-03 17:21 (UTC)
PHP 5.6 will stop getting security updates in January 2019. Consider upgrading to PHP 7 now
mickael9 commented on 2016-04-06 11:51 (UTC) (edited on 2018-10-03 17:18 (UTC) by mickael9)
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 :
mickael9 commented on 2016-01-14 01:53 (UTC) (edited on 2016-08-06 17:00 (UTC) by mickael9)