Build an Official ISO/SME10

From SME Server
PythonIcon.png Skill level: Developer
Risk of inconsistencies with Koozali SME Server methodology, upgrades & functionality is high. One must be knowledgeable about how changes impact their Koozali SME Server. Significant risk of irreversible harm.

Warning.png Work in Progress:
This page is a Work in Progress. The contents off this page may be in flux, please have a look at this page history the to see list of changes.

This page uses some transclusion from the main page Build_an_Official_ISO



These Notes have been kindly shared by Ian Wells, thanks to him. This howto is there to document the way on the build of an official Iso. For an introduction you must follow first this howto and get a full workable buildserver

bugzilla:7675 build_installer and build_ISO are meant to be run in a mock chroot with the stage tree nfs mounted into it. The build box can be the same, eg COS6 x64 for all ISOs, it is only the mock image that needs to match the ISO, and this is magically handled by the mock configs. You also need to have access to the extras repo as many of the packages needed to build the installer and ISO are contained in there. This repo is to house the needed packages that aren't going to be included in the ISO. For clarification read

bugzilla:7931 Please read Bug #7931 regarding repodata and symlinks.

Warning.png Warning:
due to the recent change of some plugins, this howto is only workable now, with the Mock Version: 1.1.41 --Stephdl (talk) 21:40, 16 March 2015 (CET)

du to the work of dani, we should use theversion of mock > 1.2 --Stephdl (talk) 11:06, 29 June 2015 (CEST)

Warning.png Warning:
build of iso on cluster should be done on builder7 with releases user

Folder structure, both local and buildsys

This document presumes that

~/smeserver/builds_bin is builds_bin from CVS
~/smeserver/cdrom.image is cdrom.image from CVS
~/anaconda-po contains the anaconda translations
~/smeserver/releases contains a local smeserver mirror 
~/smeserver/rpms is rpms folder from CVS

if absent then :

cd ~ 
mkdir -p smeserver/builds_bin smeserver/cdrom.image smeserver/cdrom.image
ln -s smeserver/builds_bin builds_bin 
ln -s smeserver/cdrom.image cdrom.image
mkdir anaconda-po

then update content or populate

cd smeserver
cvs -z3 co -P builds_bin
cvs -z3 co -P cdrom.image
cvs -z3 co -P rpms
cd ~

Local Only: mock requirement

on centos 7

yum install python-decoratortools

Local Only: mock plugin : iso_prepare

You have to install a new plugin for mock : Iso_prepare

copy the content of (updated for CentOS 7 and python 3.6) and paste it in

sudo  wget -O /usr/lib/python3.6/site-packages/mockbuild/plugins/

Local Only: update_repos

The script update_repos relies on RPM2 which can be found as a RPM.

yum install perl-RPM2 repoview --enablerepo=epel

update_repos (/build/smeserver/stage/bin/update_repos) is used to keep the repos in sync and to create the ‘stage’ from which the ISO is built. On the local build system update_repos can be run manually before building an ISO, whereas it runs every hours on the buildsys.

Important.png Note:
Note that update_repos copies packages from smeupdates-testing to stage but not from smetest, so packages freshly built won't be included into the new ISO until they are manually moved from smetest to smeupdates-testing

The buildsys has two main folders that are relevant for building an ISO.

repo      => '/build/smeserver/repo/ ', eg '/build/smeserver/repo/testing/9/'
stage     => '/build/smeserver/stage/', eg  '/build/smeserver/stage/9/'
  • repo is the folder that replicates to the mirrors. Be careful of all changes here.
  • stage is the working directory. Note that update_repos expects the folder structure to be in place.

It also needs all GPG keys for every package that it sees, it can take a while to find them all.

Local Only: Create the repo folder and the binary program folder

Local Only

mkdir -p /build/smeserver/repo
mkdir -p /build/smeserver/stage/bin

The content of builds_bin from CVS needs to be copied to /build/smeserver/stage/bin


