If these look ok I'll enable the runs this weekend:
http://mmcgrath.fedorapeople.org/epel5 http://mmcgrath.fedorapeople.org/epel4
-Mike
I maintain limph, and I could have sworn RHEL had php-mhash and php-mcrypt. Since these aren't EPEL packages ( and I see php-pear-crypt-chap needs them for epel5 as well), whom do I talk to about resolving this? I think they're build as part of the mail php SRPM, no?
If these look ok I'll enable the runs this weekend:
http://mmcgrath.fedorapeople.org/epel5 http://mmcgrath.fedorapeople.org/epel4
-Mike
epel-devel-list mailing list epel-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/epel-devel-list
On Jul 19, 2007, at 10:45 AM, Jon Ciesla wrote:
I maintain limph, and I could have sworn RHEL had php-mhash and php-mcrypt. Since these aren't EPEL packages ( and I see php-pear-crypt-chap needs them for epel5 as well), whom do I talk to about resolving this? I think they're build as part of the mail php SRPM, no?
I believe that in Fedora, these are part of the php-extras RPM. I think another issue is that those packages rely on mhash and mcrypt which AFAIK are not present in RHEL and have not yet been built for EPEL.
-Jeff
On Jul 19, 2007, at 10:45 AM, Jon Ciesla wrote:
I maintain limph, and I could have sworn RHEL had php-mhash and php-mcrypt. Since these aren't EPEL packages ( and I see php-pear-crypt-chap needs them for epel5 as well), whom do I talk to about resolving this? I think they're build as part of the mail php SRPM, no?
I believe that in Fedora, these are part of the php-extras RPM. I think another issue is that those packages rely on mhash and mcrypt which AFAIK are not present in RHEL and have not yet been built for EPEL.
Given that, what do I do? Have the EPEL4/5 builds of limph pulled, and note the cvs branches? And do more thorough deps checking for my next attempted EPEL build? :)
-Jeff
On Jul 19, 2007, at 11:49 AM, Jon Ciesla wrote:
Given that, what do I do? Have the EPEL4/5 builds of limph pulled, and note the cvs branches?
That's one option. Or you can become a co-maintainer for the needed packages in EPEL. See the wiki for more info on that if you're interested.
And do more thorough deps checking for my next attempted EPEL build? :)
Yes, and I believe we need to really emphasize this for people wanting to build packages for EPEL. At this point in time, it is not safe to assume that a package is in EPEL simply because it exists in Fedora/Extras.
-Jeff
s/mail/main/
If these look ok I'll enable the runs this weekend:
http://mmcgrath.fedorapeople.org/epel5 http://mmcgrath.fedorapeople.org/epel4
-Mike
epel-devel-list mailing list epel-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/epel-devel-list
epel-devel@lists.fedoraproject.org