Hi, just wanted to mention that the current dependency of libsmbclient to python-talloc cause a regression when upgrading from a samba3 based libsmbclient to a samba4 based libsmbclient in certain multiarch environments.
The problem is that libsmbclient:i386 and libsmbclient:amd64 can be co-installed with samba3 but no longer with samba4 because of the python-talloc dependency. Right now samba-libs contains a dependency on libpytalloc-util.so.2 library which is part of python-talloc. See https://bugs.launchpad.net/ubuntu/+source/samba4/+bug/1308657 for the details. The options are: 1. move libpytalloc-util.so.2 to libtalloc2 2. move /usr/lib/x86_64-linux-gnu/samba/libsamba_python.so.0 to samba-python 3. move libpytalloc-util.so.2 into its own libtalloc2-python (or similar) package I don't know enough about the samba4 packaging to have a strong opinion, but it seems like (1) is a reasonable solution as it does not require changing existing dependencies. It would mean a tiny additional lib (libpytalloc-util.so.2 - 11k on my system) in libtalloc2 that not everyone needs. I'm happy to work on a patch to get rid of the python-talloc dependency and unblock the multiarch upgrade, but I would like to hear from you what option you prefer. Cheers, Michael -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org