Description of problem: Third-party (e.g. EPEL) and Fedora packaging requires a "virtual" provide for the PHP language version, independent of the specific php packages which are installed. We are using "php(language) = version" for this; this should be added to the php packages in Red Hat Enterprise Linux so third-party packagers can produce consistently packaged PHP libraries (and web applications) for Fedora and RHEL. Version-Release number of selected component (if applicable): php-5.3.3-14.el6_3 How reproducible: always Steps to Reproduce: 1. rpm -q --provides php-common | grep 'php(language)' Actual results: nada Expected results: 5.3.3
This request was not resolved in time for the current release. Red Hat invites you to ask your support representative to propose this request, if still desired, for consideration in the next release of Red Hat Enterprise Linux.
This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development. This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4.
Changes to be applied for EPEL packagers From rpmdiff output on php-common: added PROVIDES php(language) = 5.3.3 added PROVIDES php-core added PROVIDES php-ereg added PROVIDES php-filter added PROVIDES php-standard And, when php-devel installed $ rpm --eval %{php_version} 5.3.3
Sorry, I have miss one. added PROVIDES php-phar Virtual provides must be in sync with php -m output.
And php-xmlwriter could be added to the php-xml subpackage's provides too? That is needed for one of the horde 4 rpms you are working on (php-horde-kronolith) I made an emtpy package with those provides to get around the problem for now. PS - One other rpm that does not seem to be in epel by the way is php-pecl-http, required by php-horde-Horde-Http - I couldn't use the rpm from your repo as it was build against php-5.4. There is a version on rpmforge's repo though built against 5.3. Thanks Remi!
php-xmlwriter and php-xmlreader will be also add (see bug #874987)
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHSA-2013-0514.html