01.11.2022 10:59, Michael Tokarev wrote:
..
And this revealed one more issue here, now with samba 4.17. Where, the
same libndr.so again, has changed soname from libndr.so.2 to libndr.so.3!
And it looks like *this* is what you're talking about now, once 4.17 with
this new libndr.so.3 hits unstable.
*Sigh*.
So now, samba-libs breaks not only bullseye sssd-ad, but also *bookworm*
sssd-ad!
So:
samba-libs 4.13: libndr.so.1
samba-libs 4.15: libndr.so.2
samba-libs 4.17: libndr.so.3
and this is what we're facing now, 4.16=>4.17 update breaks things again.
and this new breakage went unnoticed, and I knew nothing about the soname
change before this very moment.
Andrew, can you share some info about the new 2=>3 soname bumb in 4.17?
I wonder if we should provide old libndr.so.1 and libndr.so.2 interface
in samba-libs forever... this shouldn't be that difficult.
This has come in 7b9f87b877bd385e8cec893cd282d4b3fc00206d:
Author: Pavel Filipenský <pfili...@redhat.com>
Date: Wed Jun 22 11:13:34 2022 +0200
librpc:ndr: Update ndr_print_debug() and add macro NDR_PRINT_DEBUG_LEVEL
Bumping the ABI to 3.0.0
This is enhancement of NDR_PRINT_DEBUG macro with following new features:
* debug level can be specified (NDR_PRINT_DEBUG always uses level 1)
* the trace header shows the location and function of the caller
instead of function 'ndr_print_debug', which is not really useful.
Signed-off-by: Pavel Filipenský <pfili...@redhat.com>
Reviewed-by: Andreas Schneider <a...@samba.org>
Is it not possible to keep the soname after this change?
I'm reviewing the changes now..
/mjt
