Hi Andrew, I performed another upgrade yesterday
First a "git clean", then a "git pull", a "./configure --enable-selftest --enable-debug --enable-avahi", a "make", and finally a "make install" After this had completed, I found that an older version of samba and smbclient had been copied into /usr/bin/ overwriting the symbolic links I had put in there. So I had exactly the same problem as before. I hadn't made any other changes to the system, so I know it's something to do with the Samba4 upgrade/install process. The correct file path for samba and smbclient is /usr/local/samba/sbin - the installation process correctly installs the current version of those commands into that path. Is there something in the configure/make/make install process that copies files into /usr/bin/, or is something else happening? I'd look for it myself and contribute to the project if I only knew what I was doing :) Kind regards Graeme ________________________________ From: Andrew Bartlett <[email protected]> To: Michael Wood <[email protected]> Cc: Graeme Porter <[email protected]>; "[email protected]" <[email protected]> Sent: Saturday, 6 April 2013, 10:49 Subject: Re: [Samba] Samba4 fails to work following upgrade - library version errors On Fri, 2013-04-05 at 16:54 +0200, Michael Wood wrote: > Hi > It sounds like the "samba" binary on your PATH is the old version. Well spotted Michael, this one really had me stumped! Andrew Bartlett -- Andrew Bartlett http://samba.org/~abartlet/ Authentication Developer, Samba Team http://samba.org -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
