Opened 10 years ago

Closed 10 years ago

Last modified 10 years ago

#450 closed defect (fixed)

Some install scripts for LiveDVD beta2 are outdated

Reported by: klokan Owned by: live-demo@…
Priority: critical Milestone:
Component: OSGeoLive Keywords:


I was reviewing the "build log" of LiveDVD beta2. It seems that some of the install scripts which are used to build the VM are not upgraded from SVN to the latest version. Please sync with SVN before building next version of the LiveDVD virtual machine!

I see that the is in the obsolete version, because it fails with an error message, which is not anymore in the source code of the script - you have used probably revision r1968 from date 2009-09-13. Latest version is r2107 from 2009-09-17. The latest version should run without problems.

Change history (5)

comment:1 Changed 10 years ago by wildintellect

Priority: normalcritical

This is important to make sure we get it right, can we include the svn revision code in the logs please.

comment:2 in reply to:  1 Changed 10 years ago by hamish

Replying to wildintellect:

can we include the svn revision code in the logs please.

that is a notoriously difficult thing to do with Subversion.

you can add SVN keywords to a file which chages a lot by using one or more of $Date$, $Id$, $Author$ in the text file then setting:

  svn propset svn:keywords "Date Id Author" filename.txt

as needed. $Id$ will include the svn rev number at checkin of that file. Maybe include as the second line of VERSION.txt and then have anything that does cat ../VERSION.txt add a "head -n 1" or "tail -n 1" to get release version or SVN check-in rev for that file? In this case that file will always need to be edited as the last step before packaging if you want it to be up to date!

probably better to have use "svn info" run from the livedvd/gisvm/trunk/ directory and grep for Last Changed Rev: and Last Changed Date:

some more ideas here


comment:3 Changed 10 years ago by hamish

Running svn2cl to create a repository ChangeLog? as a step in the build script is another idea.

comment:4 Changed 10 years ago by camerons

Resolution: fixed
Status: newclosed

In the build process, I do a fresh checkout of the scripts from svn into a clean xubuntu system.

The build process takes 24 to 48 hours to build, which is probably why the version you were looking at didn't have the latest script in it.

I've added "svn status" to the script, to print out the svn version number into the logs.

Closed this ticket as resolved.

comment:5 Changed 10 years ago by camerons

PS. svn status was added in version 2210. It will need to be added manually to 2.0beta3.

Note: See TracTickets for help on using tickets.