Hi,

  In a bookworm environment, I need to use a MIT-kerberos version of samba.
It means using the version in testing/unstable or using the backported
samba packages. Of course, I tried to use the backported version
(2:4.21.1+dfsg-2~bpo12+1).
  But, when trying to install it, apt tells me that (in backports)
samba-libs : Breaks: sssd-ad (< 2.9.4-1+b1)
and, of course, I need sssd-ad.

  So, I tried to backport sssd itself locally. It works easily
(I just needed to revert the 64-bit time_t patch).

  Then, I installed my local backport of sssd with the official
backport of samba. Packages installed with no problem. However,
sssd refused to restart. Looking into the logs, I found:
   *  (2024-11-07 16:57:22): [be[DOMAIN]] [dp_module_open_lib] (0x1000): Loading module [ad] with path [/usr/lib/x86_64-linux-gnu/sssd/libsss_ad.so]
   *  (2024-11-07 16:57:22): [be[DOMAIN]] [dp_module_open_lib] (0x0010): Unable to load module [ad] with path [/usr/lib/x86_64-linux-gnu/sssd/libsss_ad.so]: libndr.so.3: cannot open shared object file: No such file or directory

  I discovered that the libndr.so.3 is in the bookworm samba-libs package,
whereas the bookworm-backports samba-libs package contains libndr.so.5

  So, I rebuilt my local sssd backport forcing the use of the
backported samba (in particular the libsmbclient-dev build dependency).
And it works.


  My point is just to signal that dh_shlibs does not correctly
capture the dependency between sssd-ad and samba-libs.
I do not look for the root reason (sssd-ad is using plugins
instead for plain shared libs?, ...)

  Regards,
    Vincent