I am sorry for replying to these accidentally in the LIFO order... > Are you talking about: > libipa-hbac-dev > libsss-sudo-dev > libsss-sudo0 > python-libipa-hbac > libipa-hbac0 > sssd-tools > libnss-sss > libpam-sss > python-sss > sssd
I do not think all of these are necessary, but it may be for some use cases. For my use case (auth and nss from kerberos, ldap and local files), just the following are needed: libnss-sss libpam-sss python-sss sssd The various *ipa-* packages probably relate to using RedHat's freeIPA (http://www.freeipa.org/page/Main_Page). I have no idea what sssd-tools contains and I do not know about the sudo-related packages either: sudo and sssd work fine without them. Of course, the various other dependencies and build-deps are required, too. > Can you confirm that all the binary packages necessary to install sssd > from Ubuntu onto standard Debian unstable are in the first list above? The dependencies I mentioned earlier (though possibly not before you wrote the email I am replying to) are: libcollection libdhash libpath-utils libref-array libini-config The last two are actually dependencies of the first three, not direct dependencies of sssd, but necessary anyway. An additional twist is this: https://bugzilla.redhat.com/show_bug.cgi?id=771484 In other words, sssd, even the Ubuntu versions, on Debian/sid *IS* *BROKEN* because of changes in libldap-2.4. The upstream libldap seems to fix this, likewise downgrading to 2.4.25-4, but at the moment, we would have sssd name lookups from ldap broken no matter what. Nice, isn't it? > could be removed without causing problems elsewhere.) Someone who cares > about sssd has to do the work. Like I said earlier, given suitable mentoring, I would be willing to take this up. Volunteers? Petter? =) Cheers, Juha -- ----------------------------------------------- | Juha Jäykkä, ju...@iki.fi | | http://www.maths.leeds.ac.uk/~juhaj | -----------------------------------------------
signature.asc
Description: This is a digitally signed message part.
