All software development progresses so quickly that anyone's script may not be current. Even a script I may have written. And that is the overall challenge with scripts, in general. We users become dependent on scripts. And we users need the learn independence. I have been learning what scripts do and how scripts do what they do. I was wanting to install 4.3.1 on Debian8 and see if I encountered bug #11573. (Had a CentOS 7 VM that will not domain provision due to bug #11573.) This holiday experiment idea will now end. Waiting until after v4.3.2 is released. Patience is a good thing. Thanks for suggestions and help, both Louis and Rowland. --- _______________________________ Bob Wooden of Donelson Trophy 615.885.2846 www.donelsontrophy.com [3] "Everyone deserves an award!!" On 2015-11-30 02:57, L.P.H. van Belle wrote:> Hi bob, > > I suggest, you stick on 4.3.0, if you use my script. > I dont advice to compile yourself, but thats what you want. > > You can use an unmodified packages also, but you need 2 or 3 packages from debian sid/experimental > > To keep is all safe do the following. > Create an preferences file so you can ping the experimental repo. > cat << EOF >> /etc/apt/preferences.d/experimental-samba > Package: * > Pin: release n=jessie,o=Debian > Pin-Priority: 500 > > Package: * > Pin: release n=jessie,l=Debian-Security > Pin-Priority: 500 > > Package: * > Pin: release n=jessie-updates > Pin-Priority: 500 > > Package: * > Pin: release n=jessie-backports > Pin-Priority: 400 > > Package: * > Pin: release a=testing > Pin-Priority: 100 > > Package: * > Pin: release a=unstable > Pin-Priority: 50 > > Package: * > Pin: release a=experimental > Pin-Priority: 400 > > EOF > > cat << EOF >> /etc/apt/sources.list.d/experimental.list > # > deb http://ftp.nl.debian.org/debian/ [1] experimental main non-free contrib > deb-src http://ftp.nl.debian.org/debian/ [1] experimental main non-free contrib > EOF > > Run apt-get update && apt-get upgrade. > Of ok, you wil not see an upgrade ( wel at least nog from experimental ) > > Now, type > apt-get build-dep samba > apt-get source samba -b > > and you have your samba debs when finished. > If it did complain about some packages, install them like > apt-get install -t experimental PACKAGE_NAME > > Greetz, > > Louis > -----Oorspronkelijk bericht----- Van: samba [mailto:samba-bounces at lists.samba.org] Namens Rowland Penny Verzonden: zondag 29 november 2015 15:25 Aan: samba at lists.samba.org Onderwerp: Re: [Samba] samba430-jessie script question On 29/11/15 13:54, Bob of Donelson Trophy wrote: Forgive me if this questions has been dealt with recently as I have been on a vacation/holiday and have not kept current with list activity. While building a VM with "setup-samba430-Jessie.sh" I notice that Debian 'experimental' is now (pulling) samba-4.3.1+dfsg-1 version. The script is not running correctly as (obviously) the patches are for samba-4.3.0+dfsg packages. Suggestions? This is something that Louis will have to fix, but I cannot really see the need to use such a script. By using Louis's script, you are dependant on him keeping it up to date, and when it isn't, you get problems like this, which may get worse as 4.3.2 is due out on Tuesday :-) You will probably be better off compiling Samba yourselfby following the wiki. You can then easily update to a new version when it comes out. You will also find that all the examples on the wiki will be valid, no need to alter paths etc. If you must use a script, write your own, after all, a script is mostly just a list of the commands you would enter one after another. Rowland -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba [2] Links: ------ [1] http://ftp.nl.debian.org/debian/ [2] https://lists.samba.org/mailman/options/samba [3] http://www.donelsontrophy.com
On 30/11/15 12:54, Bob of Donelson Trophy wrote:> > > All software development progresses so quickly that anyone's script may > not be current. Even a script I may have written. And that is the > overall challenge with scripts, in general. We users become dependent on > scripts. And we users need the learn independence. I have been learning > what scripts do and how scripts do what they do. > > I was wanting to install 4.3.1 on Debian8 and see if I encountered bug > #11573. (Had a CentOS 7 VM that will not domain provision due to bug > #11573.) This holiday experiment idea will now end. > > Waiting until after v4.3.2 is released. Patience is a good thing. > > Thanks for suggestions and help, both Louis and Rowland. > > >How about this: #!/bin/bash ## where to build samba. # NOTE: Samba will be installed to /usr/local/ # if build dir given and exists, then it will # used as build base, else /usr/src will be used if [ -n $1 ] && [ -d $1 ]; then SOURCELOCATION=$1 else SOURCELOCATION=/usr/src fi # Packages required to build Samba4 apt-get install -y build-essential libacl1-dev libattr1-dev libblkid-dev libreadline-dev python-dev libpam0g-dev python-dnspython gdb pkg-config libpopt-dev libldap2-dev dnsutils libbsd-dev attr krb5-user docbook-xsl libcups2-dev acl libkrb5-dev libssl-dev xsltproc krb5-config libpam-krb5 libgnutls28-dev # NOTE: to build on wheezy, replace 'libgnutls28-dev' with 'libgnutls-dev' echo "Compiling samba." echo "Please wait, this could take some time." # get latest samba tarball HERE=$(pwd) cd ${SOURCELOCATION} # NOTE: it downloads the latest tarball! wget -cq https://www.samba.org/samba/ftp/samba-latest.tar.gz tar zxf samba-latest.tar.gz cd samba* ./configure && make && make install cd ${HERE} # Set the path in /etc/profile.d/samba4.sh PATHTEST=$(echo $PATH | grep [s]amba) if [ -x "$PATHTEST" ]; then echo "PATH=/usr/local/samba/bin:/usr/local/samba/sbin:\$PATH" > /etc/profile.d/samba4.sh export PATH=/usr/local/samba/bin:/usr/local/samba/sbin:$PATH fi echo "Samba compiled." exit 0 This will install the packages required to build Samba on debian jessie, then download the latest Samba tarball, unpack it and then compile it. It has been tested (on Devuan jessie), it provisions as a DC and joins as a DC. Rowland
Thank you. And from what I have read. When the next "newer" version is released, stop samba services (all of them) and run the script and the script will replace the previously installed version by installing the newer version into the same location? --- _______________________________ Bob Wooden of Donelson Trophy 615.885.2846 www.donelsontrophy.com [2] "Everyone deserves an award!!" On 2015-11-30 07:35, Rowland Penny wrote:> On 30/11/15 12:54, Bob of Donelson Trophy wrote: > >> All software development progresses so quickly that anyone's script may not be current. Even a script I may have written. And that is the overall challenge with scripts, in general. We users become dependent on scripts. And we users need the learn independence. I have been learning what scripts do and how scripts do what they do. I was wanting to install 4.3.1 on Debian8 and see if I encountered bug #11573. (Had a CentOS 7 VM that will not domain provision due to bug #11573.) This holiday experiment idea will now end. Waiting until after v4.3.2 is released. Patience is a good thing. Thanks for suggestions and help, both Louis and Rowland. > > How about this: > > #!/bin/bash > > ## where to build samba. > # NOTE: Samba will be installed to /usr/local/ > # if build dir given and exists, then it will > # used as build base, else /usr/src will be used > if [ -n $1 ] && [ -d $1 ]; then > SOURCELOCATION=$1 > else > SOURCELOCATION=/usr/src > fi > > # Packages required to build Samba4 > apt-get install -y build-essential libacl1-dev libattr1-dev libblkid-dev libreadline-dev python-dev libpam0g-dev python-dnspython gdb pkg-config libpopt-dev libldap2-dev dnsutils libbsd-dev attr krb5-user docbook-xsl libcups2-dev acl libkrb5-dev libssl-dev xsltproc krb5-config libpam-krb5 libgnutls28-dev > > # NOTE: to build on wheezy, replace 'libgnutls28-dev' with 'libgnutls-dev' > > echo "Compiling samba." > echo "Please wait, this could take some time." > > # get latest samba tarball > HERE=$(pwd) > cd ${SOURCELOCATION} > # NOTE: it downloads the latest tarball! > wget -cq https://www.samba.org/samba/ftp/samba-latest.tar.gz [1] > tar zxf samba-latest.tar.gz > cd samba* > ./configure && make && make install > cd ${HERE} > > # Set the path in /etc/profile.d/samba4.sh > PATHTEST=$(echo $PATH | grep [s]amba) > if [ -x "$PATHTEST" ]; then > echo "PATH=/usr/local/samba/bin:/usr/local/samba/sbin:$PATH" > /etc/profile.d/samba4.sh > export PATH=/usr/local/samba/bin:/usr/local/samba/sbin:$PATH > fi > > echo "Samba compiled." > > exit 0 > > This will install the packages required to build Samba on debian jessie, then download the latest Samba tarball, unpack it and then compile it. > > It has been tested (on Devuan jessie), it provisions as a DC and joins as a DC. > > RowlandLinks: ------ [1] https://www.samba.org/samba/ftp/samba-latest.tar.gz [2] http://www.donelsontrophy.com