Obtaining Samba: Difference between revisions

From SambaWiki
m (Reformatting. Adding spaces between paragraphs)
m (Fixed typo)
 
(11 intermediate revisions by 2 users not shown)
Line 1: Line 1:
= Stable version (recommended) =
= Stable Version =


Running only stable versions of Samba is recommended.
You can download the latest version of Samba from [https://www.samba.org/ https://www.samba.org/].


Download the Samba sources only from [https://www.samba.org/ https://www.samba.org/].
It is always recommended that you install the latest version of the [[Samba_Release_Planning#Current_Stable_Release|current stable release]]. If you require to choose a previous series, always choose the last version out of the [[Samba_Release_Planning#Maintenance_Mode|Maintainance Mode series]] or at least from the [[Samba_Release_Planning#Security_Fixes_Only_Mode|Security Fixes Only Mode]]. Older version may not contain all improvements, bug- and security fixes. Also if you require help and ask e. g. on the [https://lists.samba.org/mailman/listinfo/samba Samba Mailing List], you typically will be told to try a recent version, to ensure that the problem isn't fixed in the meantime.


Samba always maintains three release series:
Further information about Samba Release Plannings and Supported Release Lifetime, you can find at the [[Samba_Release_Planning|Samba Release Planning]] page.
* [[Samba_Release_Planning#Current_Stable_Release|current stable]]
* [[Samba_Release_Planning#Maintenance_Mode|maintenance mode]]
* [[Samba_Release_Planning#Security_Fixes_Only_Mode|security fixes only mode]]


The Samba team recommends that you always install the latest version of a [[Samba_Release_Planning|supported release]]. This guarantees that your installation contains all available security fixes.


In case you discover any problem, please update your installation to the latest version of the [[Samba_Release_Planning#Current_Stable_Release|current stable]] release before. This ensures that the problem has not been fixed in the meantime and reduces duplicate bug reports and unnecessary questions on the [https://lists.samba.org/mailman/listinfo/samba Samba Mailing List].


For further information about the release planning and the Samba life cycle, see [[Samba_Release_Planning|Samba Release Planning]].




= Development versions =


== samba-master ==


'''Warning: Never install a development version in production! It may contain untested features and can cause damages to your installation! Development releases are for testing purposes only!'''


= Development Versions =
„samba-master“ contains the source of the [[Samba_Release_Planning#Upcoming_Release|upcoming release series]].


{{Imbox
To download the latest samba-master repository, run
| type = warning
| text = Never run a development version in a production environment. They contain untested features that can cause damages and data loss. Use development version only for testing purposes.
}}


$ git clone git://git.samba.org/samba.git samba-master






== The samba-master Branch ==
== Development version of a specific branch ==


The v*-test branches contain the latest changes and patches since the last official release of that source tree.


The <code>samba-master</code> branch contains the source code of the [[Samba_Release_Planning#Upcoming_Release|next release series]]. To download:
The following example demonstrates the checkout of the latest sources of Samba 4.1, scheduled for the next 4.1.x release:


$ git clone -b v4-1-test git://git.samba.org/samba.git samba-v4-1-test
$ git clone git://git.samba.org/samba.git samba-master


alternatively:


$ git clone -b v4-1-test http://git.samba.org/samba.git samba-v4-1-test


== Development Version of a Specific Branch ==


The <code>v*-test</code> branches contain the latest fixes and enhancements since the last release of the version source tree.


For example, to clone the latest development branch for Samba 4.5 using the git protocol:
== Updating a local git repository ==


$ git clone -b v4-5-test git://git.samba.org/samba.git samba-v4-5-test
If you already have downloaded a development source tree via „git“ and want to update it to the latest version, run the following command out of your corresponding git source directory:


To clone the same branch using the HTTP protocol:
$ git pull


$ git clone -b v4-5-test http://git.samba.org/samba.git samba-v4-5-test
If you receive the following error


fatal: Unable to create '[...]/.git/index.lock': File exists.


run


== Updating a Local Git Repository ==
$ git clean -x -f -d


To update a local cloned repository, run in the source directory:
to reset your tree.

$ git pull

Latest revision as of 20:16, 2 November 2016

Stable Version

Running only stable versions of Samba is recommended.

Download the Samba sources only from https://www.samba.org/.

Samba always maintains three release series:

The Samba team recommends that you always install the latest version of a supported release. This guarantees that your installation contains all available security fixes.

In case you discover any problem, please update your installation to the latest version of the current stable release before. This ensures that the problem has not been fixed in the meantime and reduces duplicate bug reports and unnecessary questions on the Samba Mailing List.

For further information about the release planning and the Samba life cycle, see Samba Release Planning.



Development Versions



The samba-master Branch

The samba-master branch contains the source code of the next release series. To download:

$ git clone git://git.samba.org/samba.git samba-master


Development Version of a Specific Branch

The v*-test branches contain the latest fixes and enhancements since the last release of the version source tree.

For example, to clone the latest development branch for Samba 4.5 using the git protocol:

$ git clone -b v4-5-test git://git.samba.org/samba.git samba-v4-5-test

To clone the same branch using the HTTP protocol:

$ git clone -b v4-5-test http://git.samba.org/samba.git samba-v4-5-test


Updating a Local Git Repository

To update a local cloned repository, run in the source directory:

$ git pull