Discussion:
[users] php-mcrypt (from php-extras) mcrypt.ini file is incorrect
Richard Lloyd
2013-05-20 09:58:02 UTC
Permalink
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>
Leon Fauster
2013-05-20 12:42:34 UTC
Permalink
Post by Richard Lloyd
; Enable mcrypt extension module
extension=mcrypt.so
; 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?
Hi Richard,

Repoforge has nothing to do with EPEL - therefore such "incompatibilities" can exist. Repoforge
is considered as 3rd party repository. It is best practice to not mix 3rd party repos.

--
LF
Todd Lyons
2013-05-20 18:53:37 UTC
Permalink
On Mon, May 20, 2013 at 5:42 AM, Leon Fauster
Post by Leon Fauster
Post by Richard Lloyd
; Enable mcrypt extension module
extension=mcrypt.so
; Enable mcrypt extension module
extension=module.so
Repoforge has nothing to do with EPEL - therefore such "incompatibilities" can exist. Repoforge
is considered as 3rd party repository. It is best practice to not mix 3rd party repos.
He's not saying that RepoForge is the same as EPEL. He's saying that
the RepoForge mcrypt package puts the wrong configuration setting in
the mcrypt.ini file, whereas the EPEL version puts the correct
configuration setting. He's requesting that RepoForge mcrypt php
package be fixed to have the correct module name in the mcrypt.ini
file so that php can actually find the correct shared object when it
looks for it.

...Todd

--
The total budget at all receivers for solving senders' problems is $0.
If you want them to accept your mail and manage it the way you want,
send it the way the spec says to. --John Levine
Leon Fauster
2013-05-21 09:42:29 UTC
Permalink
Post by Todd Lyons
On Mon, May 20, 2013 at 5:42 AM, Leon Fauster
Post by Leon Fauster
Post by Richard Lloyd
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?
Repoforge has nothing to do with EPEL - therefore such "incompatibilities" can exist. Repoforge
is considered as 3rd party repository. It is best practice to not mix 3rd party repos.
He's not saying that RepoForge is the same as EPEL. He's saying that
the RepoForge mcrypt package puts the wrong configuration setting in
the mcrypt.ini file, whereas the EPEL version puts the correct
configuration setting. He's requesting that RepoForge mcrypt php
package be fixed to have the correct module name in the mcrypt.ini
file so that php can actually find the correct shared object when it
looks for it.
Hello Todd,

sure and valid - i did not want to smother Richard's request. My reply just
addresses the last phrase of Richards's request (see above) - thats all :-)

--
Best regards,

LF
Todd Lyons
2013-05-21 15:54:21 UTC
Permalink
Ok, sorry, that part was not clear to me. My apologies of that was
condescending.

...Todd

On Tue, May 21, 2013 at 2:42 AM, Leon Fauster
Post by Leon Fauster
Post by Todd Lyons
On Mon, May 20, 2013 at 5:42 AM, Leon Fauster
Post by Leon Fauster
Post by Richard Lloyd
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?
Repoforge has nothing to do with EPEL - therefore such "incompatibilities" can exist. Repoforge
is considered as 3rd party repository. It is best practice to not mix 3rd party repos.
He's not saying that RepoForge is the same as EPEL. He's saying that
the RepoForge mcrypt package puts the wrong configuration setting in
the mcrypt.ini file, whereas the EPEL version puts the correct
configuration setting. He's requesting that RepoForge mcrypt php
package be fixed to have the correct module name in the mcrypt.ini
file so that php can actually find the correct shared object when it
looks for it.
Hello Todd,
sure and valid - i did not want to smother Richard's request. My reply just
addresses the last phrase of Richards's request (see above) - thats all :-)
--
Best regards,
LF
_______________________________________________
users mailing list
users at lists.repoforge.org
http://lists.repoforge.org/mailman/listinfo/users
--
The total budget at all receivers for solving senders' problems is $0.
If you want them to accept your mail and manage it the way you want,
send it the way the spec says to. --John Levine
Jani Ollikainen
2013-05-26 19:16:22 UTC
Permalink
Hi,

It seems to be so hard problem to fix that 2 months has gone by and no
fix :)

https://github.com/repoforge/rpms/issues/254
Post by Richard Lloyd
The php-mcrypt 5.3.3-1 package (created from the php-extras src rpm)
from repoforge.org <http://repoforge.org> appears to have an incorrect
/etc/php.d/mcrypt.ini file. The equivalent package from Fedora EPEL
; 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.rpm
; 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
_______________________________________________
users mailing list
users at lists.repoforge.org
http://lists.repoforge.org/mailman/listinfo/users
Loading...