Difference between revisions of "Live GIS Build"

From OSGeo
Jump to navigation Jump to search
m (Modified Lubuntu OS version (18.04 => 22.04) and architecture (i386 => amd64))
 
(249 intermediate revisions by 9 users not shown)
Line 1: Line 1:
−
=About=
+
= Getting started =
  
−
[http://gisvm.com/ GISVM] is an Xubuntu based Virtual Machine which has been installed with a suite of the best Open Source Geospatial software. It is also used to build [http://www.arramagong.com/Arramagong.html Arramagong], the Linux based Live DVD.
+
The first thing you will have to do is check-out the latest build scripts using either one of these two Git servers:
 +
git clone <nowiki>https://git.osgeo.org/gitea/osgeolive/OSGeoLive.git</nowiki>
  
−
=How to add your project or data to GISVM / Arramagong=
+
git clone <nowiki>https://github.com/OSGeo/OSGeoLive.git</nowiki>
  
−
All that's required to add your favorite package into GISVM is to:
+
* see [[Live_GIS_Disc#Git_migration|here]] for more details.
  
−
* '''Optional''': Subscribe to the [http://lists.osgeo.org/mailman/listinfo/live-demo Live Demo] email list to discuss issues.
+
=How to add your project to OSGeo Live=
  
−
* '''Optional''': Install the latest Arramamgong / GIS virtual machine as per: [[Live_GIS_Disc_Quick_Start]].
+
* [[Live_GIS_Add_Project|Instructions for adding new projects]]
−
* write a shell script which installs and configures your stable package into the current GISVM virtual machine (which will usually be the same as installing on Xubuntu or Ubuntu).
 
  
−
* add the script to subversion, in https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/bin/ , as per http://wiki.osgeo.org/wiki/Live_GIS_Disc#Subversion
+
= Creating a fresh Virtual Machine to use as a build host (Optional) =
−
: If you are unfamiliar with subversion then you can send the script to the [[Live_GIS_Disc#Communication|OSGeo live-demo mailing list]] ''as an attachment'' and we'll see that it makes it in.
+
Refer to: [[Live_GIS_Virtual_Machine]].
  
−
* Notify the GISVM team to test your script, and will ensure to reference your script from ''main.sh''.
+
= Build the Live DVD ISO image =
  
−
== Example scripts ==
 
  
−
You can see example scripts at: https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/bin/
+
== Build ISO ==
  
−
The script may be as simple as:
+
This section describes the new method for building OSGeoLive as described in [https://help.ubuntu.com/community/LiveCDCustomization official ubuntu wiki]. This section is self-contained and there is no need to perform any of the procedures described above.
  
−
[https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/bin/install_mapserver.sh install_mapserver.sh], which just "apt-get install mapserver"
+
All you need is a running Ubuntu/Xubuntu/Kubuntu/Lubuntu installation (even within a virtual machine as long as it has ~20GB free disk space). All needed to be done are the following steps under a "user" account:
  
−
Projects that haven't been packaged yet are slightly more complicated:
+
* Bootstrap the host operating system. If you use the system to build more than once, then this must be done only for the first build
 +
host$ cd /tmp
 +
host$ wget https://github.com/OSGeo/OSGeoLive/raw/master/bin/bootstrap.sh
 +
host$ chmod a+x bootstrap.sh
 +
host$ sudo ./bootstrap.sh
 +
This will install Git and the install scripts, and create a link to them from your home directory.
  
−
The Udig package is a good example: [https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/bin/install_udig.sh install_udig.sh]
+
* Set the Version Number and Changes
 +
  Update https://github.com/OSGeo/OSGeoLive/blob/master/VERSION.txt with the current version number.
  
−
*3rd Party Repositories - Create an <app>.list file with your repository in sources.list.d/ in the svn, in your script copy the file to the local machine like
+
  Update https://github.com/OSGeo/OSGeoLive/blob/master/CHANGES.txt with changes since the last release.
−
wget https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/sources.list.d/qgis.list --output-document=/etc/apt/sources.list.d/qgis.list
+
This list can be a summary of the [https://github.com/OSGeo/OSGeoLive/commits/master revision log] between releases
−
don't forget to add the repository key like so
+
Commit the changes to Git through a Pull Request right before a release build.
−
apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 68436DDF
 
  
−
== Packaging conventions ==
+
* Execute the build script:
 +
host$ cd ~/gisvm/bin
 +
host$ sudo ./build_chroot.sh amd64 release master OSGeo 2>&1 | tee /var/log/osgeolive/chroot-build.log
  
−
# Assume the script is to be executed as root.
+
* Compress the logs:
−
# It is ok initially to have manual steps in your script. When this happens, include:
+
  host$ cd ~/livecdtmp
−
  # FIXME
+
  host$ tar czf version-log.tar.gz -C /var/log osgeolive
−
  echo "install_<package>.sh FIXME: <describe manual step>
 
−
# Where appropriate, create an icon on the desktop which loads the application. (Todo: How do we do this?)
 
−
# Create an icon in the the Applications pull down list. (Todo: How do we do this?)
 
−
# If the application is launched from the browser, then include the application in Firefox bookmarks.
 
  
−
= Build Drivers =
+
* After the completion of the above script the new iso file is located in ~/livecdtmp along with the build logs. In case you wish to rerun the build process, do not remove or move the lubuntu official iso located in this folder to skip downloading it again.
−
== Which version? ==
 
−
The criteria used to select applications for GISVM is as follows:
 
  
−
# Priority goes to Ubuntu packaged software first, then Debian packaged software! This facilitates easy and reliable maintenance and update. Users will benefit from it. Programmers are encouraged to move their software into [http://wiki.debian.org/DebianGis DebianGIS] or [https://wiki.ubuntu.com/UbuntuGIS UbuntuGIS] repositories.
+
* It is required to reboot your host machine after build is completed
−
# Stable, always! GISVM users are mainly starters. So they obviously are better with stable software. They have enough problems already and will gladly be happier without software bugs.
 
  
−
For people who want the latest version, they can create an alternative upgrade script.
+
* Once the ISO is complete copy it out to a server (a local server is fastest)
 +
scp ~/livecdtmp/osgeolive-mini-8.0.iso user@server.org:destination/path/
 +
scp ~/livecdtmp/osgeolive-mini-8.0-log.tar.gz user@server.org:destination/path/
  
−
== Low Memory ==
+
* And/OR wget or scp the file to the upload.osgeo.org server (Note wget is much faster if you have a good webserver to host from)
−
Both Virtual Machines, and a LiveDVD images are likely to be constrained by limited memory. So to reduce memory usage. Disk image size is not of major concern, as we can just distribute less data.
 
  
−
The following principles should be followed.
+
=== Build Full ISO from Mini ISO ===
−
# Do not start applications upon power up. (Ie, don't start deamons, allow users to start them instead).
 
−
# Set up examples which, by default, don't depend on other applications. Less applications open, means less memory. Ie, Have GeoServer access a shapefile instead of PostGIS.
 
−
# Try to avoid scenarios which write data to disk, as disk space in the Live DVD is stored in RAM, and is not cleared afterward.
 
  
−
= Directory Structure =
+
Any mini iso file resulting from the procedure below can be turned into full iso, which is identical but adds the Windows and Mac software installers. Note that the resulting file may be bigger than a DVD. In that case the list of included applications in the load_mac_installers.sh need to be edited to exclude additional applications.
  
−
# /tmp Temporary files (e.g., downloaded archives) go into /tmp. Please create a separate folder for your project.
+
The standard current rules used to pick applications:
−
# /usr/lib application are usually installed into /usr/lib
+
* Desktop Applications
−
# /usr/bin things that get executed by the user such as startup scripts or links to them should go into /usr/bin
+
* OSGeo projects and Incubated projects
−
# /etc/init.d startup/shutdown scripts for services (e.g., postgres, apache, tomcat) are stored in /etc/init.d
 
−
# /usr/local/share sample data and documentation goes into /usr/local/share
 
−
# /etc config files are stored in /etc
 
−
# /home/user user specific config files or working directories can go into <tt>/home/user/</tt>. However, keep files in /home/user as small as possible as this folder is loaded into memory in the Live DVD. Symlinks into /usr/local can be useful here.
 
  
−
= Mounting as Existing Image =
+
sudo ./build_full_iso.sh /full/path/to/osgeo-live-mini-8.0.iso 2>&1 | tee ~/build_full_iso.log
−
For the purposes of faster dissemination of updates to the Live image via something like rsync you can mount an image file.
 
−
Make sure you turn off the virtual machine before you attempt to mount it, and that you unmount it before you attempt to run the vm again.
 
  
−
== Using VMWare ==
+
== How to do development / debugging with the current build method ==
−
This method assumes you have vmware server installed, the key is that the vmware-mount script is on your system somewhere.
 
−
This instructions use /space/virtual as the vmware installation folder and /space/virtual/machines as the location of the disk images.
 
−
For more information see the [http://www.vmware.com/pdf/VMwareDiskMount.pdf VMware mounting guide]
 
−
*If it complains about not finding libdir/lib/libcrypto.so.0.9.8/libcrypto.so.0.9.8
 
−
*It's because it's looking for it in your vmware bin/libdir which doesn't exist so symlink
 
−
sudo ln -s /space/virtual/lib/vmware/ libdir
 
−
*Temporarily move your .vmx file out of the directory
 
−
sudo ./vmware-mount -p /space/virtual/machines/gisvm20090828x.vmdk
 
−
*Should be partition 1
 
−
*Make a directory to mount to somewhere easy to find, in my case where I keep my vm images
 
−
mkdir /space/virtual/machines
 
−
*Mount it
 
−
sudo ./vmware-mount /space/virtual/machines/gisvm20090828x.vmdk 1 /space/virtual/machines/mountedimage
 
−
*Don't forget to umount when you're done
 
−
sudo ./vmware-mount -d /space/virtual/machines/mountedimage
 
  
−
== Using VirtualBox ==
+
We have created a debug build process so that projects can now easily create their own iso, including parts of the OSGeoLive (eg only one project) in order to test if the installer scripts work well under this new build method.
−
These instructions have not been tested yet, they require VirtualBox 2.0+
+
Here are the steps to debug/test your application:
−
http://forums.virtualbox.org/viewtopic.php?f=7&t=17574
 
  
−
= Creating a fresh Virtual Machine =
+
===One time steps===
−
== System Requirements ==
 
−
* RAM: You can only just get away with 1 Gig. 2 Gig is what you will require to avoid slowdowns due to memory swapping.
 
−
* About 10 Gig of spare hard disk.
 
  
−
== Install VMWare Server ==
+
You will need to create a pure Lubuntu Virtual Machine setup:
−
You will need [http://www.vmware.com/products/server/ VMWare server] which provides all the tools for configuring a VM, setting the disk size, compressing the image etc. VirtualBox doesn't seem to have the compression scripts required, and it doesn't seem to have a way to copy your image to VMWare.
 
  
−
If you are installing on linux, the installer will ask a series of questions. Answer the default for everything, except the default administrator. For this, you need to enter in your <user_id> for the local computer you are installing on.
+
* Download lubuntu-22.04-desktop-amd64.iso from [http://cdimage.ubuntu.com/lubuntu/releases/22.04/release/lubuntu-22.04-desktop-amd64.iso lubuntu web site].
 +
* Download and install VirtualBox.
 +
* Create a fresh VM installation of Lubuntu. You will need to create a virtual disk drive with at least 25 GB of space and allocate 768MB of RAM to the VM. During installation set the username to "user" and hostname to "osgeolive". DO NOT install system updates during lubuntu installation or after the installation is done. At this moment we work with the default kernel included in lubuntu.
 +
* After the VM is done, login as "user" and open a terminal.
 +
* Bootstrap the VM:
 +
osgeolive$ cd /tmp
 +
osgeolive$ wget https://github.com/OSGeo/OSGeoLive/raw/master/bin/bootstrap.sh
 +
osgeolive$ chmod a+x bootstrap.sh
 +
osgeolive$ sudo ./bootstrap.sh
  
−
== Create an Xubuntu Virtual Machine ==
+
This will install Git, the install scripts, and create a link to them from your home directory.
−
If you already have an Xubuntu (or similar) Virtual Machine, you can skip this step.
 
  
−
'''Side note:''' vmbuilder is reported to be a good way to create an Ubuntu image. I haven't tried it, and haven't worked out if it can create the smaller Xubuntu image. (Please update this wiki if you try it). On ubuntu:
+
===Steps to create the build (repeat as much as needed)===
−
apt-get install python-vm-builder
 
  
−
Otherwise, run VMWare Server, and create an image.
+
* Make changes to your project's installation script and commit to Git.
  
−
Download the latest [http://www.xubuntu.org/ Xubuntu ISO]. Copy to the Virtual Machine directory:
+
* Update the git code:
 +
osgeolive$ cd ~/gisvm
 +
osgeolive$ git pull origin master
  
−
wget http://mirror.internode.on.net/pub/ubuntu/xubuntu/9.04/release/xubuntu-9.04-desktop-i386.iso
+
* Open file inchroot.sh with an editor and comment out all scripts you do not need for your test.  
−
  mv xubuntu-9.04-desktop-i386.iso "/var/lib/vmware/Virtual Machines/"
+
osgeolive$ cd ~/gisvm/bin
 +
  osgeolive$ vi inchroot.sh
  
−
Run vmware, which opens up a browser based User Interface.
+
* Always leave un-commented the following scripts: setup.sh, install_services.sh, install_mysql.sh, install_java.sh, install_apache2.sh, install_tomcat6.sh, install_desktop.sh and setdown.sh.  
−
vmware
 
  
−
Create a new Virtual Machine with:
+
* Save your changes and execute the build:
−
* RAM = 512 Gig (we might want to experiment with less)
+
osgeolive$ cd ~/gisvm/bin
−
* Hard Disk = 20 Gig (you probably only need 8 Gig or so, but it is a pain to increase later, and can't be done from VMWare Player)
+
osgeolive$ sudo ./build_chroot.sh amd64 2>&1 | tee /var/log/osgeolive/chroot-build.log
−
* Mount the XUbuntu ISO image for the disk drive
 
  
−
Run the Virtual Machine, which will boot from the Xubuntu CD. Select to install Xubuntu, using defaults, plus:
+
* After a while the iso will be created in ~livecdtmp/
−
* Username = user
 
−
* Password = user
 
  
−
Install vmware tools, as per: http://www.ubuntugeek.com/howto-install-vmware-tools-in-ubuntu.html
+
* Do not delete the file ~/livecdtmp/lubuntu-22.04-desktop-amd64.iso as it will be needed for next build (saves time not to download again)
−
sudo apt-get install build-essential linux-headers-`uname -r` psmisc
 
−
tar xvfz VMwareTools-7.8.6-185404.tar.gz
 
−
cd vmware-tools-distrib/
 
−
sudo ./vmware-install.pl
 
−
# default reply to all questions
 
  
−
You should now have a XUbuntu Virtual Machine image in /var/lib/vmware/Virtual Machines/ . It would be a good idea to save a copy of this machine somewhere, so you can use it again.
+
* Logs are created at /var/log/osgeolive/chroot-build.log
  
−
== Bootstrap the Live DVD ==
+
* Copy the iso and test
−
* Start the Xubuntu Virtual Machine
 
−
* Open a terminal
 
−
* Copy the bootstrap script into your home directory and execute it
 
−
cd ~
 
−
wget https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/bin/bootstrap.sh
 
−
sudo ./bootstrap.sh
 
−
* This will install subversion, and the install scripts, and create a link to them from your home directory.
 
−
* Optional: If you have run through this process a number of times, you might be smart enough to have saved a local copy of the tmp/ directory. You can save time and bandwidth by copying the tmp/ contents onto the live DVD:
 
−
rsync -avz username@hostname.org:/path_to_tmp_dir/ /tmp/
 
−
* cd to the install scripts directory, and run the main.sh installer.
 
−
cd ~/gisvm/trunk/bin
 
−
sudo ./main.sh
 
−
* Answer prompts as they come up, there are a few at the start. Wait for a few hours while everything is downloaded and installed.
 
−
* When finished, and before you shutdown your virtual machine, copy the download directories in /tmp to your local computer. (This is to save you re-downloading the files if you are to run through the process again.)
 
−
* The Live DVD should now be ready to test.
 
  
−
== Package the Live DVD ==
+
= Build the Live DVD VM image =
  
−
Compress the image:
+
== Create the VM ==
−
sudo vmware-toolbox
+
 
−
# select "shrink" to shrink the image. This option comes with vmware server, but not with vmware player.
+
The OSGeoLive Virtual Machine creation process is now exactly similar to a plain Lubuntu VM installation.
 +
Use the mini iso file that was created from the previous chapter.  
 +
Instructions can be found [[Live_GIS_Virtual_Machine]]
 +
 
 +
== Package the VM ==
 +
 
 +
From within the VM, fill empty space with zeros in order to be able to shrink the virtual disk files:
 +
 
 +
osgeolive$ sudo ~/gisvm/bin/zerofill.sh
 +
 
 +
Shrink the virtual machine:
 +
 
 +
host$ VBoxManage modifyhd osgeolive.vdi --compact
 +
 
 +
Convert to vmdk format (more widely compatible):
 
   
 
   
 +
host$ VBoxManage clonehd osgeolive.vdi osgeolive-14.0-amd64.vmdk --format VMDK
 +
OR with a recent version of QEMU
 +
host$ qemu-img convert -f vdi -o compat6 -O vmdk osgeolive.vdi osgeolive-14.0-amd64.vmdk
 +
 
Zip the image up:
 
Zip the image up:
−
  7z a -mx=9 ArramagongGISVM2009alpha4.7z ArramagongGISVM2009alpha4/
 
  
−
If the image is greater than 2 Gig, then you also need to split the image. The OSGeo download server isn't configured to accept files of a greater size.
+
host$ 7z a -mx=9 osgeolive-14.0-amd64.vmdk.7z osgeolive-14.0-amd64.vmdk
−
  split -b 1500M ArramagongGISVM2009alpha4.7z ArramagongGISVM2009alpha4.7z
+
 
 +
Create the md5sum checksums, so which can be used to confirm that the images have been downloaded correctly:
 +
host$ md5sum *.7z*
 +
 
 +
= Upload the Release =
 +
 
 +
== Upload to sourceforge ==
 +
As of 6.0 the official releases are hosted on sourceforge. To upload you need a sourceforge account and permissions to the osgeo-live project upload.
 +
 
 +
  rsync -e ssh osgeolive-14.0-amd64.iso username,osgeo-live@frs.sourceforge.net:/home/pfs/project/o/os/osgeo-live/14.0/
  
 
== Upload to the OSGeo Server ==
 
== Upload to the OSGeo Server ==
 +
 +
host$ scp -pr osgeolive-gisvm-2.0-alpha5 username@upload.osgeo.org:/osgeo/download/livedvd/
 +
 +
Update the index.html file at: https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/download/index.html
 +
 +
Check the result at: http://download.osgeo.org/livedvd
 +
 +
== Creating a torrent file ==
 +
'''Ibiblio has offered torrent hosting, this section needs to include who to contact/how to setup'''
 +
Several tools exist for creating torrents. Below are the key settings you need.
 +
 +
Deluge with the torrent creator plugin has been tested.
 +
* Make sure you have a copy of the file you want to create a torrent for. Mounted remote drives may work.
 +
* Web Seed - URL to a web server that hosts the file, adds speed to the torrents especially at the start. (Most clients implement this now)
 +
* Tracker - There are 2 open and free trackers that have been tested, use one or the other as most clients do not handle multiple trackers yet.
 +
http://tracker.openbittorrent.com/announce
 +
udp://tracker.openbittorrent.com:80/announce
 +
OR
 +
http://tracker.publicbt.com:80/announce
 +
udp://tracker.publicbt.com:80/announce
 +
* Upload the .torrent file of your iso file for others to grab
 +
* Start the torrent on your machine or dedicated seeder, so that others have somewhere to start.
 +
* There is a possibility of seeding from osgeo machines but a Quality of Service (QoS) system would need to be in place to ensure it does not impact other services.
 +
 +
= SVN branches and tags =
 +
 +
=== Naming ===
 +
 +
* main development happens in "<tt>trunk</tt>" (aka HEAD)
 +
* a branch is split off before release time. Bug fixes (only) happen in it and updates like version 2.1 are tagged from it.
 +
: its name might be like "<tt>arramagong_2</tt>"
 +
* a tag is a snapshot of the svn at some point in time, aka a release name. It does not make sense to checkin fixes to one. They should ideally be set as read-only after creation to prevent this.
 +
: its name might be like "<tt>release_20090927_arramagong_2_0</tt>"
 +
 +
=== Creating ===
 +
 +
cd livedvd/gisvm/
 +
 +
svn copy trunk branches/arramagong_2
 +
svn commit branches/arramagong_2 -m "Splitting off branch for 2.x"
 +
 +
cd branches/arramagong_2/bin/
 +
# something like this, maybe need a for loop or xargs:
 +
sed -e 's+gisvm/trunk+gisvm/branches/arramagong_2+g' *.sh | less  # check
 +
sed -i -e 's+gisvm/trunk+gisvm/branches/arramagong_2+g' *.sh      # execute
 +
cd -
 +
 
 +
svn copy branches/arramagong_2 tags/release_20090927_arramagong_2_0_3
 +
svn commit tags/release_20090927_arramagong_2_0_3 -m "tag release 2.0.3"
 +
 +
=== Merging ===
 +
 +
To merge a change from <tt>trunk</tt> into a release branch use "<tt>svn&nbsp;merge</tt>", as follows: (in this example r2131 from trunk)
 +
 +
svn up branches/arramagong_2/
 +
cd branches/arramagong_2/
 +
 +
svn merge -c 2131 <nowiki>https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk</nowiki>
 +
svn diff
 +
svn commit -m "bugfix: bikeshed should be orange! (merge from trunk r2131)"
 +
 +
If you do this a lot you might make a little shell script. Here's one called svn_merge_livefromtrunk.sh:
 +
#!/bin/sh
 +
# Usage: svn_merge_livefromtrunk <rev number>
 +
svn merge -c $1 <nowiki>https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk</nowiki>
 +
 +
=== See also ===
 +
 +
* Many good hints can be found in the [https://trac.osgeo.org/grass/wiki/HowToSVN GRASS SVN-help wiki page].
  
 
[[Category: Live-demo]]
 
[[Category: Live-demo]]
 +
 +
 +
= Staging the new release =
 +
 +
== Website ==
 +
Log in to live.osgeo.org.
 +
cd /osgeo/osgeolive
 +
mkdir ''<versionnumber>''
 +
 +
From another machine (ususally adhoc) go to the root of the docs and do
 +
scp -r /osgeo/livedvd/www/docs/* live.osgeo.org:/osgeo/osgeolive/''<versionumber>''/
 +
 +
Once done check that it's all good:
 +
<nowiki>http://live.osgeo.org/archive/</nowiki>''versionnumber''
 +
 +
Assuming docs are ok, then update the current symlink:
 +
chmod -R g+w ''<versionnumber>''
 +
rm current
 +
ln -s ''<versionnumber>'' current
 +
 +
== Download mirror ==
 +
 +
Upload files to https://sourceforge.net/projects/osgeo-live/files/
 +
 +
Add a new folder for the release, go into it, then scp the file to SourceForge.
 +
* See  https://sourceforge.net/p/forge/documentation/Release%20Files%20for%20Download/#scp
 +
 +
Click the box to stage the files for 3 days to give time for the mirrors to populate.
 +
 +
Once the files are ready (no longer say "Pending...") and the download links and redirects from download.osgeo.org are tested & working, set the default download on the SourceForge site to either the full or mini ISO by clicking the "i" information button next to the file and "select all" for all platform types, then click the Save button.

Latest revision as of 08:02, 26 June 2022

Getting started

The first thing you will have to do is check-out the latest build scripts using either one of these two Git servers: 

git clone https://git.osgeo.org/gitea/osgeolive/OSGeoLive.git

git clone https://github.com/OSGeo/OSGeoLive.git
  • see here for more details.

How to add your project to OSGeo Live

Creating a fresh Virtual Machine to use as a build host (Optional)

Refer to: Live_GIS_Virtual_Machine.

Build the Live DVD ISO image

Build ISO

This section describes the new method for building OSGeoLive as described in official ubuntu wiki. This section is self-contained and there is no need to perform any of the procedures described above.

All you need is a running Ubuntu/Xubuntu/Kubuntu/Lubuntu installation (even within a virtual machine as long as it has ~20GB free disk space). All needed to be done are the following steps under a "user" account:

  • Bootstrap the host operating system. If you use the system to build more than once, then this must be done only for the first build
host$ cd /tmp
host$ wget https://github.com/OSGeo/OSGeoLive/raw/master/bin/bootstrap.sh
host$ chmod a+x bootstrap.sh
host$ sudo ./bootstrap.sh

This will install Git and the install scripts, and create a link to them from your home directory.

  • Set the Version Number and Changes
 Update https://github.com/OSGeo/OSGeoLive/blob/master/VERSION.txt with the current version number.

 Update https://github.com/OSGeo/OSGeoLive/blob/master/CHANGES.txt with changes since the last release.

This list can be a summary of the revision log between releases Commit the changes to Git through a Pull Request right before a release build.

  • Execute the build script:
host$ cd ~/gisvm/bin
host$ sudo ./build_chroot.sh amd64 release master OSGeo 2>&1 | tee /var/log/osgeolive/chroot-build.log
  • Compress the logs:
host$ cd ~/livecdtmp
host$ tar czf version-log.tar.gz -C /var/log osgeolive
  • After the completion of the above script the new iso file is located in ~/livecdtmp along with the build logs. In case you wish to rerun the build process, do not remove or move the lubuntu official iso located in this folder to skip downloading it again.
  • It is required to reboot your host machine after build is completed
  • Once the ISO is complete copy it out to a server (a local server is fastest)
scp ~/livecdtmp/osgeolive-mini-8.0.iso user@server.org:destination/path/
scp ~/livecdtmp/osgeolive-mini-8.0-log.tar.gz user@server.org:destination/path/
  • And/OR wget or scp the file to the upload.osgeo.org server (Note wget is much faster if you have a good webserver to host from)

Build Full ISO from Mini ISO

Any mini iso file resulting from the procedure below can be turned into full iso, which is identical but adds the Windows and Mac software installers. Note that the resulting file may be bigger than a DVD. In that case the list of included applications in the load_mac_installers.sh need to be edited to exclude additional applications.

The standard current rules used to pick applications:

  • Desktop Applications
  • OSGeo projects and Incubated projects
sudo ./build_full_iso.sh /full/path/to/osgeo-live-mini-8.0.iso 2>&1 | tee ~/build_full_iso.log

How to do development / debugging with the current build method

We have created a debug build process so that projects can now easily create their own iso, including parts of the OSGeoLive (eg only one project) in order to test if the installer scripts work well under this new build method. Here are the steps to debug/test your application:

One time steps

You will need to create a pure Lubuntu Virtual Machine setup:

  • Download lubuntu-22.04-desktop-amd64.iso from lubuntu web site.
  • Download and install VirtualBox.
  • Create a fresh VM installation of Lubuntu. You will need to create a virtual disk drive with at least 25 GB of space and allocate 768MB of RAM to the VM. During installation set the username to "user" and hostname to "osgeolive". DO NOT install system updates during lubuntu installation or after the installation is done. At this moment we work with the default kernel included in lubuntu.
  • After the VM is done, login as "user" and open a terminal.
  • Bootstrap the VM:
osgeolive$ cd /tmp
osgeolive$ wget https://github.com/OSGeo/OSGeoLive/raw/master/bin/bootstrap.sh
osgeolive$ chmod a+x bootstrap.sh
osgeolive$ sudo ./bootstrap.sh

This will install Git, the install scripts, and create a link to them from your home directory.

Steps to create the build (repeat as much as needed)

  • Make changes to your project's installation script and commit to Git.
  • Update the git code:
osgeolive$ cd ~/gisvm
osgeolive$ git pull origin master
  • Open file inchroot.sh with an editor and comment out all scripts you do not need for your test.
osgeolive$ cd ~/gisvm/bin
osgeolive$ vi inchroot.sh
  • Always leave un-commented the following scripts: setup.sh, install_services.sh, install_mysql.sh, install_java.sh, install_apache2.sh, install_tomcat6.sh, install_desktop.sh and setdown.sh.
  • Save your changes and execute the build:
osgeolive$ cd ~/gisvm/bin
osgeolive$ sudo ./build_chroot.sh amd64 2>&1 | tee /var/log/osgeolive/chroot-build.log
  • After a while the iso will be created in ~livecdtmp/
  • Do not delete the file ~/livecdtmp/lubuntu-22.04-desktop-amd64.iso as it will be needed for next build (saves time not to download again)
  • Logs are created at /var/log/osgeolive/chroot-build.log
  • Copy the iso and test

Build the Live DVD VM image

Create the VM

The OSGeoLive Virtual Machine creation process is now exactly similar to a plain Lubuntu VM installation. Use the mini iso file that was created from the previous chapter. Instructions can be found Live_GIS_Virtual_Machine

Package the VM

From within the VM, fill empty space with zeros in order to be able to shrink the virtual disk files: 

osgeolive$ sudo ~/gisvm/bin/zerofill.sh

Shrink the virtual machine: 

host$ VBoxManage modifyhd osgeolive.vdi --compact

Convert to vmdk format (more widely compatible): 

host$ VBoxManage clonehd osgeolive.vdi osgeolive-14.0-amd64.vmdk --format VMDK
OR with a recent version of QEMU
host$ qemu-img convert -f vdi -o compat6 -O vmdk osgeolive.vdi osgeolive-14.0-amd64.vmdk

Zip the image up: 

host$ 7z a -mx=9 osgeolive-14.0-amd64.vmdk.7z osgeolive-14.0-amd64.vmdk

Create the md5sum checksums, so which can be used to confirm that the images have been downloaded correctly: 

host$ md5sum *.7z*

Upload the Release

Upload to sourceforge

As of 6.0 the official releases are hosted on sourceforge. To upload you need a sourceforge account and permissions to the osgeo-live project upload. 

rsync -e ssh osgeolive-14.0-amd64.iso username,osgeo-live@frs.sourceforge.net:/home/pfs/project/o/os/osgeo-live/14.0/

Upload to the OSGeo Server

host$ scp -pr osgeolive-gisvm-2.0-alpha5 username@upload.osgeo.org:/osgeo/download/livedvd/

Update the index.html file at: https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/download/index.html

Check the result at: http://download.osgeo.org/livedvd

Creating a torrent file

Ibiblio has offered torrent hosting, this section needs to include who to contact/how to setup Several tools exist for creating torrents. Below are the key settings you need.

Deluge with the torrent creator plugin has been tested.

  • Make sure you have a copy of the file you want to create a torrent for. Mounted remote drives may work.
  • Web Seed - URL to a web server that hosts the file, adds speed to the torrents especially at the start. (Most clients implement this now)
  • Tracker - There are 2 open and free trackers that have been tested, use one or the other as most clients do not handle multiple trackers yet.
http://tracker.openbittorrent.com/announce
udp://tracker.openbittorrent.com:80/announce

OR 

http://tracker.publicbt.com:80/announce
udp://tracker.publicbt.com:80/announce
  • Upload the .torrent file of your iso file for others to grab
  • Start the torrent on your machine or dedicated seeder, so that others have somewhere to start.
  • There is a possibility of seeding from osgeo machines but a Quality of Service (QoS) system would need to be in place to ensure it does not impact other services.

SVN branches and tags

Naming

  • main development happens in "trunk" (aka HEAD)
  • a branch is split off before release time. Bug fixes (only) happen in it and updates like version 2.1 are tagged from it.
its name might be like "arramagong_2"
  • a tag is a snapshot of the svn at some point in time, aka a release name. It does not make sense to checkin fixes to one. They should ideally be set as read-only after creation to prevent this.
its name might be like "release_20090927_arramagong_2_0"

Creating

cd livedvd/gisvm/

svn copy trunk branches/arramagong_2
svn commit branches/arramagong_2 -m "Splitting off branch for 2.x"

cd branches/arramagong_2/bin/
# something like this, maybe need a for loop or xargs:
sed -e 's+gisvm/trunk+gisvm/branches/arramagong_2+g' *.sh | less   # check
sed -i -e 's+gisvm/trunk+gisvm/branches/arramagong_2+g' *.sh       # execute
cd -
 
svn copy branches/arramagong_2 tags/release_20090927_arramagong_2_0_3
svn commit tags/release_20090927_arramagong_2_0_3 -m "tag release 2.0.3"

Merging

To merge a change from trunk into a release branch use "svn merge", as follows: (in this example r2131 from trunk) 

svn up branches/arramagong_2/
cd branches/arramagong_2/

svn merge -c 2131 https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk
svn diff
svn commit -m "bugfix: bikeshed should be orange! (merge from trunk r2131)"

If you do this a lot you might make a little shell script. Here's one called svn_merge_livefromtrunk.sh: 

#!/bin/sh
# Usage: svn_merge_livefromtrunk <rev number>
svn merge -c $1 https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk

See also


Staging the new release

Website

Log in to live.osgeo.org. 

cd /osgeo/osgeolive
mkdir <versionnumber>

From another machine (ususally adhoc) go to the root of the docs and do 

scp -r /osgeo/livedvd/www/docs/* live.osgeo.org:/osgeo/osgeolive/<versionumber>/

Once done check that it's all good: 

http://live.osgeo.org/archive/versionnumber

Assuming docs are ok, then update the current symlink: 

chmod -R g+w <versionnumber>
rm current
ln -s <versionnumber> current

Download mirror

Upload files to https://sourceforge.net/projects/osgeo-live/files/

Add a new folder for the release, go into it, then scp the file to SourceForge.

Click the box to stage the files for 3 days to give time for the mirrors to populate.

Once the files are ready (no longer say "Pending...") and the download links and redirects from download.osgeo.org are tested & working, set the default download on the SourceForge site to either the full or mini ISO by clicking the "i" information button next to the file and "select all" for all platform types, then click the Save button.

Retrieved from "http://wiki.osgeo.org/w/index.php?title=Live_GIS_Build&oldid=128684"