samba - Sep 2016 - Upgrading samba from source over debian packages

On 2016-09-27 13:31, Marc Muehlfeld via samba wrote:
> Hello Elias,
> 
> Am 27.09.2016 um 18:16 schrieb Elias Pereira via samba: 
> 
>> We have samba 4.1.17 installed via debian package and would like to
install
>> the latest version 4.5 from source.
>> 
>> It's possible to perform this upgrade over the packages? If so,
what the
>> paths used in the installation via debian packages?
> 
>
https://wiki.samba.org/index.php/Build_Samba_from_Source#Viewing_Built_Options_of_an_Existing_Installation
> 
> Pass the paths as options to the 'configure' script. See --help.
> 
> Don't forget to uninstall the packages before running 'make
install'.
> Otherwise you risk that a Debian update overrides your setup or getting
> dependency problems.
> 
> Regards,
> Marc
When it comes to compiling from source I have just begun learning the
"ins and outs" as they say. Now . . . here is a real newbie question,
sorry but I don't know. What happens when said distro comes along with
their own upgrade? Let's just say the distro comes along with version
4.4.5 upgrade, for example, is my version 4.5.0 from source installed to
their paths ignored? As in left alone . . . as in their upgrade does not
"mess up" my compiled installation?

-- 
_______________________________

Bob Wooden of Donelson Trophy

Am 27.09.2016 um 23:17 schrieb Bob of Donelson Trophy via
samba:
> On 2016-09-27 13:31, Marc Muehlfeld via samba wrote:
>
>> Hello Elias,
>>
>> Am 27.09.2016 um 18:16 schrieb Elias Pereira via samba:
>>
>>> We have samba 4.1.17 installed via debian package and would like to
install
>>> the latest version 4.5 from source.
>>>
>>> It's possible to perform this upgrade over the packages? If so,
what the
>>> paths used in the installation via debian packages?
>>
>>
https://wiki.samba.org/index.php/Build_Samba_from_Source#Viewing_Built_Options_of_an_Existing_Installation
>>
>> Pass the paths as options to the 'configure' script. See
--help.
>>
>> Don't forget to uninstall the packages before running 'make
install'.
>> Otherwise you risk that a Debian update overrides your setup or getting
>> dependency problems.
>>
>> Regards,
>> Marc
>
> When it comes to compiling from source I have just begun learning the
> "ins and outs" as they say. Now . . . here is a real newbie
question,
> sorry but I don't know. What happens when said distro comes along with
> their own upgrade? Let's just say the distro comes along with version
> 4.4.5 upgrade, for example, is my version 4.5.0 from source installed to
> their paths ignored? As in left alone . . . as in their upgrade does not
> "mess up" my compiled installation?
surely when you use the default paths and hence you should learn to 
build packages and override the distro onces whenever it is possible in 
context of other dependencies

and even if you decide to install to /opt or /usr/local there is no 
valid reason not to learn build packages - when i can't something 
package to a rpm on my Fedora systems it has no reason to exist there be 
it perl, python or whatever stuff

On Tue, 27 Sep 2016 16:17:10 -0500
Bob of Donelson Trophy via samba <samba at lists.samba.org> wrote:
> On 2016-09-27 13:31, Marc Muehlfeld via samba wrote:
> 
> > Hello Elias,
> > 
> > Am 27.09.2016 um 18:16 schrieb Elias Pereira via samba: 
> > 
> >> We have samba 4.1.17 installed via debian package and would like
> >> to install the latest version 4.5 from source.
> >> 
> >> It's possible to perform this upgrade over the packages? If
so,
> >> what the paths used in the installation via debian packages?
> > 
> >
https://wiki.samba.org/index.php/Build_Samba_from_Source#Viewing_Built_Options_of_an_Existing_Installation
> > 
> > Pass the paths as options to the 'configure' script. See
--help.
> > 
> > Don't forget to uninstall the packages before running 'make
> > install'. Otherwise you risk that a Debian update overrides your
> > setup or getting dependency problems.
> > 
> > Regards,
> > Marc
> 
> When it comes to compiling from source I have just begun learning the
> "ins and outs" as they say. Now . . . here is a real newbie
question,
> sorry but I don't know. What happens when said distro comes along with
> their own upgrade? Let's just say the distro comes along with version
> 4.4.5 upgrade, for example, is my version 4.5.0 from source installed
> to their paths ignored? As in left alone . . . as in their upgrade
> does not "mess up" my compiled installation?
> 
If you have the distro's packages installed and also have a
selfcompiled SAmba installed in /usr/local/samba, about all that would
happen is that the libnss links will get messed with.