/bin/cd ~/smeserver/builds_bin
/usr/bin/cvs update -dPA
/bin/cp ~/smeserver/builds_bin/* /build/smeserver/stage/bin

Local Only: Mock Special Settings

  • hard-coded UID of release account

verify that in all /etc/mock/smeserver-{i386,x86_64}-iso.cfg you have config_opts['chrootuid'] = os.getuid()

- config_opts['chrootuid'] = 10020
+ config_opts['chrootuid'] = os.getuid()
Important.png Note:
Due to local settings you have to edit each configuration of mock and edit smeserver-X-{i386,x86_64}-iso.cfg files to include /build in the chroot

These are the changes that you need to made if you do not have the nfs mounts on your local machine
config_opts['plugin_conf']['mount_opts']['dirs'].append(('storage:/export/build', '/build', 'nfs', 'defaults,noatime,nodiratime,nosuid'))
config_opts['plugin_conf']['mount_opts']['dirs'].append(('storage:/mirrors', '/mirrors', 'nfs', 'defaults,noatime,nodiratime,nosuid'))


#config_opts['plugin_conf']['mount_opts']['dirs'].append(('storage:/export/build', '/build', 'nfs', 'defaults,noatime,nodiratime,nosuid'))
#config_opts['plugin_conf']['mount_opts']['dirs'].append(('storage:/mirrors', '/mirrors', 'nfs', 'defaults,noatime,nodiratime,nosuid'))
config_opts['plugin_conf']['bind_mount_opts']['dirs'].append(('/build', '/build' ))


sudo vim /etc/mock/smeserver-9-x86_64-iso.cfg

Local Only: Patch a Mock Plugin

Important.png Note:
this does not seems to be needed anymore on a CentOS 7 builder using python3.6 as per 2020/06/11

There is also an update to /usr/lib/python2.6/site-packages/mockbuild/ that needs to happen so loop devices get mounted correctly. Check /var/lib/mock/smeserver-VERSION-ARCH/result/root.log after mock -r smeserver-VERSION-ARCH-iso --init (eg mock -r smeserver-8-i386-iso --init). The mounting of the /dev/loopX should pass (return code 0). If it fails (return code 32) then the patch below is needed on your build host. see

save as see

--- /usr/lib/python2.6/site-packages/mockbuild/	2015-06-04 13:34:04.000000000 +0200
+++	2015-06-26 18:05:53.924416540 +0200
@@ -76,6 +76,9 @@
    def mount(self):
+        if not os.path.isdir(self.srcpath) and not os.path.isfile(self.srcpath):
+            util.touch(self.bindpath)
        if not self.mounted:
            cmd = ['/bin/mount', '-n',
                   '--bind', self.srcpath, self.bindpath ]
@@ -126,5 +129,9 @@

+    def get_mounted(self):
+        return [ m.mountpath for m in self.mounts if m.ismounted() ]
+    @traceLog()
    def get_mountpoints(self):
        return [ m.mountpath for m in self.mounts ]

then do

sudo patch -N  /usr/lib/python2.6/site-packages/mockbuild/ <

save as see

--- /usr/lib/python2.6/site-packages/mockbuild/plugins/	2015-06-04 13:34:04.000000000 +0200
+++	2015-06-26 18:05:53.921418037 +0200
@@ -41,11 +41,11 @@
        self.opts = conf
        plugins.add_hook("preinit", self._mountPreInitHook)
        for device, dest_dir, vfstype, mount_opts in self.opts['dirs']:
-            builroot.mounts.add(FileSystemMountPoint(buildroot.make_chroot_path(dest_dir),
+            buildroot.mounts.add(FileSystemMountPoint(buildroot.make_chroot_path(dest_dir),
    def _mountPreInitHook(self):
        for device, dest_dir, vfstype, mount_opts in self.opts['dirs']:
-            mockbuild.util.mkdirIfAbsent(self.builroot.make_chroot_path(dest_dir))
+            mockbuild.util.mkdirIfAbsent(self.buildroot.make_chroot_path(dest_dir))

then do

sudo patch -N  /usr/lib/python2.6/site-packages/mockbuild/plugins/ <

Preparation of a new Major Release

this part is a work in progress and might help for SME 11

Check how to tweak Anaconda

download last anaconda package from CentOS and update source in buildsys. Do this on shell VM.

~/smeserver/common/ -b sme10 anaconda-
cd ~/smeserver/rpms/anaconda/sme10

then you want to harvest the pathc we already have. For SME10:

  1. 100-anaconda-koozali-product.patch
  2. 101-anaconda-koozali-add-koozali-install-class.patch
cvs add 100-anaconda-koozali-product.patch

cvs add 101-anaconda-koozali-add-koozali-install-class.patch

#alternative could to play with
#$ cvs update -p -r rev file.txt > file.txt
#$ cvs add file.txt
#$ cvs commit

then add to the spec file the needed elements to apply the patches, and udpate changelog

## at beginning

Patch100: 100-anaconda-koozali-product.patch
Patch101: 101-anaconda-koozali-add-koozali-install-class.patch

### in %prep

%patch100 -p1
pushd pyanaconda/installclasses/
cp -f
%patch101 -p1

### in changelog
* Tue Feb 16 2021 Jean-Philipe Pialasse <>
- patch for product.img branding of anaconda

then commit

cvs commit

also prepare for later usage

make clean
make prep

if it fails applying the patches you will need to manually modify the files and ceate new patches...

Update isolinux content


Update cdrom.image content

Update cdrom.image to the latest in CVS

create a new tree if this is a new SME version

cd smeserver
cvs -z3 co -P cdrom.image
cd cdrom.image 
cp -r sme9 sme10
rm -rf sme10/CVS
rm -rf sme10/isolinux/CVS
rm -rf sme10/Packages/base/CVS  
rm -rf sme10/Packages/CVS
rm -rf sme10/product/CVS
rm -rf sme10/product/installclasses/CVS
rm -rf sme10/product/pixmaps/CV
rm -rf sme10/updates/CVS
cvs add sme10
cd sme10

add new key


do a little tidy up, then

find ./ -name CVS -prune -o -print | xargs cvs add
cvs commit -m 'new cdrom.image version for sme10'

alternatively to only update content

cd ~/cdrom.image 
cvs update -dPA

Preparation for a new ISO release

Generate a new Changelogs

When generating an ISO the Release Notes for the ISO should contain the full delta from the last ISO. Ian gets a script for doing that

When it is available you need to put it there:

to do this :

cd ~/smeserver/cdrom.image 
cvs update -dPA
cd  sme9/

then copy the new version, as instance you could do this:

cp ~/ReleaseNotes.txt README.txt

then commit:

cvs commit -m "Release 9.2" README.txt

The Smeserver version name

The Version number comes from a rpm, smeserver-release, you need to bump the version in the spec file and build the rpm, think to push it to smeupdates-testing.

RPM dependencies

The smeos, smeupdates, and smeupdates-testing repos are included so we can stage the packages we are going to release without actually having to release them. Normally the smeupdates-testing repo is used for verification (testing is for developer testing). During the ISO release schedule (usually very short) we hold moving packages to updates-testing until the ISO is built.

Examples of dependencies
cp /mirrors/rpmforge/redhat/el6/en/i386/dag/RPMS/perl-Taint-Util-0.08-1.el6.rf.i686.rpm /build/smeserver/repo/testing/9/smetest/i386/RPMS/
cp /mirrors/centos/6/os/i386/Packages/libtevent-0* /build/smeserver/repo/testing/9/smeupdates-testing/i386/RPMS/

This shows that on the buildsys the /mirrors has the main upstream repos and they will normally hold the RPM needed to resolve the dependency. You need to get it into smeupdates-testing, but it is safer to first copy the RPM to smetest and check that all is well.

Rpm update cycle

If an RPM is released during the update cycle:


If an RPM is only needed for a new ISO and never needed as an update (before the ISO is released) :


Note that you don't put it into smeos, that is taken care of by the build scripts.

What are smeos/smeextras
  • Every package that needs to be in the ISO will go into smeos, by the buildsys.
  • Packages that are needed for building the ISO, but not actually needed in the ISO, will be in smeextras
How get a Fully updated ISO

If your Iso is not fully updated and a 'yum update' fetch updates after the first boot, in generally centos updates. You will need to push missed updates from smetest to smeupdates-testing.

RPM QA verification

Warning.png Warning:

Server-Manager translations

Check translations from if the filesize is >0 then need to patch smeserver-locale (to sme8 & sme9) and produce new rpms that will must be pushed to smeupdate-testing

Anaconda translations

Check installer translations from

get the latest files (-w 1 means wait one second between two requests, to prevent your IP behing blacklisted):

wget --mirror --no-parent -w 1 -P ~/anaconda-po

you can also fast the operation by doing the following if you only need on sme version:

mkdir ~/anaconda-po/sme9
wget --mirror --no-parent -w 1 -P ~/anaconda-po/sme9

Check if installer needs re-building

Warning.png Warning:
If either anaconda has changed OR there is new content in cdrom.image (apart from the release note) then the installer needs to be rebuilt (by the script build_installer). Otherwise just the ISO needs to be built (by the script Build_ISO).

Check Anaconda version

Check which anaconda was used upstream, (eg & and is it newer than the one in CVS. If it is then anaconda needs to be updated and patched. | The latest Anaconda also needs to be in smeextras.

Bump smeserver-release if needed

Most of the time, we'll create a new ISO when we release a new SME Server version. So, we have to bump the version of the smeserver-release RPM.

Important.png Note:
Be careful to bump the version, the release and the displayversion macro, eg
%define version 9.2
%define release 0.rc2
%define displayversion %{version}rc2

or with final release:

%define version 9.2
%define release 1
%define displayversion %{version}

Do not forget the changelog !

Bump version in the splash screen

We need to update the title of the splsh screen. For this, we have to update the title line in cdrom.images/sme9/isolinux/isolinux.cfg, eg

menu title Welcome to SME Server 9.2 RC2

to do this :

cd ~/smeserver/cdrom.image 
cvs update -dPA
cd  sme9/isolinux/
vim isolinux.cfg

then edit, and finish with:

cvs commit -m "Release 9.2" isolinux.cfg

Remove the 'Beta warning' in Anaconda

For SME10

edit the file .buildstamp

cd /build/smeserver/stage/extra/images/10/product
vim .buildstamp
Product=Koozali SME Server

change isFinal to True

Also bump the Version !

For SME9

The Iso gets a 'beta' tag with warnings during the install process. How remove the beta tag, add --final in the /build/smeserver/stage/bin/build_installer

# add --final when we have final product
  PYTHONPATH=/usr/lib/anaconda/ sudo /usr/lib/anaconda-runtime/buildinstall \
      --product "$distname" \
      --version "${distvers/[^0-9.]*/}" \
      --release "$distname" \
      --brand "centos" \
      --final \
      --bugurl \
      --output $(pwd)/$distarch/ \
      /build/smeserver/repo/$distrel/smeextras/$distarch/ \
  /bin/sed -i -e "s|packagedir =.*|packagedir = Packages|" $(pwd)/$distarch/.treeinfo

