Add Conflicts on mod_ssl because it interferes with mod_proxy and dogtag

We had this in v1 but removed it with v2 because we no longer used
TurboGears for the UI. Because we are now proxying requests to dogtag
we need to re-add this so that mod_ssl doesn't interfere with our
communication.

mod_ssl always blindly registers itself as the SSL provider for mod_proxy.
mod_nss will only register itself if mod_ssl hasn't already done so.

https://fedorahosted.org/freeipa/ticket/2177

freeipa.spec.in

@@ -153,6 +153,10 @@ Requires(postun): python initscripts chkconfig
 Conflicts: bind-dyndb-ldap < 1.0.0-0.1.b1
 Conflicts: bind < 9.8.1-1
 
+# mod_proxy provides a single API to communicate over SSL. If mod_ssl
+# is even loaded into Apache then it grabs this interface.
+Conflicts: mod_ssl
+
 Obsoletes: ipa-server >= 1.0
 
 %description server
@@ -668,6 +672,9 @@ fi
 %ghost %attr(0644,root,apache) %config(noreplace) %{_sysconfdir}/ipa/ca.crt
 
 %changelog
+* Thu Feb 23 2012 Rob Crittenden <rcritten@redhat.com> - 2.99.0-17
+- Add Conflicts on mod_ssl
+
 * Thu Feb 16 2012 Rob Crittenden <rcritten@redhat.com> - 2.99.0-16
 - Set min for 389-ds-base to 1.2.10.1-1 to fix install segfault,
   schema replication.