Note: This web site is only kept up to date for OSG Software
1.2 (VDT 2.0.0). If you are looking for information for the most recent
release, the RPM-based OSG Software 3.0, please see
the OSG documentation web site
VDT 2.0.0p8 Update
On 2009-08-21, the VDT team announced the release of VDT 2.0.0p8.
-
Updated OSG-RSV to fix a problem that prevented the gratia-consumer
from sending RSV records if the python OpenSSL module was not installed
on the system. The VDT will automatically install the pyOpenSSL module
as of 2.0.0p6, and with this fix, the gratia-consumer can now find it
in the environment. (VDT ticket 5653)
-
Updated Apache to version 2.2.13, which fixes some security issues.
(VDT ticket 5639)
-
Updated Java 1.5 and 1.6 to new versions which include security
fixes. (VDT ticket 5644)
-
Fixed a bug in configure_bestman that prevented it from being run
twice.
-
Updated the Gratia probes to fix a bug that can cause delayed reporting
of records (VDT ticket 5695)
-
Updated the Gratia Services and Reporting packages to 1.04.4. This includes
a fix for PBS reporting, and other bug fixes. Most sites do not run a local
Gratia collector, so this update will not affect them. (VDT ticket 5675)
-
Improved robustness when upgrading a VOMS-Server from an older VDT. Upgrade
installs should now finish, as opposed to crashing during the pacman
install. However, there are some reports from the field (Dan Yocum) that
upgrade installs still do not work correctly. We will continue to
investigate and make necessary improvements in future releases.
-
Further reduced the size of vdt-install.log by reducing extraneous logging
from vdt-update-certs. (VDT ticket 5605)
If you installed VDT 2.0.0 after VDT 2.0.0p8 was released on
2009-08-21, you do not need to do any of these update operations
because you will have 2.0.0p8.
Recommended method: VDT Updater
We strongly encourage users to update the VDT using the VDT updater
script:
VDT Updater Instructions
Not recommended: Pacman update
If you really want to do it the hard way,
instructions for updating by using
Pacman directly are available on another page. This method is
hard to follow and error prone.