![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
https://bugzilla.novell.com/show_bug.cgi?id=769155 https://bugzilla.novell.com/show_bug.cgi?id=769155#c0 Summary: sssd relies on a particular ldb version Classification: openSUSE Product: openSUSE 12.2 Version: Factory Platform: All OS/Version: Linux Status: NEW Severity: Major Priority: P5 - None Component: Samba AssignedTo: samba-maintainers@SuSE.de ReportedBy: jengelh@inai.de QAContact: samba-maintainers@SuSE.de CC: coolo@suse.com Found By: Beta-Customer Blocker: --- I noticed that the sssd deamon of sssd-1.8.3 exits shortly after start in a Factory install. The cause for this is that "sssd" was not rebuilt after the "ldb" package changed -- but this is a requirement; LDB modules must be run against the version they are compiled with. See https://fedorahosted.org/pipermail/sssd-devel/2012-June/010300.html for the mailing list thread I did upstream. rebuild=direct would be good, but alas, this would also work and properly link modules against the right LDB version. I propose to change the ldb package to have a SONAME bump at every release. Unfortunately, ldb uses the waf build system which I have no clue about. If it were autotools, I would use the -release flag libldb_la_LDFLAGS = -release ${PACKAGE_VERSION} which would cause the library to be named libldb-1.1.6.so.1. LDB modules (in /usr/lib64/ldb) are then linked against that rather than just libldb.so.1. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.