Bug#881100: [Pkg-samba-maint] Bug#881100: libnss-winbind is not multiarch safe

2017-11-10 Thread Matthew Gabeler-Lee

On Fri, 10 Nov 2017, Mathieu Parent wrote:


This looks similar to #647430 which was solved in 2:4.6.5+dfsg-6.

Can you test from sid?


While that is likely a necessary component to fixing this, it is not 
sufficient.  That fixes a script error, this ticket is about package 
dependency errors between the various binary packages from the Samba 
source package.


Trying to install both "PC" architectures of libnss-winbind produces 
this error when targeting sid (which is basically the same as when targeting

stable or buster, just different package versions referenced):

The following packages have unmet dependencies:
 libnss-winbind : Depends: samba-libs (= 2:4.7.1+dfsg-1) but it is not going to 
be installed
  Depends: winbind (= 2:4.7.1+dfsg-1) but it is not going to be 
installed
 libnss-winbind:i386 : Depends: samba-libs:i386 (= 2:4.7.1+dfsg-1) but it is 
not going to be installed
   Depends: winbind:i386 (= 2:4.7.1+dfsg-1) but it is not 
going to be installed

You can't co-install multiple architectures of the winbind daemon, of
course.  I'm not an expert on Debian packaging, but I believe that could be
solved by changing the dependency there to be "arch any", since it just
needs to have the daemon be installed to communicate with it, not
necessarily have the daemon of the same architecture be running.  Though I
don't know if the local socket/pipe protocol it uses is maybe
architecture-specific (e.g. binary packed stuff that is dependent on the
cpu arch), so there might still be problems there.

The samba-libs problem seems to be related to samba-libs depending on
python-talloc, which is #862338.  As I noted before I'm not sure
libnss-winbind actually needs to depend on samba-libs at all, though I'm not
really sure of that.  Running strings on the shared libs shipped in
libnss-winbind doesn't find anything that looks like it's trying to dlopen
libraries from samba-libs, nor does it link against them directly.

--
-Matt
"Reality is that which, when you stop believing in it, doesn't go away".
-- Philip K. Dick
GPG fingerprint: 0061 15DF D282 D4A9 57CE  77C5 16AF 1460 4A3C C4E9



Bug#881100: [Pkg-samba-maint] Bug#881100: libnss-winbind is not multiarch safe

2017-11-10 Thread Mathieu Parent
2017-11-07 20:53 GMT+01:00 Matthew Gabeler-Lee :
> Package: libnss-winbind
> Version: 2:4.5.12+dfsg-2
> Severity: normal

Hi,

> Background: I use libnss-winbind, and a mulitiarch amd64/i386 system because
> I need to run some third party i386 binaries.  At least one of those
> binaries needs to be able to do nss lookups for some basic account 
> information.
>
> Trying to install libnss-winbind:i386 fails because:
>
> 1) It depends on the i386 version of the main winbind package.  This seems
>wrong-ish?  It just needs _some_ version of winbind installed so it can
>talk to it over the socket.
>
> 2) It depends on samba-libs, which fails multiarch because of at least
>#862338, though it's not immediately obvious to me _why_ it depends on
>samba-libs if the nss lib is just a thin shim to talk to other daemons?
>If it's dlopening stuff from that, though, it'd make sense.

This looks similar to #647430 which was solved in 2:4.6.5+dfsg-6.

Can you test from sid?

Regards

-- 
Mathieu Parent