Difference between revisions of "Build an Official ISO"
Unnilennium (talk | contribs) |
Unnilennium (talk | contribs) |
||
| Line 456: | Line 456: | ||
====OR Refresh cdrom content==== | ====OR Refresh cdrom content==== | ||
If only refreshing the files, then remove the delete. | If only refreshing the files, then remove the delete. | ||
| + | cd ~/smeserver | ||
| + | cvs -z3 -d:pserver:anonymous@smeserver.cvs.sourceforge.net:/cvsroot/smeserver co -P cdrom.image | ||
rsync -a --exclude 'CVS/' --exclude 'isolinux/' ~/cdrom.image/sme9/ /build/smeserver/stage/9/x86_64/ | rsync -a --exclude 'CVS/' --exclude 'isolinux/' ~/cdrom.image/sme9/ /build/smeserver/stage/9/x86_64/ | ||
Revision as of 20:16, 27 April 2017
Introduction
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 http://bugs.contribs.org/show_bug.cgi?id=7675#c37
bugzilla:7931
Please read Bug #7931 regarding repodata and symlinks.
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 -d:pserver:anonymous@smeserver.cvs.sourceforge.net:/cvsroot/smeserver co -P builds_bin cvs -z3 -d:pserver:anonymous@smeserver.cvs.sourceforge.net:/cvsroot/smeserver co -P cdrom.image cvs -z3 -d:pserver:anonymous@smeserver.cvs.sourceforge.net:/cvsroot/smeserver 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 http://bugs.contribs.org/attachment.cgi?id=5145 and paste it in
sudo vim /usr/lib/python2.6/site-packages/mockbuild/plugins/iso_prepare.py
on centos 7
sudo vim /usr/lib/python2.7/site-packages/mockbuild/plugins/iso_prepare.py
then you will need to comment the two follwoing lines (32 and 33) if you build on a centos 7 box:
# for l in glob.glob("/dev/loop*"):
# buildroot.mounts.add(BindMountPoint(srcpath=l, bindpath=buildroot.make_chroot_path(l)))
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.
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
Eg
/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()
- 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'))
with
#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' ))
Eg:
sudo vim /etc/mock/smeserver-9-x86_64-iso.cfg
Local Only: Patch a Mock Plugin
There is also an update to /usr/lib/python2.6/site-packages/mockbuild/mounts.py 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 http://bugs.contribs.org/show_bug.cgi?id=7675#c61
save as mounts.py.20150626.daniel.berteaud.patch see http://bugs.contribs.org/attachment.cgi?id=5146
--- /usr/lib/python2.6/site-packages/mockbuild/mounts.py 2015-06-04 13:34:04.000000000 +0200
+++ mounts.py 2015-06-26 18:05:53.924416540 +0200
@@ -76,6 +76,9 @@
@traceLog()
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 @@
m.umount()
@traceLog()
+ 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/mounts.py < mounts.py.20150626.daniel.berteaud.patch
save as mount.py.20150626.daniel.berteaud.patch see http://bugs.contribs.org/attachment.cgi?id=5147
--- /usr/lib/python2.6/site-packages/mockbuild/plugins/mount.py 2015-06-04 13:34:04.000000000 +0200
+++ mount.py 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),
filetype=vfstype,
device=device,
options=mount_opts))
@traceLog()
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/mount.py < mount.py.20150626.daniel.berteaud.patch
Preparation of a new Major Release
this part is a work in progress and might help for SME 11
Check how to tweak Anaconda
TODO
Update isolinux content
TODO
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 -d:ext:smeserver.cvs.sourceforge.net:/cvsroot/smeserver 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
wget http://mirror.canada.pialasse.com/releases/testing/10/smeos/x86_64/RPM-GPG-KEY-koozali
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:
smetest->smeupdates-testing->smeupdates
If an RPM is only needed for a new ISO and never needed as an update (before the ISO is released) :
/mirrors->smeupdates-testing->smeos
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
Server-Manager translations
Check translations from https://translate.koozali.org/patches/ 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 https://translate.koozali.org/anaconda/
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 -A.mo -P ~/anaconda-po https://translate.koozali.org/anaconda/
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 -A.mo -P ~/anaconda-po/sme9 https://translate.koozali.org/anaconda/sme9/
Check if installer needs re-building
Check Anaconda version
Check which anaconda was used upstream, (eg http://vault.centos.org/5.11/os/SRPMS/ & http://vault.centos.org/6.6/os/Source/SPackages/) 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.
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
[Main] Product=Koozali SME Server Version=10alpha2 BugURL=https://bugs.koozali.org IsFinal=False UUID=alpha2.x86_64 [Compose] Lorax=19.6.66-1
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 http://bugs.contribs.org/ \
--output $(pwd)/$distarch/ \
/build/smeserver/repo/$distrel/smeextras/$distarch/ \
$(pwd)/$distarch/
/bin/sed -i -e "s|packagedir =.*|packagedir = Packages|" $(pwd)/$distarch/.treeinfo
Prepare SME Server 10
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.
VER=10 VERSION=$VER.0.alpha3 VERPREV=$VER.0.alpha2
mkdir -p /build/smeserver/stage/$VERSION/{SRPMS,x86_64}
cd /build/smeserver/stage/
rm -f $VER
ln -s $VERSION $VER
cd /build/smeserver/stage/extra/images/$VER/product/
make any needed modification in the product image. then create the file and put it in place
find . | cpio -c -o | gzip -9cv > ../product.img; cd .. cp product.img /build/smeserver/stage/$VER/x86_64/images/
Local Only
mkdir -p /build/smeserver/stage/extra/isolinux/
Create cdrom content
When starting from fresh rsync can copy cdrom.image content, it also generates the folder tree.
Also note that the isolinux content goes into a temporary directory, /build/smeserver/stage/extra/isolinux/
rsync -a --delete --delete-excluded --exclude 'CVS/' --exclude 'isolinux/' ~/cdrom.image/sme10/ /build/smeserver/stage/10/x86_64/ rsync -a --delete --delete-excluded --exclude 'CVS/' ~/cdrom.image/sme10/isolinux/ /build/smeserver/stage/extra/isolinux/10/
OR Refresh cdrom content
If only refreshing the files, then remove the delete.
rsync -a --exclude 'CVS/' --exclude 'isolinux/' ~/cdrom.image/sme10/ /build/smeserver/stage/10/x86_64/ rsync -a --exclude 'CVS/' ~/cdrom.image/sme10/isolinux/ /build/smeserver/stage/extra/isolinux/10/
Create the remaining folders
- x86_64
cd /build/smeserver/stage/10/x86_64 ln -s Packages/ SME 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/10/x86_64 mkdir -p /build/smeserver/stage/iso/10/source
Copy anaconda translations
Anaconda translations need copying to /updates/po from ~/anaconda-po
cp -R ~/anaconda-po/translate.koozali.org/anaconda/sme10/* /build/smeserver/stage/10/i386/updates/po/
Copy anaconda content
See ~/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-21.48.22.56
cd ~/smeserver/rpms/anaconda/sme10/ make prep cd ~/smeserver/rpms/anaconda/sme10/anaconda-21.48.22.56
this does not work and need to be updated.
cp -R storage /build/smeserver/stage/10/x86_64/updates/ cp -R textw/*.py /build/smeserver/stage/10/x86_64/updates/textw cp -R iw/*.py /build/smeserver/stage/10/x86_64/updates/iw cp *.py /build/smeserver/stage/10/x86_64/updates cp lang-table /build/smeserver/stage/10/x86_64/updates
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
Local Only
/build/smeserver/stage/bin/update_repos
Prepare SME Server 9
Local Only: Update local mirror as seen by the chroot
Local Only
rsync -av --delete --progress ~/smeserver/releases/9/ /build/smeserver/repo/9
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/9.2/{SRPMS,i386,x86_64}
cd /build/smeserver/stage/
rm -f 9
ln -s 9.2 9
Local Only
mkdir -p /build/smeserver/stage/extra/isolinux/
Create cdrom content
When starting from fresh rsync can copy cdrom.image content, it also generates the folder tree.
Also note that the isolinux content goes into a temporary directory, /build/smeserver/stage/extra/isolinux/
cd ~/smeserver cvs -z3 -d:pserver:anonymous@smeserver.cvs.sourceforge.net:/cvsroot/smeserver co -P cdrom.image
rsync -a --delete --delete-excluded --exclude 'CVS/' --exclude 'isolinux/' ~/cdrom.image/sme9/ /build/smeserver/stage/9/x86_64/ rsync -a --delete --delete-excluded --exclude 'CVS/' --exclude 'isolinux/' ~/cdrom.image/sme9/ /build/smeserver/stage/9/i386/ rsync -a --delete --delete-excluded --exclude 'CVS/' ~/cdrom.image/sme9/isolinux/ /build/smeserver/stage/extra/isolinux/9/
OR Refresh cdrom content
If only refreshing the files, then remove the delete.
cd ~/smeserver cvs -z3 -d:pserver:anonymous@smeserver.cvs.sourceforge.net:/cvsroot/smeserver co -P cdrom.image
rsync -a --exclude 'CVS/' --exclude 'isolinux/' ~/cdrom.image/sme9/ /build/smeserver/stage/9/x86_64/ rsync -a --exclude 'CVS/' --exclude 'isolinux/' ~/cdrom.image/sme9/ /build/smeserver/stage/9/i386/ rsync -a --exclude 'CVS/' ~/cdrom.image/sme9/isolinux/ /build/smeserver/stage/extra/isolinux/9/
Create the remaining folders
- i386
cd /build/smeserver/stage/9/i386 ln -s Packages/ SME mkdir -p /build/smeserver/stage/9/i386/repodata/ mkdir -p /build/smeserver/stage/9/i386/updates/po mkdir -p /build/smeserver/stage/9/i386/updates/textw mkdir -p /build/smeserver/stage/9/i386/updates/iw mkdir -p /build/smeserver/stage/9/i386/updates/storage/devicelibs
- x86_64
cd /build/smeserver/stage/9/x86_64 ln -s Packages/ SME mkdir -p /build/smeserver/stage/9/x86_64/repodata/ mkdir -p /build/smeserver/stage/9/x86_64/updates/po mkdir -p /build/smeserver/stage/9/x86_64/updates/textw mkdir -p /build/smeserver/stage/9/x86_64/updates/iw mkdir -p /build/smeserver/stage/9/x86_64/updates/storage/devicelibs
- other directories
mkdir -p /build/smeserver/stage/iso/9/i386 mkdir -p /build/smeserver/stage/iso/9/x86_64 mkdir -p /build/smeserver/stage/iso/9/source
Copy anaconda translations
Anaconda translations need copying to /updates/po from ~/anaconda-po
cp -R ~/anaconda-po/translate.koozali.org/anaconda/sme9/* /build/smeserver/stage/9/i386/updates/po/ cp -R ~/anaconda-po/translate.koozali.org/anaconda/sme9/* /build/smeserver/stage/9/x86_64/updates/po/
Copy anaconda content
See ~/cdrom.image/sme9/updates/README.txt for details of what to copy. The patched anaconda files from ~/smeserver/rpms/anaconda/sme9 will go to updates directory. The exact directory depends on the anaconda version, eg ~/smeserver/rpms/anaconda/sme9/anaconda-13.21.254
cd ~/smeserver/rpms/anaconda/sme9/ make prep cd ~/smeserver/rpms/anaconda/sme9/anaconda-13.21.254 cp -R storage /build/smeserver/stage/9/i386/updates/ cp -R textw/*.py /build/smeserver/stage/9/i386/updates/textw cp -R iw/*.py /build/smeserver/stage/9/i386/updates/iw cp *.py /build/smeserver/stage/9/i386/updates cp lang-table /build/smeserver/stage/9/i386/updates
cp -R storage /build/smeserver/stage/9/x86_64/updates/ cp -R textw/*.py /build/smeserver/stage/9/x86_64/updates/textw cp -R iw/*.py /build/smeserver/stage/9/x86_64/updates/iw cp *.py /build/smeserver/stage/9/x86_64/updates cp lang-table /build/smeserver/stage/9/x86_64/updates
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
Local Only
/build/smeserver/stage/bin/update_repos
Build & Release SME Server 10
VER=10 VERSION=$VER.0.alpha2 VERPREV=$VER.0.alpha1
You can find logs of the related scripts build_ISO and build_installer
If something goes wrong, please verify first
/build/smeserver/stage/$VER/build_installer.x86_64
and after if you have no errors
/build/smeserver/stage/$VER/build_ISO.x86_64
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 pushd /build/smeserver/stage/$VER/x86_64/ ln -s Packages SME popd
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 pushd /build/smeserver/stage/$VER/x86_64/ ln -s Packages SME popd
Build & Release SME Server 9
You can find logs of the related scripts build_ISO and build_installer
If something goes wrong, please verify first
/build/smeserver/stage/9/build_installer.i386
or
/build/smeserver/stage/9/build_installer.x86_64
and after if you have no errors
/build/smeserver/stage/9/build_ISO.i386
or
/build/smeserver/stage/9/build_ISO.x86_64
Build SME Server 9 32 bit ISO
as releases on builder7
rm -f /build/smeserver/stage/9/i386/SME /usr/bin/mock -r smeserver-9-i386-iso --init /usr/bin/mock -r smeserver-9-i386-iso --mount --cwd /build/smeserver/stage/9 --unpriv --chroot /build/smeserver/stage/bin/build_installer /usr/bin/mock -r smeserver-9-i386-iso --mount --cwd /build/smeserver/stage/9 --unpriv --chroot /build/smeserver/stage/bin/build_ISO pushd /build/smeserver/stage/9/i386/ ln -s Packages SME popd
local only
rm -f /build/smeserver/stage/9/i386/SME mock -r smeserver-9-i386-iso --init mock -r smeserver-9-i386-iso --mount --cwd /build/smeserver/stage/9 --unpriv --chroot /build/smeserver/stage/bin/build_installer sudo chmod -R a+w /build/smeserver/stage mock -r smeserver-9-i386-iso --mount --cwd /build/smeserver/stage/9 --unpriv --chroot /build/smeserver/stage/bin/build_ISO pushd /build/smeserver/stage/9/i386/ ln -s Packages SME popd
Build SME Server 9 64 bit ISO
rm -f /build/smeserver/stage/9/x86_64/SME /usr/bin/mock -r smeserver-9-x86_64-iso --init /usr/bin/mock -r smeserver-9-x86_64-iso --mount --cwd /build/smeserver/stage/9 --unpriv --chroot /build/smeserver/stage/bin/build_installer /usr/bin/mock -r smeserver-9-x86_64-iso --mount --cwd /build/smeserver/stage/9 --unpriv --chroot /build/smeserver/stage/bin/build_ISO pushd /build/smeserver/stage/9/x86_64/ ln -s Packages SME popd
local only
rm -f /build/smeserver/stage/9/x86_64/SME mock -r smeserver-9-x86_64-iso --init mock -r smeserver-9-x86_64-iso --mount --cwd /build/smeserver/stage/9 --unpriv --chroot /build/smeserver/stage/bin/build_installer sudo chmod -R a+w /build/smeserver/stage mock -r smeserver-9-x86_64-iso --mount --cwd /build/smeserver/stage/9 --unpriv --chroot /build/smeserver/stage/bin/build_ISO pushd /build/smeserver/stage/9/x86_64/ ln -s Packages SME popd
Where are My F... ISO
ls /build/smeserver/stage/iso/8/ i386 source x86_64
and
ls /build/smeserver/stage/iso/9/ i386 source x86_64
or
ls /build/smeserver/stage/iso/10/ source x86_64
Developer Access Needed
From this point a developer access to the buildsys and the main repo is Needed, sorry guys. Has to be done from buildsrv
SME10
VER=10 VERSION=$VER.0.alpha2 VERPREV=$VER.0.alpha1
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:
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/ ln -s $VERSION $VER popd
SME9
Prepare directory structure for SME9 release
VER=9 VERSION=$VER.2.rc2 VERPREV=$VER.2.rc1 VERFINAL=$VER.2 VERACT=`echo "$VERFINAL - .1"|bc`
SME 9.x test releases will go to /build/smeserver/repo/testing/9. Check that the link points to the correct testing release. Note when uploading Jigdos the ‘9’ link will not be pointing to the new directory.
mkdir -p /build/smeserver/repo/testing/$VERSION/iso/i386/ 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/ mkdir -p /build/smeserver/repo/testing/$VERSION/smeos/i386/
cd /build/smeserver/repo/testing/ unlink /build/smeserver/repo/testing/$VER ln -s $VERSION /build/smeserver/repo/testing/$VER
Copy SME Server 9 64 bit Jigdo to mirror
/bin/cp -a /build/smeserver/stage/iso/9/x86_64/smeserver-$VERSION-x86_64.jigdo /build/smeserver/repo/testing/$VERSION/iso/x86_64/ /bin/cp -a /build/smeserver/stage/iso/9/x86_64/smeserver-$VERSION-x86_64.template /build/smeserver/repo/testing/$VERSION/iso/x86_64/ rsync -a --delete /build/smeserver/stage/9/x86_64/ /build/smeserver/repo/testing/$VERSION/smeos/x86_64/
Copy SME Server 9 32 bit Jigdo to mirror
/bin/cp -a /build/smeserver/stage/iso/9/i386/smeserver-$VERSION-i386.jigdo /build/smeserver/repo/testing/$VERSION/iso/i386/ /bin/cp -a /build/smeserver/stage/iso/9/i386/smeserver-$VERSION-i386.template /build/smeserver/repo/testing/$VERSION/iso/i386/ rsync -a --delete /build/smeserver/stage/9/i386/ /build/smeserver/repo/testing/$VERSION/smeos/i386
Copy SME Server 9 SRPMS Jigdo to mirror
/bin/cp -a /build/smeserver/stage/iso/9/source/smeserver-$VERSION-SRPMS.jigdo /build/smeserver/repo/testing/$VERSION/iso/source/ /bin/cp -a /build/smeserver/stage/iso/9/source/smeserver-$VERSION-SRPMS.template /build/smeserver/repo/testing/$VERSION/iso/source/ rsync -a --delete /build/smeserver/stage/9/SRPMS/ /build/smeserver/repo/testing/$VERSION/smeos/SRPMS
Copy SME Server 9 ISOs to mirror
rsync -a --delete /build/smeserver/stage/iso/9/ /build/smeserver/repo/testing/$VERSION/iso
Hard links
As an example how to create the hard links:
cp -lr /build/smeserver/repo/testing/$VERSION/smeos/* /build/smeserver/repo/testing/$VERFINAL/smeos/ mkdir -p /build/smeserver/repo/testing/$VERFINAL/smeaddons/ mkdir -p /build/smeserver/repo/testing/$VERFINAL/smecontribs/ mkdir -p /build/smeserver/repo/testing/$VERFINAL/smedev/ mkdir -p /build/smeserver/repo/testing/$VERFINAL/smeextras/ mkdir -p /build/smeserver/repo/testing/$VERFINAL/smetest/ mkdir -p /build/smeserver/repo/testing/$VERFINAL/smeupdates/ mkdir -p /build/smeserver/repo/testing/$VERFINAL/smeupdates-testing/
cp -lr /build/smeserver/repo/testing/$VERSION/smecontribs/* /build/smeserver/repo/testing/$VERFINAL/smecontribs/ cp -lr /build/smeserver/repo/testing/$VERSION/smedev/* /build/smeserver/repo/testing/$VERFINAL/smedev/ cp -lr /build/smeserver/repo/testing/$VERSION/smeextras/* /build/smeserver/repo/testing/$VERFINAL/smeextras/ cp -lr /build/smeserver/repo/testing/$VERSION/smetest/* /build/smeserver/repo/testing/$VERFINAL/smetest/ cp -lr /build/smeserver/repo/testing/$VERSION/smeupdates/* /build/smeserver/repo/testing/$VERFINAL/smeupdates/ cp -lr /build/smeserver/repo/testing/$VERSION/smeupdates-testing/* /build/smeserver/repo/testing/$VERFINAL/smeupdates-testing/ cp -lr /build/smeserver/repo/testing/$VERSION/smeaddons/* /build/smeserver/repo/testing/$VERFINAL/smeaddons/
alternatively the second part could be starting 9.1 $VERFINAL as an example from 9.0 $VERACT
cp -lr /build/smeserver/repo/$VERACT/smecontribs/* /build/smeserver/repo/testing/$VERFINAL/smecontribs/ cp -lr /build/smeserver/repo/$VERACT/smedev/* /build/smeserver/repo/testing/$VERFINAL/smedev/ cp -lr /build/smeserver/repo/$VERACT/smeextras/* /build/smeserver/repo/testing/$VERFINAL/smeextras/ cp -lr /build/smeserver/repo/$VERACT/smetest/* /build/smeserver/repo/testing/$VERFINAL/smetest/ cp -lr /build/smeserver/repo/$VERACT/smeupdates/* /build/smeserver/repo/testing/$VERFINAL/smeupdates/ cp -lr /build/smeserver/repo/$VERACT/smeupdates-testing/* /build/smeserver/repo/testing/$VERFINAL/smeupdates-testing/ cp -lr /build/smeserver/repo/$VERACT/smeaddons/* /build/smeserver/repo/testing/$VERFINAL/smeaddons/
then you can mv from testing to main folder
