On Thu, 2020-04-16 at 07:34 +0100, Rowland penny wrote:> On 15/04/2020 21:29, Andrew Bartlett via samba wrote: > > That is correct. Most of the time this isn't an issue because the > > new > > ldb modules, linking to the new symbol versions, overwrite the old > > files on 'make install'. > > > > However we chose to remove some obsolete ldb modules in the 4.12 > > cycle > > and so the old modules remain, triggering these warnings. > > > > We notice the old modules because we try to load all the modules > > during > > startup of ldb to see if they wish to provide hooks for the command > > line handling in the ldb* tools. (But this happens for all ldb > > consumers, including samba-tool). > > > > Andrew Bartlett > > > > Andrew, if we are going to do things like this, don't you think it > would > be a good idea to document it in the release notes ?We could. This isn't the first time we have removed modules, and we haven't ever promised that you can install Samba on top of an existing installation, but you would be correct to say it has often worked. Andrew Bartlett -- Andrew Bartlett https://samba.org/~abartlet/ Authentication Developer, Samba Team https://samba.org Samba Developer, Catalyst IT https://catalyst.net.nz/services/samba
In that case I'd update the wiki and make that clear, since it misled me to believe that it could all be done "in-place" when compiling yourself :) https://wiki.samba.org/index.php/Build_Samba_from_Source#Upgrading_a_Self-compiled_Samba_Installation On 16/04/2020 08:12, Andrew Bartlett via samba wrote:> On Thu, 2020-04-16 at 07:34 +0100, Rowland penny wrote: >> On 15/04/2020 21:29, Andrew Bartlett via samba wrote: >>> That is correct. Most of the time this isn't an issue because the >>> new >>> ldb modules, linking to the new symbol versions, overwrite the old >>> files on 'make install'. >>> >>> However we chose to remove some obsolete ldb modules in the 4.12 >>> cycle >>> and so the old modules remain, triggering these warnings. >>> >>> We notice the old modules because we try to load all the modules >>> during >>> startup of ldb to see if they wish to provide hooks for the command >>> line handling in the ldb* tools. (But this happens for all ldb >>> consumers, including samba-tool). >>> >>> Andrew Bartlett >>> >> Andrew, if we are going to do things like this, don't you think it >> would >> be a good idea to document it in the release notes ? > We could. > > This isn't the first time we have removed modules, and we haven't ever > promised that you can install Samba on top of an existing installation, > but you would be correct to say it has often worked. > > Andrew Bartlett
Idea to think about before we change the wiki. I dont know what you guys say about this but..this part on the wiki.. Compiling Samba requires only a few steps: Install all dependencies. See Package Dependencies Required to Build Samba. Download the sources from samba.org Extract the source package Run ./configure make>> maybe add here.. : stop sambasudo make install>> and add: start samba.And if im correct you dont see these anymore.> ldb: unable to dlopen /usr/lib64/samba/ldb/local_password.so : > /usr/lib64/samba/libsamdb-common-samba4.so: version `SAMBA_4.11.6' notGreetz, Louis> -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens Alex > MacCuish via samba > Verzonden: donderdag 16 april 2020 11:53 > Aan: samba at lists.samba.org > Onderwerp: Re: [Samba] Samba-tool error after update to 4.12.0 > > In that case I'd update the wiki and make that clear, since > it misled me > to believe that it could all be done "in-place" when > compiling yourself :) > > https://wiki.samba.org/index.php/Build_Samba_from_Source#Upgra > ding_a_Self-compiled_Samba_Installation > > On 16/04/2020 08:12, Andrew Bartlett via samba wrote: > > On Thu, 2020-04-16 at 07:34 +0100, Rowland penny wrote: > >> On 15/04/2020 21:29, Andrew Bartlett via samba wrote: > >>> That is correct. Most of the time this isn't an issue because the > >>> new > >>> ldb modules, linking to the new symbol versions, overwrite the old > >>> files on 'make install'. > >>> > >>> However we chose to remove some obsolete ldb modules in the 4.12 > >>> cycle > >>> and so the old modules remain, triggering these warnings. > >>> > >>> We notice the old modules because we try to load all the modules > >>> during > >>> startup of ldb to see if they wish to provide hooks for > the command > >>> line handling in the ldb* tools. (But this happens for all ldb > >>> consumers, including samba-tool). > >>> > >>> Andrew Bartlett > >>> > >> Andrew, if we are going to do things like this, don't you think it > >> would > >> be a good idea to document it in the release notes ? > > We could. > > > > This isn't the first time we have removed modules, and we > haven't ever > > promised that you can install Samba on top of an existing > installation, > > but you would be correct to say it has often worked. > > > > Andrew Bartlett > > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/options/samba > >
No. It's not about stopping samba during make install. You would still see the issue because make install doesn't remove what's already there. Those instructions are good for a first time install, but the second time, you need to remove the ldb modules as Andrew said. The easiest way I find is just moving everything somewhere else and copying state back after running make install. Alex :) On 16/04/2020 11:33, L.P.H. van Belle via samba wrote:> Idea to think about before we change the wiki. > > I dont know what you guys say about this but..this part on the wiki.. > > Compiling Samba requires only a few steps: > > Install all dependencies. See Package Dependencies Required to Build Samba. > Download the sources from samba.org > Extract the source package > Run > ./configure > make >>> maybe add here.. : stop samba > sudo make install >>> and add: start samba. > And if im correct you dont see these anymore. >> ldb: unable to dlopen /usr/lib64/samba/ldb/local_password.so : >> /usr/lib64/samba/libsamdb-common-samba4.so: version `SAMBA_4.11.6' not > > Greetz, > > Louis > > >> -----Oorspronkelijk bericht----- >> Van: samba [mailto:samba-bounces at lists.samba.org] Namens Alex >> MacCuish via samba >> Verzonden: donderdag 16 april 2020 11:53 >> Aan: samba at lists.samba.org >> Onderwerp: Re: [Samba] Samba-tool error after update to 4.12.0 >> >> In that case I'd update the wiki and make that clear, since >> it misled me >> to believe that it could all be done "in-place" when >> compiling yourself :) >> >> https://wiki.samba.org/index.php/Build_Samba_from_Source#Upgra >> ding_a_Self-compiled_Samba_Installation >> >> On 16/04/2020 08:12, Andrew Bartlett via samba wrote: >>> On Thu, 2020-04-16 at 07:34 +0100, Rowland penny wrote: >>>> On 15/04/2020 21:29, Andrew Bartlett via samba wrote: >>>>> That is correct. Most of the time this isn't an issue because the >>>>> new >>>>> ldb modules, linking to the new symbol versions, overwrite the old >>>>> files on 'make install'. >>>>> >>>>> However we chose to remove some obsolete ldb modules in the 4.12 >>>>> cycle >>>>> and so the old modules remain, triggering these warnings. >>>>> >>>>> We notice the old modules because we try to load all the modules >>>>> during >>>>> startup of ldb to see if they wish to provide hooks for >> the command >>>>> line handling in the ldb* tools. (But this happens for all ldb >>>>> consumers, including samba-tool). >>>>> >>>>> Andrew Bartlett >>>>> >>>> Andrew, if we are going to do things like this, don't you think it >>>> would >>>> be a good idea to document it in the release notes ? >>> We could. >>> >>> This isn't the first time we have removed modules, and we >> haven't ever >>> promised that you can install Samba on top of an existing >> installation, >>> but you would be correct to say it has often worked. >>> >>> Andrew Bartlett >> -- >> To unsubscribe from this list go to the following URL and read the >> instructions: https://lists.samba.org/mailman/options/samba >> >> >
On 16/04/2020 11:33, L.P.H. van Belle via samba wrote:> And if im correct you dont see these anymore. >> ldb: unable to dlopen /usr/lib64/samba/ldb/local_password.so : >> /usr/lib64/samba/libsamdb-common-samba4.so: version `SAMBA_4.11.6' notEven though Andrew says that modules have been removed (what modules ?), on a self compiled Samba the '.so' files in /usr/lib64 shouldn't be used if the path is correct. When you compile Samba yourself, by default everything ends up in /usr/local/samba. If you then run /usr/local/samba/bin/samba-tool, then it should use the libs under /usr/local/samba, not the ones under /usr/lib64/samba. Also, if you have just compiled 4.12.0, it shouldn't attempt to use libs from 4.11.6 The last time this happened (as far as I can recall) was when the Samba python time.py was removed, but this was because it wasn't removed from on disk and Samba still used it, instead of the standard python 'time' module. So, if you compile Samba yourself './configure && make && sudo make install', it will just overwrite what is in /usr/local/samba on a like for like basis, but anything that no longer gets compiled will not get removed. However, self compiled Samba shouldn't use Samba modules outside /usr/local/samba. Rowland