You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Current »

Minutes

Release Manager

Navid is making progress with the Windows builds.  He now needs to find a way to store the MySQL passwords and then should be set to go.

LSF troubles continue for the Mac builds, Navid will be contacting Neal to get an update from unix-admin.

u30 is down to about 87% full, and Navid has removed all that can be obviously cleaned up.  Richard reports u35 will be cleaned in the next couple of days, and we will then have an additional 4.6 TB.  Initially, Navid will move all the SCons builds to u35 and we will access if that leaves enough space on u30 for the CMT builds.

The installer is still producing distributions.  Jim Chiang had asked for instructions for Jonathan Ormes who has an interest in Mac builds.  Navid offered to provide instructions.  We will make those also available on Confluence or through the workbook.  Navid asked for testers on the linux and windows machines to be sure the instructions work as advertised.  Heather will happily test on windows and will try on Linux, and may enlist Joanne's help.

Navid has received some requests for a RHEL5 version of RMViewer.  The RHEL4 binaries will not work on RHEL5.  Actually, the RHEL4 version needs a rebuild to use the static libraries of MySQL rather than the shared libraries, that way if a user lacks MySQL on their system RMViewer will still run.  One additional issue is the need for the user to change the permissions on the Linux version of the executable, while the app comes ready to roll for Mac and Windows.

Release Manager Front End Web Page

Karen has implemented Joanne's suggested changes to display the time stamps on one line to allow easier comparison of start and stop times.  Karen encourages more comments.  Heather asked about viewing the checkout and compile output, which does seem available in RMViewer.  Karen responded that if the output is available in the DB tables, she makes it available.  Either the information is not in the tables, or she is looking in the wrong place.  Karen will contact Navid about that.

Windows Support

Joanne continues to make progress.  She can now build using either VS2003 or 2008, debug or not, and run resulting executables.  See latest entries in the log for more details.  Work continues on project files. Her development environment is not easily exportable for users:

  1. Express edition of VS 2008 is missing most documentation and normal install does not put c runtime libraries in the standard path (however one can just copy them to, e.g., the WINNT\system32 folder).
  2. The vs_revamp branch of SCons is not installed as a production SCons release would be and is not immediately compatible with GoGui.

2. is the bigger problem.  However, gossip on the SCons mailing list is that the vs_revamp branch will be merged into the trunk before the next significant SCons production release, 1.3.0.

GlastRelease

Heather has played with GR 15-49-00 and has built all the unit tests, libraries and applications after our meeting last week.  The Gleam package creates the test_Gleam application, but at the moment does not create a Gleam application.  They are admittedly identical except for the name, but it would probably be a good idea to create the Gleam app just as we do in CMT.

ROOT Builds

Emmanuel has spent some time rebuilding ROOT 5.20.00-gl1 on the Mac.  The first time around, the configure step failed to enable python.  That has been fixed and now Emmanuel has been testing the build.  Some troubles have cropped up in terms of using PyROOT.  Emmanuel has copied the Root.py file into the python distribution site-packages area to allow python to find libPyROOT.so.  There is now another issue when attempting to import ROOT in python.  This sounds very similar to what was happening on Windows when we moved to python 2.5.1.  Python now prefers the use of *.pyd rather than *.dll - perhaps there is a similar issue on the Mac.  The Windows fix, involved just copying the libPyRoot.dll and provide a libPyRoot.pyd as well.  In addition, it is unclear whether we should be moving portions of ROOT into the python distribution, rather, it would seem sufficient to update the PYTHONPATH environment variable.  Does that take care of the issues Emmanuel was seeing?

Agenda

  • Release Manager Status
    • Backend
      • Windows
      • Mac - LSF woes  Is there an ETA from unix-admins about getting that fixed?
      • u30, sounds like u35 is coming our way?
      • Other Issues?
  • rhel4 and rhel5
    • G4 rebuilt in optimized mode now in GR v17r2p1
    • Any Babar news?
  • Installer/  RMviewer /Tag Collector - Navid
  • Front End - Karen
  • No labels