On Mon, Mar 08, 2010 at 12:48:00PM -0600, BJ Dierkes wrote: > > > On Mar 8, 2010, at 12:20 PM, Josh Kayse wrote: > > > I have recently acquired mod_wsgi commit permissions and am going through > > some of the open bugs for it on bugzilla. According to [1], and from my > > testing, mod_wsgi and mod_python conflict resulting in apache segfaulting. > > The policy currently states that no packages in EPEL may conflict with a > > package from Red Hat Base. Technically, mod_wsgi and mod_python conflict > > with each other, but mod_python is optional. > > > > I don't think that mod_wsgi should be pulled from EPEL because it is > > already built for RHEL5 and it is usable as long as mod_python is disabled > > in apache. > > > > [1] https://bugzilla.redhat.com/show_bug.cgi?id=524120 > > I agree, and think there might be room in the policy for edge cases like > this. I'd like to see something added to the policy that would cover this > situation, being that mod_python is optional. > I'm not sure what such a policy would look like but +1 to something along this line.
-Toshio
pgp42lwCS9bmy.pgp
Description: PGP signature
_______________________________________________ epel-devel-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/epel-devel-list
