Problem with "samba-tool"

[MJ]

On 12/09/2019 9:41 pm, Carmel NY wrote:
> On Thu, 12 Sep 2019 08:45:32 +1000, MJ stated:
>> On 11/09/2019 10:19 pm, Andrea Venturoli wrote:
>>> On 2019-09-11 13:17, Carmel NY wrote:
>>>> FreeBSD 12.0-RELEASE-p10
>>>> samba version 4.8.12
>>>>
>>>> When attempting to use the 'samba-tool', I always receive this error
>>>> message:
>>>>
>>>> samba-tool
>>>> Traceback (most recent call last):
>>>>     File "/usr/local/bin/samba-tool", line 33, in <module>
>>>>       from samba.netcmd.main import cmd_sambatool
>>>>     File "/usr/local/lib/python2.7/site-packages/samba/__init__.py",
>>>> line 28, in <module> import ldb
>>>> ImportError: /usr/local/lib/python2.7/site-packages/ldb.so:
>>>> Undefined symbol "ldb_handler_copy"
>>>>
>>>> It doesn't make any difference what command options I use. Before I
>>>> ask on a dedicated 'samba support forum', I thought I would first
>>>> try and see if this was a localized FreeBSD problem.
>>>>   
>>>
>>> You are in good company.
>>> See:
>>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239480
>>
>> LOL dependency hell. Free software is great but when you pull in so
>> many libraries to build it, stuff like this does happen.
> 
> I don't remember seeing any notice that 'samba-tool' was not functional
> in the port description or any notice in the UPDATING file. If there
> was, and I missed it, then I do apologize. That brings me to my next
> point, why wasn't such a notice given? I see that I am not the only
> person to have wasted time on this.
> 
> The hard work that port maintainer's do for FreeBSD is certainly
> appreciated. However, they also have an obligation to at least give
> their product a "test drive" first before releasing it, and noting any
> know problems.
> 
> According to the samba site: Tuesday, September 17 2019 - Planned
> release date for Samba 4.11.0. Hopefully, this can be modified to work
> with FreeBSD in its entirety.
> 

I totally see your point, but in this case the regression seems to have crept in.

I'm not sure on the specifics but as per comment #8 in the bug, this is just an example of dependency hell.

As I said, if you want a timeline on the fix, ask Timur.

Cheers,
Mark