On 27/10/16 09:28, Alexander Bokovoy wrote:
# rpm -q --requires freeipa-server|grep ^lib|xargs -n1 rpm
-q --whatprovides|sort -u
glibc-2.23.1-10.fc24.x86_64
krb5-libs-1.14.4-4.fc24.x86_64
libcom_err-1.42.13-4.fc24.x86_64
libgcc-6.2.1-2.fc24.x86_64
libsss_nss_idmap-1.14.2-1.fc24.x86_64
libtalloc-2.1.6-1.fc24.x86_64
libtevent-0.9.28-1.fc24.x86_64
libunistring-0.9.4-3.fc24.x86_64
libuuid-2.28.2-1.fc24.x86_64
libverto-0.2.6-6.fc24.x86_64
nspr-4.13.1-1.fc24.x86_64
nss-3.27.0-1.1.fc24.x86_64
nss-util-3.27.0-1.0.fc24.x86_64
openldap-2.4.44-1.fc24.x86_64
openssl-libs-1.0.2j-1.fc24.x86_64
samba-client-libs-4.4.6-1.fc24.x86_64
You cannot remove samba-client-libs due to this.
We also do not support downgrading Samba.
ough, this is not good this Siamese-twins type of existence.
AD easy integration is very nice thing to have but
admins/users should also be able to equally easy disintegrate.
It to me goes way too weird - sssd won't exist (according to
rpm deps logic) without sssd-ad and then IPA follows.
We should have IPA which does not depend on Samba.
I myself am in a sticky wicket situation right now - my BDC
Samba 4.2.x on Centos 7 is not happy with userdb
multi-master ldap backend, PDC which is Centos 6.8 with
3.6.23-36.el6_8 has ruled that little domain fine for many
years and win clients, etc are a OK. But Samba 4.2.x fails.
I believe it might be a bug - I have even submitted a
report: https://bugzilla.redhat.com/show_bug.cgi?id=1388589
- but I'm stuck!! I cannot try (at least not in orderly
manner) any Samba 3 version which I believe would be quick &
nice fix to my problem.
I'm stuck between these Siamese twins.
hmm...kupa.
L.
--
Manage your subscription for the Freeipa-users mailing list:
https://www.redhat.com/mailman/listinfo/freeipa-users
Go to http://freeipa.org for more info on the project
