Up: IPP at the ROE

Upgrading IPP

Since IPP is in development, the source tree changes daily.

Before submitting a bug report, upgrade IPP.

Recall you've set $SRCDIR to something like /home/ert/local/src/ipp.

Upgrading, building, and installing the latest IPP

• Ensure the environment is set properly
  • psconfig default
• Go to the source directory main trunk
  • cd $SRCDIR/trunk
• Get the updates with svn. This is where subversion really shines. No need to know where you got the source from. It remembers.
  • svn update
• cd psconfig
• Check that we have all the perl libraries necessary
  • ./pscheckperl
  • If any are missing,
    • ./pscheckperl -build
• Rebuild the source code
  • ./psbuild -dev -extbuild -optimize > & Update.log
  • Check Update.log. It should end with ** psbuild: finished **. Or perhaps not.

Make necessary changes to the databases

For each of your databases, follow all the instructions in $SRCDIR/trunk/dbconfig/changes.txt

• Access the mySQL server
  • > mysql --user ipp --password
• Check the previous version
  • mysql> select * from dbversion;
• Check $SRCDIR/trunk/dbconfig/changes.txt for the MySQL commands to execute.

Troubleshooting after Upgrade

While downloading data (see IppDownloadData), if you get an error in the pantasks console like:

 -> pxCheckImportVersion (pxtools.c:278): unknown psLib error
     input file schema_version: 1.1.57 does not match data base: 1.1.56
 -> importrunMode (stacktool.c:1395): unknown psLib error
     pxCheckImportVersion failed

then you need to adjust the schema_version stored in the database. In the following example, I'm assuming the database is PS1data owned by the mysql user ipp and we need to update to version 1.1.57.

• mysql --user ipp --password
  • <enter password>
  • show databases;
  • use PS1data;
  • update dbversion set schema_version='1.1.57', updated=CURRENT_TIMESTAMP();
  • quit;