Prepare SME Server

Local Only: Update local mirror as seen by the chroot

Local Only

rsync -av --delete --progress ~/smeserver/releases/10/ /build/smeserver/repo/10

Create release specific folder and link (or rename the folder)

The build_installer and build_ISO expect to be run from a directory that points to the head of the stage (ex. /build/stage/8). This is usually a symlink to 8.1 or 8.1beta1. The script fully expands the symlink and pulls off the last element to figure out what version we are going to build.

mkdir -p /build/smeserver/stage/$VERSION/{SRPMS,x86_64}
mkdir -p /build/smeserver/stage/$VERSION/x86_64/{Packages,EFI,images,isolinux,LiveOS,repodata,repoview,updates,product,netinstall}
mkdir -p /build/smeserver/stage/$VERSION/x86_64/Packages/base
mkdir -p /build/smeserver/stage/$VERSION/x86_64/images/pxeboot
cd /build/smeserver/stage/
rm -f $VER

Get last LiveOS from centos

cd /build/smeserver/stage/$VERSION/x86_64/LiveOS

Get CentOS last images content

cd /build/smeserver/stage/$VERSION/x86_64/Packages/images
cd /build/smeserver/stage/$VERSION/x86_64/images/pxeboot

Prepare to build the product.img. There should be some pictures to copy from previous builds. Some modification from anaconda

