#4090: BUG in vdt-version, reports wrong version of condor-cron

vdt-version reports an incorrect version of condor-cron
I recently updated a couple of packages on my OSG CE, vdt 1.10.1,
but not condor-cron. Nevertheless vdt-version reports that
I'm running condor-cron 7.0.4, as opposed to the version 7.0.2
which originally came with the VDT and all the condor logs say
that it still is condor 7.0.2 when the daemons start up.

Steve Timm




--
------------------------------------------------------------------
Steven C. Timm, Ph.D (630) 840-8525
timm@fnal.gov http://home.fnal.gov/~timm/
Fermilab Computing Division, Scientific Computing Facilities,
Grid Facilities Department, FermiGrid Services Group, Assistant Group Leader.

On Wed Oct 01 15:42:43 2008, timm@fnal.gov wrote:

Hi Steve,

This is a bug that has existed for a long time. Scot Kronenfeld and I
just talked about it, and we think that Scot will be able to implement a
fix in the short-term future. The fix will have to be phased in
gradually, so it won't get perfect all at once, but the situation will
gradually improve.

I've assigned Scot this ticket, and he'll let us know how the
implementation goes.

-alain

-----------------------------------------------------------------
Alain Roy vdt-support@opensciencegrid.org
VDT Support http://vdt.cs.wisc.edu/support.html

Commit comment:
Overhaul of vdt-version. The script now will display the correct
version of installed software rather than the version that is in
the vdt-version.info file (which is static for each VDT lettered
release). In order to use this behavior, packages must use the
new "--short-version" flag when being added. As we update packages
we will convert their pacman files to use this new flag.

I also fixed the indentation, changed variable names, and various
other changes, so this change will touch almost every line of this
file.


Changed files:
U vdt/branches/vdt-1.10.1/VDT-Version/vdt/bin/vdt-version

To generate a diff:
svn diff -c 8150 file:///p/vdt/workspace/svn

Commit comment:
We've changed the output of vdt-version slightly, so I changed that test
accordingly.


Changed files:
U vdt/branches/vdt-1.10.1/VDT-Certification-Tests/vdt/tests/tests/install.t

To generate a diff:
svn diff -c 8161 file:///p/vdt/workspace/svn

Commit comment:
For all the packages updated in 1.10.1k, I added the "--short-version"
argument to the "vdt-version --add" call. This is a new parameter for
vdt-version, and will enable vdt-version to display the correct version
of an installed software component (as well as check for available updates)


Changed files:
U vdt/branches/vdt-1.10.1/Apache/Apache.pacman
U vdt/branches/vdt-1.10.1/Condor/Condor.pacman
U vdt/branches/vdt-1.10.1/Condor-Cron/Condor-Cron.pacman
U vdt/branches/vdt-1.10.1/Gratia-Reporting/Gratia-Reporting.pacman
U vdt/branches/vdt-1.10.1/Gratia-Services/Gratia-Services.pacman
U vdt/branches/vdt-1.10.1/MySQL-5/MySQL-5.pacman
U vdt/branches/vdt-1.10.1/OSG-RSV/OSG-RSV.pacman
U vdt/branches/vdt-1.10.1/Tomcat-5.5/Tomcat-5.5.pacman
U vdt/branches/vdt-1.10.1/UberFTP/UberFTP.pacman

To generate a diff:
svn diff -c 8163 file:///p/vdt/workspace/svn

Commit comment:
Added --short-version


Changed files:
U vdt/branches/vdt-1.10.1/CGSI-gSOAP/CGSI-gSOAP.pacman

To generate a diff:
svn diff -c 8166 file:///p/vdt/workspace/svn

On Mon Oct 06 14:52:30 2008, kronenfe wrote:

That should say, the script will NOW* attempt to determine if updates
are available.