Bug 8320 - SLES11 x86_64 3.5.9-44 packages not working
SLES11 x86_64 3.5.9-44 packages not working
Product: BuildFarm
Classification: Unclassified
Component: scripts
x64 Linux
: P5 major
: ---
Assigned To: Björn Jacke
Samba QA Contact
Depends on:
  Show dependency treegraph
Reported: 2011-07-26 13:44 UTC by catWorkX
Modified: 2011-08-15 06:29 UTC (History)
0 users

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description catWorkX 2011-07-26 13:44:50 UTC
Dear Sernet team.

the pakages provided under


which imho similar to 


are not working on a fresh SLES11 SP0 with latest patches.

The nmbd can not start because of an libtalloc-Error.

Starting SAMBA nmbd :/usr/sbin/nmbd: symbol lookup error: /usr/sbin/nmbd: undefined symbol: _talloc_free
startproc:  exit status of parent of /usr/sbin/nmbd: 127

Please try for yourself.

After removing every default SLES11 samba package an the all packages it depends on, we were able to compile your 3.5.9-44 source code, which has the talloc call statically included (i think).
Earlier compile tries with installed libtalloc1 package led to samba packages with the same error.
The self compiled packages are working fine now but i hope, i can get them from your repository...

Kind regards in advance,
Comment 1 Björn Jacke 2011-08-05 12:49:17 UTC
you mean compiling the src rpm isn't possible if you have the system talloc packages installed ?  That isn't really a bug of the packages. This is due to the design of that lib being just backward compatible. With extensions of the abi the version of the lib doesn't increase, unfortunately, because this results is problems like those you see. I'd say just deinstall the talloc library is the way to go.
Comment 2 catWorkX 2011-08-15 06:29:09 UTC
@Björn: yes removing, i.e. rpm -e libtalloc-devel and rpm -e libtalloc1 along with all packages requiring the latter helped starting the compiled nmbd.

I would stronly suggest to prefix the symbols if the libtalloc provided aloing with your sourcepackage to avoid clashes of the "namespace"