Comment 11 for bug 1629038

Hi,
so the lib that is missing the other symbols "should" not be installed at all.

I also found that I had only x86_64 versions of it.
$ ll /usr/lib/*/libndr.so.0
lrwxrwxrwx 1 root root 15 Sep 23 19:44 /usr/lib/x86_64-linux-gnu/libndr.so.0 -> libndr.so.0.0.5
$ dpkg -S /usr/lib/*/libndr.so.0
samba-libs:amd64: /usr/lib/x86_64-linux-gnu/libndr.so.0

On i386 the same looks like this:
$ ll /usr/lib/*/libndr.so.0
lrwxrwxrwx 1 root root 15 Sep 23 19:45 /usr/lib/i386-linux-gnu/libndr.so.0 -> libndr.so.0.0.5
$ dpkg -S /usr/lib/*/libndr.so.0
samba-libs:i386: /usr/lib/i386-linux-gnu/libndr.so.0

Both working fine.

I tried to force some chaos by installing i386 packages onto x86_64 system and vice versa.
dpkg --add-architecture i386
apt-get update
# for dependencies I need to install more than just libs
apt-get install samba-libs:i386 python-talloc:i386 python:i386
# apt is smart about conflicts as I see
[...]
The following packages will be REMOVED:
  python python-crypto python-ldb python-minimal python-samba python-talloc python-tdb python2.7 python2.7-minimal samba samba-common-bin samba-dsdb-modules samba-libs
  samba-vfs-modules
[...]
# And afterwards I get a correct working samba:
$ ll /usr/lib/*/libndr.so.0
lrwxrwxrwx 1 root root 15 Sep 23 19:45 /usr/lib/i386-linux-gnu/libndr.so.0 -> libndr.so.0.0.5
$ dpkg -S /usr/lib/*/libndr.so.0
samba-libs:i386: /usr/lib/i386-linux-gnu/libndr.so.0

You seem to have a mixed environment, for that a few questions.
- do you have a 64 or 32 bit setup in general?
- and old experiments around samba libs?
- any experiments around multiarch?
- Did you maybe in the past build a custom 32bit samba that still has libs around interfering with the packaged samba?
- please report "ll /usr/lib/*/libndr.so.0" and "dpkg -S /usr/lib/*/libndr.so.0"
- if your /usr/lib/i386-linux-gnu/libndr.so.0 doesn't belong to a package where did it come from?