sys-auth/sssd-1.9.3 has a direct dependency on app-crypt/mit-krb5 and net-fs/samba-4.0.0 Samba-4.0.0 depends on app-crypt/heimdal. app-crypt/mit-krb5 and app-crypt/heimdal are mutualy exclusive. With the current set of dependencies sssd can not be emerged. Please remove the samba dependency so it can be emerged again. Reproducible: Always
(In reply to comment #0) > sys-auth/sssd-1.9.3 has a direct dependency on app-crypt/mit-krb5 and > net-fs/samba-4.0.0 > pinkbyte@phantom ~ $ grep -ir samba /usr/portage/sys-auth/sssd/*.ebuild /usr/portage/sys-auth/sssd/sssd-1.9.2.ebuild:#--enable-pac-responder required samba-4 /usr/portage/sys-auth/sssd/sssd-1.9.3.ebuild:#--enable-pac-responder required samba-4 The only one mention of samba is a comment, so this is definitely NOT a direct dependency
Sorry, forget my previous sentence, sssd-1.9.3 NOW has a direct dependency on samba.
(In reply to comment #0) > sys-auth/sssd-1.9.3 has a direct dependency on app-crypt/mit-krb5 and > net-fs/samba-4.0.0 > > Samba-4.0.0 depends on app-crypt/heimdal. > > app-crypt/mit-krb5 and app-crypt/heimdal are mutualy exclusive. > > With the current set of dependencies sssd can not be emerged. > > Please remove the samba dependency so it can be emerged again. > > > Reproducible: Always 1.9.3 is hardmasked in profile now; also, odd release series is development, I'm not plan to stabilize it; on the contrary, even have LTS releases
This version removed from tree. I want to wait samba-4 unmasked