Note: This version of the VDT (1.10.1) is supported, but is not our latest stable release. The current stable release is 2.0.0.
On 21 May 2008, the VDT team announced the release of VDT 1.10.1a.
In VOMS-Client, voms-proxy-info now sets its exit status correctly in more circumstances. Alain Roy and John Weigand worked together to create this patch, but it has now been accepted by the VOMS developers and is expected to be part of the next official VOMS release. Read toward the end of the ticket for more information, including the results of John Weigand’s thorough testing. (VDT ticket 3493)
Although this change should affect only VOMS-Client, it is best to update the entire VOMS package due to the way in which we build and package VOMS.
If you installed VDT 1.10.1 after VDT 1.10.1a was released (21 May 2008), you do not need to do any of these update operations because you will have 1.10.1a already.
The best way to update your VDT installation is to update the individual
packages that have changed. To be clear, we do not recommend
using pacman -update without specifying specific package
names. Also note that you only need to update packages if you installed them.
You can see what packages have been installed with:
pacman -l -d 1
Before you do the update directions that follow, please run the following commands.
cd $VDT_LOCATION . setup.sh vdt-control --off cp -pr $VDT_LOCATION BACKUP-LOCATION
The copy command makes a complete backup of your VDT installation, in case something goes wrong. Do not skip this step!
If you have the full VOMS package installed, update it:
pacman -update VOMS
If you have only the VOMS-Client package installed, then update just that part:
pacman -update VOMS-Client