Richard Lloyd
2013-05-20 09:58:02 UTC
The php-mcrypt 5.3.3-1 package (created from the php-extras src rpm) from
repoforge.org appears to have an incorrect /etc/php.d/mcrypt.ini file. The
equivalent package from Fedora EPEL (yes, it's also available there!) says:
; Enable mcrypt extension module
extension=mcrypt.so
But the repoforge version at
http://apt.sw.be/redhat/el6/en/x86_64/dag/RPMS/php-mcrypt-5.3.3-1.el6.rf.x86_64.rpmincorrectly
says:
; Enable mcrypt extension module
extension=module.so
There aren't that many PHP packages that use mcrypt - phpMyAdmin and
TeamPass are probably two of the more well known ones (unfortunately, we
use both...). It's not clear to me why Repoforge has exactly the same RPM
version as Fedora EPEL either - is it normal policy to allow such
redundancy?
Richard Lloyd
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.repoforge.org/pipermail/users/attachments/20130520/12aeb7f5/attachment.html>
repoforge.org appears to have an incorrect /etc/php.d/mcrypt.ini file. The
equivalent package from Fedora EPEL (yes, it's also available there!) says:
; Enable mcrypt extension module
extension=mcrypt.so
But the repoforge version at
http://apt.sw.be/redhat/el6/en/x86_64/dag/RPMS/php-mcrypt-5.3.3-1.el6.rf.x86_64.rpmincorrectly
says:
; Enable mcrypt extension module
extension=module.so
There aren't that many PHP packages that use mcrypt - phpMyAdmin and
TeamPass are probably two of the more well known ones (unfortunately, we
use both...). It's not clear to me why Repoforge has exactly the same RPM
version as Fedora EPEL either - is it normal policy to allow such
redundancy?
Richard Lloyd
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.repoforge.org/pipermail/users/attachments/20130520/12aeb7f5/attachment.html>