cd  /build/smeserver/stage/$VERSION/x86_64/product/
rsync -arv /build/smeserver/repo/testing/$VERPREV/smeos/x86_64/product /build/smeserver/stage/$VERSION/x86_64/

make any needed modification in the product image. at least update the release version

vim .buildstamp 

those files should be updated via anaconda, if not, do it and return there.

cp ~/smeserver/rpms/anaconda/sme10/anaconda-  run/install/product/pyanaconda/installclasses/
cp ~/smeserver/rpms/anaconda/sme10/anaconda- usr/lib64/python2.7/site-packages/pyanaconda/installclasses/
cp ~/smeserver/rpms/anaconda/sme10/anaconda- usr/lib64/python2.7/site-packages/pyanaconda/installclasses/
cp ~/smeserver/rpms/anaconda/sme10/anaconda- usr/lib64/python2.7/site-packages/pyanaconda/installclasses/

build new product.img and copy it to stage, if you want but it should be done by the build.ISO script

#find . | cpio -c -o | gzip -9cv > ../product.img; cd ..
#mkdir -p /build/smeserver/stage/$VER/x86_64/images/
#cp product.img /build/smeserver/stage/$VER/x86_64/images/

Populate isolinux dir:

rsync -arv /mirrors/centos/7/os/x86_64/isolinux/* /build/smeserver/stage/$VERSION/x86_64/isolinux/

now if you have not updated files for isolinux in smeserver/cdrom.image/sme10/isolinux in cvs it is time, and also to refresh the local copy

pushd ~/smeserver/cdrom.image/sme10/
cvs update
rsync -arv ~/smeserver/cdrom.image/sme10/isolinux/* /build/smeserver/stage/$VERSION/x86_64/isolinux/ --exclude=CVS

Populate EFI

rsync -arv /mirrors/centos/7/os/x86_64/EFI /build/smeserver/stage/$VERSION/x86_64/
rsync -arv ~/smeserver/cdrom.image/sme10/EFI/* /build/smeserver/stage/$VERSION/x86_64/EFI/ --exclude=CVS

populate netinstall

rsync -arv ~/smeserver/cdrom.image/sme10/netinstall /build/smeserver/stage/$VERSION/x86_64/ --exclude=CVS

populate Packages/base

rsync -arv ~/smeserver/cdrom.image/sme10/

Create cdrom content

WIP: From there on with SME 10, we are copying EFI, LiveOS, isolinux, images folders from CentOS or previous version and add over some files from CVS or rebuild some img files.

this has to be done before building product.img and put it in images. Also you will have to update the isolinux.cfg content.

When starting from fresh rsync can copy cdrom.image content, it also generates the folder tree.

Warning.png Warning:
Before doing this, you should use an account with CVS write access to bump the version or alter the following files:
  1. Packages/base/comp.xml
  2. isolinux{boot.msg, help.txt,isolinux.cfg}
  3. updates/README.txt

Refresh cdrom content

If only refreshing the files, then remove the delete.

cd ~/smeserver
cvs -z3 co -P cdrom.image
rsync -rloDv --exclude 'CVS/'  ~/smeserver/cdrom.image/sme10/ /build/smeserver/stage/$VER/x86_64/

Create the remaining folders

Important.png Note:
Note: TO DO translations in the updates image or move to product ?

  • x86_64
cd /build/smeserver/stage/10/x86_64
mkdir -p /build/smeserver/stage/10/x86_64/repodata/
mkdir -p /build/smeserver/stage/10/x86_64/updates/po
mkdir -p /build/smeserver/stage/10/x86_64/updates/textw
mkdir -p /build/smeserver/stage/10/x86_64/updates/iw
mkdir -p /build/smeserver/stage/10/x86_64/updates/storage/devicelibs
  • other directories
mkdir -p /build/smeserver/stage/iso/$VER/{x86_64,source}

Copy anaconda translations

Anaconda translations need copying to /updates/po from ~/anaconda-po

cp -R ~/anaconda-po/* /build/smeserver/stage/10/x86_64/updates/po/

Copy anaconda content

See ~/smeserver/cdrom.image/sme10/updates/README.txt for details of what to copy. The patched anaconda files from ~/smeserver/rpms/anaconda/sme10 will go to updates directory. The exact directory depends on the anaconda version, eg ~/smeserver/rpms/anaconda/sme10/anaconda-

pushd ~/smeserver/rpms/anaconda/sme10/
cvs update -dPA
make prep
cp ~/smeserver/rpms/anaconda/sme10/anaconda- /build/smeserver/stage/$VERSION/x86_64/product/usr/lib64/python2.7/site-packages/pyanaconda/
cp ~/smeserver/rpms/anaconda/sme10/anaconda-{fedora,centos,koozali}.py /build/smeserver/stage/$VERSION/x86_64/product/usr/lib64/python2.7/site-packages/pyanaconda/installclasses/
cp ~/smeserver/rpms/anaconda/sme10/anaconda- /build/smeserver/stage/$VERSION/x86_64/product/usr/lib64/python2.7/site-packages/pyanaconda/packaging/
cp ~/smeserver/rpms/anaconda/sme10/anaconda- /build/smeserver/stage/$VERSION/x86_64/product/run/install/product/pyanaconda/installclasses/

Local Only: Hack: Permission Fixup

This is only needed on local server if permissions are incorrect. It should not be needed.

Local Only

sudo chmod -R a+w /build/smeserver/stage

Local Only: Create stage content

Important.png Note:
Note: This step occurs every hours on the buildsys.

Local Only


Build & Release SME Server


You can find logs of the related scripts build_ISO and build_installer

If something goes wrong, please verify first


and after if you have no errors


Build SME Server 10 64 bit ISO

rm -f /build/smeserver/stage/$VER/x86_64/SME
mock -r smeserver-$VER-x86_64-iso --init
# not to do #mock -r smeserver-$VER-x86_64-iso --mount --cwd /build/smeserver/stage/$VER --unpriv --chroot /build/smeserver/stage/bin/build_installer
mock -r smeserver-$VER-x86_64-iso --mount --cwd /build/smeserver/stage/$VER --unpriv --chroot /build/smeserver/stage/bin/build_ISO
local only
rm -f /build/smeserver/stage/$VER/x86_64/SME
mock -r smeserver-$VER-x86_64-iso --init
#not to do #mock -r smeserver-$VER-x86_64-iso --mount --cwd /build/smeserver/stage/$VER --unpriv --chroot /build/smeserver/stage/bin/build_installer
sudo chmod -R a+w /build/smeserver/stage
mock -r smeserver-$VER-x86_64-iso --mount --cwd /build/smeserver/stage/$VER --unpriv --chroot /build/smeserver/stage/bin/build_ISO

Where are My F... ISO

ls /build/smeserver/stage/iso/8/
i386  source  x86_64


ls /build/smeserver/stage/iso/9/
i386  source  x86_64


ls /build/smeserver/stage/iso/10/
source  x86_64

Dev access to release ISO

Prepare directory structure for SME10 release

SME 10.x test releases will go to /build/smeserver/repo/testing/10. Check that the link points to the correct testing release. Note when uploading Jigdos the ‘10’ link will not be pointing to the new directory.

mkdir -p /build/smeserver/repo/testing/$VERSION/iso/source/
mkdir -p /build/smeserver/repo/testing/$VERSION/iso/x86_64/
mkdir -p /build/smeserver/repo/testing/$VERSION/smeos/x86_64/
Copy SME Server 10 64 bit Jigdo to mirror
/bin/cp -a /build/smeserver/stage/iso/$VER/x86_64/smeserver-$VERSION-x86_64.jigdo /build/smeserver/repo/testing/$VERSION/iso/x86_64/
/bin/cp -a /build/smeserver/stage/iso/$VER/x86_64/smeserver-$VERSION-x86_64.template /build/smeserver/repo/testing/$VERSION/iso/x86_64/
rsync -a --delete /build/smeserver/stage/$VER/x86_64/ /build/smeserver/repo/testing/$VERSION/smeos/x86_64/

Copy SME Server 10 SRPMS Jigdo to mirror
/bin/cp -a /build/smeserver/stage/iso/$VER/source/smeserver-$VERSION-SRPMS.jigdo /build/smeserver/repo/testing/$VERSION/iso/source/
/bin/cp -a /build/smeserver/stage/iso/$VER/source/smeserver-$VERSION-SRPMS.template /build/smeserver/repo/testing/$VERSION/iso/source/
rsync -a --delete /build/smeserver/stage/$VER/SRPMS/ /build/smeserver/repo/testing/$VERSION/smeos/SRPMS
Copy SME Server 10 ISOs to mirror
rsync -a --delete /build/smeserver/stage/iso/$VER/ /build/smeserver/repo/testing/$VERSION/iso

Hard links

As an example how to create the hard links:

#this one already rsynced from stage
#cp -lr /build/smeserver/repo/testing/$VERPREV/smeos/* /build/smeserver/repo/testing/$VERSION/smeos/
mkdir -p /build/smeserver/repo/testing/$VERSION/smeaddons/
mkdir -p /build/smeserver/repo/testing/$VERSION/smecontribs/
mkdir -p /build/smeserver/repo/testing/$VERSION/smedev/
mkdir -p /build/smeserver/repo/testing/$VERSION/smeextras/
mkdir -p /build/smeserver/repo/testing/$VERSION/smetest/
mkdir -p /build/smeserver/repo/testing/$VERSION/smeupdates/
mkdir -p /build/smeserver/repo/testing/$VERSION/smeupdates-testing/
cp -lr /build/smeserver/repo/testing/$VERPREV/smecontribs/* /build/smeserver/repo/testing/$VERSION/smecontribs/
cp -lr /build/smeserver/repo/testing/$VERPREV/smedev/* /build/smeserver/repo/testing/$VERSION/smedev/
cp -lr /build/smeserver/repo/testing/$VERPREV/smeextras/* /build/smeserver/repo/testing/$VERSION/smeextras/
cp -lr /build/smeserver/repo/testing/$VERPREV/smetest/* /build/smeserver/repo/testing/$VERSION/smetest/
cp -lr /build/smeserver/repo/testing/$VERPREV/smeupdates/* /build/smeserver/repo/testing/$VERSION/smeupdates/
cp -lr /build/smeserver/repo/testing/$VERPREV/smeupdates-testing/* /build/smeserver/repo/testing/$VERSION/smeupdates-testing/
cp -lr /build/smeserver/repo/testing/$VERPREV/smeaddons/* /build/smeserver/repo/testing/$VERSION/smeaddons/
Switch main version link

and finally

rm -f  /build/smeserver/repo/testing/$VER
pushd /build/smeserver/repo/testing/