On Mon, 2022-06-20 at 10:39 +0200, Hannes Eberhardt wrote: > Package: samba-libs > Version: 2:4.16.1+dfsg-8~bpo11+1 > Severity: normal > X-Debbugs-Cc: hannes.eberha...@neumannmueller.com > > Dear Maintainer, > > I noticed that sssd service of a freeipa-client installation broke > with the following error message because of missing library. > sssd[651553]: /usr/libexec/sssd/sssd_pac: error while loading shared > libraries: libndr.so.1: cannot open shared object file: No such file > or directory > > I previously reported the issue on the backports mailing list. This > is the thread: > https://lists.debian.org/debian-backports/2022/06/msg00012.html > > I was asked to file a bug report against the samba-libs package as > the root cause seems to be here. Please find the corresponding reply > here: https://lists.debian.org/debian-backports/2022/06/msg00015.html
I don't claim to understand debian policy but I think that freeIPA should, just as sssd should, expect to need to rebuild after any Samba version upgrade. (And therefore Samba backports may not be possible, and this may be why Samba is often installed in a custom prefix by 3rd party packagers). I changed the libndr.so version upstream in Samba 4.15 to properly address regressions from earlier fixes in that library. Almost all users of the library will have been impacted by the changed function signatures, no fallbacks are/were possible. Upstream Samba doesn't have the resources to provide a stable ABI to libndr, but the output of PIDL (eg compile-time API) should still work. Andrew Bartlett -- Andrew Bartlett (he/him) https://samba.org/~abartlet/ Samba Team Member (since 2001) https://samba.org Samba Team Lead, Catalyst IT https://catalyst.net.nz/services/samba Samba Development and Support, Catalyst IT - Expert Open Source Solutions
