The IPA packages recently released are the ones which came out as 
security updates along with TUV's 6.2 release.  The current 6.2 BETA has 
those packages integrated.  So, to answer your question, SL 6.2 will 
ship by default with these IPA packages available and not any earlier 
versions.  Thus, in 6.2 you will not be able to have bind-dyndb-ldap and 
ipa-server installed due to their conflict.  I've no idea why they 
conflict as I'm unfamiliar with the specifics of the technology, but I 
trust upstream to get this right.

Pat

On 01/12/2012 12:55 PM, Natxo Asenjo wrote:
> hi,
>
> when trying to patch a sl 6.1 installation with ipa-server I get this error:
>
> Setting up Update Process
> Resolving Dependencies
> -->  Running transaction check
> --->  Package 389-ds-base.i686 0:1.2.8.2-1.el6 will be updated
> --->  Package 389-ds-base.i686 0:1.2.9.14-1.el6 will be an update
> --->  Package 389-ds-base-libs.i686 0:1.2.8.2-1.el6 will be updated
> --->  Package 389-ds-base-libs.i686 0:1.2.9.14-1.el6 will be an update
> --->  Package curl.i686 0:7.19.7-26.el6_1.1 will be updated
> --->  Package curl.i686 0:7.19.7-26.el6_1.2 will be an update
> --->  Package ipa-admintools.i686 0:2.0.0-23.el6 will be updated
> --->  Package ipa-admintools.i686 0:2.1.3-9.el6 will be an update
> --->  Package ipa-client.i686 0:2.0.0-23.el6 will be updated
> --->  Package ipa-client.i686 0:2.1.3-9.el6 will be an update
> --->  Package ipa-pki-ca-theme.noarch 0:9.0.3-6.el6 will be updated
> --->  Package ipa-pki-ca-theme.noarch 0:9.0.3-7.el6 will be an update
> --->  Package ipa-pki-common-theme.noarch 0:9.0.3-6.el6 will be updated
> --->  Package ipa-pki-common-theme.noarch 0:9.0.3-7.el6 will be an update
> --->  Package ipa-python.i686 0:2.0.0-23.el6 will be updated
> --->  Package ipa-python.i686 0:2.1.3-9.el6 will be an update
> -->  Processing Dependency: libipa_hbac-python for package:
> ipa-python-2.1.3-9.el6.i686
> --->  Package ipa-server.i686 0:2.0.0-23.el6 will be updated
> --->  Package ipa-server.i686 0:2.1.3-9.el6 will be an update
> --->  Package ipa-server-selinux.i686 0:2.0.0-23.el6 will be updated
> --->  Package ipa-server-selinux.i686 0:2.1.3-9.el6 will be an update
> --->  Package libcurl.i686 0:7.19.7-26.el6_1.1 will be updated
> --->  Package libcurl.i686 0:7.19.7-26.el6_1.2 will be an update
> --->  Package libxml2.i686 0:2.7.6-4.el6 will be updated
> --->  Package libxml2.i686 0:2.7.6-4.el6_2.1 will be an update
> --->  Package libxml2-python.i686 0:2.7.6-4.el6 will be updated
> --->  Package libxml2-python.i686 0:2.7.6-4.el6_2.1 will be an update
> --->  Package pki-ca.noarch 0:9.0.3-10.el6 will be updated
> --->  Package pki-ca.noarch 0:9.0.3-20.el6 will be an update
> --->  Package pki-common.noarch 0:9.0.3-10.el6 will be updated
> --->  Package pki-common.noarch 0:9.0.3-20.el6 will be an update
> --->  Package pki-java-tools.noarch 0:9.0.3-10.el6 will be updated
> --->  Package pki-java-tools.noarch 0:9.0.3-20.el6 will be an update
> --->  Package pki-native-tools.i686 0:9.0.3-10.el6 will be updated
> --->  Package pki-native-tools.i686 0:9.0.3-20.el6 will be an update
> --->  Package pki-selinux.noarch 0:9.0.3-10.el6 will be updated
> --->  Package pki-selinux.noarch 0:9.0.3-20.el6 will be an update
> --->  Package pki-setup.noarch 0:9.0.3-10.el6 will be updated
> --->  Package pki-setup.noarch 0:9.0.3-20.el6 will be an update
> --->  Package pki-silent.noarch 0:9.0.3-10.el6 will be updated
> --->  Package pki-silent.noarch 0:9.0.3-20.el6 will be an update
> --->  Package pki-symkey.i686 0:9.0.3-10.el6 will be updated
> --->  Package pki-symkey.i686 0:9.0.3-20.el6 will be an update
> --->  Package pki-util.noarch 0:9.0.3-10.el6 will be updated
> --->  Package pki-util.noarch 0:9.0.3-20.el6 will be an update
> --->  Package sssd.i686 0:1.5.1-34.el6 will be updated
> --->  Package sssd.i686 0:1.5.1-66.el6 will be an update
> -->  Processing Dependency: libipa_hbac = 1.5.1-66.el6 for package:
> sssd-1.5.1-66.el6.i686
> -->  Processing Dependency: libipa_hbac.so.0 for package: sssd-1.5.1-66.el6.i686
> -->  Processing Dependency: libunistring.so.0 for package: sssd-1.5.1-66.el6.i686
> --->  Package sssd-client.i686 0:1.5.1-34.el6 will be updated
> --->  Package sssd-client.i686 0:1.5.1-66.el6 will be an update
> --->  Package xmlrpc-c.i686 0:1.16.24-1200.1840.el6 will be updated
> --->  Package xmlrpc-c.i686 0:1.16.24-1200.1840.el6_1.4 will be an update
> --->  Package xmlrpc-c-client.i686 0:1.16.24-1200.1840.el6 will be updated
> --->  Package xmlrpc-c-client.i686 0:1.16.24-1200.1840.el6_1.4 will be an update
> -->  Running transaction check
> --->  Package libipa_hbac.i686 0:1.5.1-66.el6 will be installed
> --->  Package libipa_hbac-python.i686 0:1.5.1-66.el6 will be installed
> --->  Package libunistring.i686 0:0.9.3-4.el6 will be installed
> -->  Processing Conflict: ipa-server-2.1.3-9.el6.i686 conflicts
> bind-dyndb-ldap<  0.2.0-3
> -->  Finished Dependency Resolution
> Error: ipa-server conflicts with bind-dyndb-ldap
>   You could try using --skip-broken to work around the problem
>   You could try running: rpm -Va --nofiles --nodigest
>
> Now, I am aware that ipa in 6.1 is a technology preview and only from
> 6.2 will be production for TUV, so this is not a big deal because I
> will probably just reinstall the server once sl 6.2 is released. Is
> this 'problem' part of the upcoming 6.2 release?
> --
> Groeten,
> natxo


-- 
Pat Riehecky
Scientific Linux Developer