If you have the distro's packages installed and compile Samba
yourself, but install it over the distro's packages, your install
could be overwritten by a distro package update.

Moral: never have the distro's Samba packages installed at the same
time as having a self compiled Samba install.

Rowland

On 2016-09-27 16:40, Rowland Penny via samba wrote:
> On Tue, 27 Sep 2016 16:17:10 -0500
> Bob of Donelson Trophy via samba <samba at lists.samba.org> wrote:
> 
> On 2016-09-27 13:31, Marc Muehlfeld via samba wrote:
> 
> Hello Elias,
> 
> Am 27.09.2016 um 18:16 schrieb Elias Pereira via samba: 
> 
> We have samba 4.1.17 installed via debian package and would like
> to install the latest version 4.5 from source.
> 
> It's possible to perform this upgrade over the packages? If so,
> what the paths used in the installation via debian packages? 
>
https://wiki.samba.org/index.php/Build_Samba_from_Source#Viewing_Built_Options_of_an_Existing_Installation
> 
> Pass the paths as options to the 'configure' script. See --help.
> 
> Don't forget to uninstall the packages before running 'make
> install'. Otherwise you risk that a Debian update overrides your
> setup or getting dependency problems.
> 
> Regards,
> Marc
When it comes to compiling from source I have just begun learning the
"ins and outs" as they say. Now . . . here is a real newbie question,
sorry but I don't know. What happens when said distro comes along with
their own upgrade? Let's just say the distro comes along with version
4.4.5 upgrade, for example, is my version 4.5.0 from source installed
to their paths ignored? As in left alone . . . as in their upgrade
does not "mess up" my compiled installation?

If you have the distro's packages installed and also have a
selfcompiled SAmba installed in /usr/local/samba, about all that would
happen is that the libnss links will get messed with.

If you have the distro's packages installed and compile Samba
yourself, but install it over the distro's packages, your install
could be overwritten by a distro package update.

Moral: never have the distro's Samba packages installed at the same
time as having a self compiled Samba install.

Rowland   

Thank you Rowland. That is what I thought. To me, the novice that I am,
it seems odd to install to the distro paths when they could
inadvertently be overwritten during a standard distro upgrade. Thank you
the clear and simple answer.

-- 
_______________________________

Bob Wooden of Donelson Trophy

On 09/27/2016 05:17 PM, Bob of Donelson Trophy via samba
wrote:
> On 2016-09-27 13:31, Marc Muehlfeld via samba wrote:
>
>> Hello Elias,
>>
>> Am 27.09.2016 um 18:16 schrieb Elias Pereira via samba:
>>
>>> We have samba 4.1.17 installed via debian package and would like to
install
>>> the latest version 4.5 from source.
>>>
>>> It's possible to perform this upgrade over the packages? If so,
what the
>>> paths used in the installation via debian packages?
>>
https://wiki.samba.org/index.php/Build_Samba_from_Source#Viewing_Built_Options_of_an_Existing_Installation
>>
>> Pass the paths as options to the 'configure' script. See
--help.
>>
>> Don't forget to uninstall the packages before running 'make
install'.
>> Otherwise you risk that a Debian update overrides your setup or getting
>> dependency problems.
>>
>> Regards,
>> Marc
> When it comes to compiling from source I have just begun learning the
> "ins and outs" as they say. Now . . . here is a real newbie
question,
> sorry but I don't know. What happens when said distro comes along with
> their own upgrade? Let's just say the distro comes along with version
> 4.4.5 upgrade, for example, is my version 4.5.0 from source installed to
> their paths ignored? As in left alone . . . as in their upgrade does not
> "mess up" my compiled installation?
>
You have to choose which version you want to use -- repository or compiled

Most of the time, upgrades such as you describe don't occur until the 
LTS upgrade of the OS

Ubuntu 14.04 provided Samba 4.1.8  When Ubuntu upgraded to 16.04, that 
changed to 4.3.8 but look what's happened now - that's gone to security 
fixes only, and will be discontinued after a few more versions.

Although I've always wanted to use the repository version, I'm thinking 
of compiling my own to stay current.