VDT 1.10.1a was released yesterday, May 21, 2008. It consists of a patch to voms-proxy-info to return the correct exit status. John Weigand and Alain Roy worked together on this fix.
Suchandra asked about bugs found yesterday in Configure-GIP. Tim replied that the VDT team hasn't yet heard about these. When an update is available, the involved people should contact firstname.lastname@example.org and the VDT team will see about integrating it.
Ed asked about addressing the Debian OpenSSL vulnerability. Will the VDT detect it and install its own? Tim replied that the VDT uses the system provided OpenSSL and will likely continue to do so. However, detecting an insecure OpenSSL and refusing to install is a possibility that the VDT team will consider.
Ed asked about problems installing the VDT on Fedora Core 9. This is an unsupported configuration. He told the system to treat his machine as Fedora Core 4. FC4 has Perl 5.8. FC9 has Perl 5.10. The problem is that Pacman requires Perl 5.8 and erroneously concludes that 5.10 is less than 5.8, probably because it's doing a simple textual comparison. Tim replied that we'll file the version detection bug upstream to Saul Youssef. That said, the VDT cannot currently support Perl 5.10. In particular, the VDT includes Perl packages built against Perl 5.8. Further discussion may happen offline.
Wayne asked about release timelines. Tim noted that 1.10.1a was released yestered. OSG is currently testing. The VDT team expects to release another lettered update before OSG 1.0. There will likely be further bugfix lettered releases after OSG 1.0; perhaps a month or so based on previous releases. Suchandra notes that OSG 1.0 is scheduled for June 2, 2008.
Tim noted that Scot Kronenfeld and Alain Roy are due back next Tuesday and Wednesday, respectively. However, catchup and other obligations mean the VDT team will be working more slowly than usual for a while beyond that.
Suchandra asked about problem when Configure-GIP tried to set up the dcache module. Apparently a Python module needed for access to Postgres was missing. Tim replied that we expect this module to be present on the system. We do ship Python in some cases if the system installed Python is too old. We don't bring many modules along, although this may increase in the future.
Ted asked about building LCG-utils, specifically about changing the version number of LCG-utils. Tim replied that package version numbers are set in the top level defs file. Ted is working on the 1.10.1 branch; Tim also needs to update the VDT version number for that branch to allow further builds to work. (It's currently targeting 1.10.1 and not the development cache. Attempts to modify the deployed cache will fail.)
Ed asked about building the VDT from source on unsupported platforms. Tim replied that this hasn't been done before. There are lots of infrastructure assumptions inside of the VDT. The VDT does not have a single Makefile, and the build process assumes the use of the NMI Build and Test Lab. How to do this isn't clear now, and will likely be a more long term problem.