[Pkg-samba-maint] Bug#1022826: samba-common-bin: testparm fails if given a config file, due to libpopt 1.19+dfsg-1

[Michael Tokarev]

Control: found -1 2:4.16.6+dfsg-3
Control: tag -1 - moreinfo unreproducible
Control: tag -1 + confirmed


26.10.2022 18:34, Arnaud Rebillout wrote:
..
> So this is version 2:4.16.6+dfsg-3. Right now I can fire a Debian sid container and reproduce the issue with:

Ok, that's excllent, thank you!

>    # apt update && apt install -y smbclient
>    # testparm /etc/samba/smb.conf --suppress-prompt
>    Load smb config files from gW???U
>    Error loading services.
> 
> NB: you MUST pass /etc/samba/smb.conf in argument to trigger the issue.

Aha. Got it.

> The issue with libpopt seems to be documented at https://github.com/rpm-software-management/popt/issues/80.

Lemme see..

> However I didn't notice that samba embeds its own libpopt, so now I'm confused. Are you 100% sure it's the embedded lib that is used?

I'm 100% sure it is *not* the embedded copy which is used, due to this:
https://salsa.debian.org/samba-team/samba/-/blob/debian/2%254.16.6+dfsg-3/debian/rules#L85

  --bundled-libraries=NONE,pytevent,ldb

>    # ldd /usr/bin/testparm | grep popt
>    libpopt.so.0 => /lib/x86_64-linux-gnu/libpopt.so.0 (0x00007f52a45d1000)
> 
> Or does the line above suggests that it uses the shared library? (real question, I'm not familiar with ldd)

It uses the system shared lib, exeactly as it should.

Samba had adoptations for the libpopt changes and changed internal popt
too, that's why I was confused as well.

Anyway, lemme look at this now when I know the version
and the environment, and was able to reproduce it.

Thanks,

/mjt