mod_wsgi

[Josh Kayse]

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.

Let me know if you have any questions and I appreciate any feedback.

Thanks,
-josh

[1] https://bugzilla.redhat.com/show_bug.cgi?id=524120

--
A: No.
Q: Should I include quotations after my reply?

Don't top post: see http://www.caliburn.nl/topposting.html for more.

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. I am seeking guidance on whether I should include a Conflicts line in the spec file. Additionally, the newest version of mod_wsgi (3.1) does not conflict with the newest version of mod_python (3.3.1). Should I update mod_wsgi to 3.1 with the hopes that Red Hat releases a newer version of mod_python for EL5?

smime.p7s
Description: S/MIME Cryptographic Signature

_______________________________________________
epel-devel-list mailing list
epel-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/epel-devel-list