gLite > gLite 3.1 > glite-VOBOX > Update to glite-VOBOX 3.1.6-0  
 
 

 

 

gLite 3.1

glite-VOBOX - Update to version 3.1.6-0


Date 06.03.08
Priority Normal

Description

GFAL update

There is also a new version of glite-data-gfal (v1.10.8-1) with the following bug fixes and new features:
  • lcg-utils creation of subdirectories
  • The GLUE AccessControlBaseRule can be based on VOMS FQANs
  • Fix bug #31687: GFAL Tests: Return wrong code on success
  • Add man pages for gfal_get_ids function
glite-BDII

An new version of the bdii package which includes an index for the attribute GlueServiceEndpoint. This attribute is now used by lcg-utils.
glite-jdl-api-cpp

This update introduces a new version of the glite-jdl-api-cpp package, which fixes several bugs.


Please also have a look at the list of known issues.

This update fixes various bugs. For the full list of bugs, please see list below.

Fixed bugs

Number Description
 #16681 requirements repeated several times by UI while submitting
 #28483 FuzzyRank attribute is not propagate from dag/collection parent to its nodes
 #30143 [Shallow]RetryCount attributes are not propagated from dag/collection parent to its nodes
 #31687 GFAL Tests: Return wrong code on success
 #32929 The GLUE AccessControlBaseRule can be based on VOMS FQANs
 #33288 lcg-utils creation of subdirectories
 #33327 [lcg-util] lcg_util does not work for VO names of 15 or more characters
 #33402 bdii: Missing index

Updated rpms

Name Version Full RPM name Description
GFAL-client 1.10.8-1.slc4 GFAL-client-1.10.8-1.slc4.i386.rpm Grid File Access Library
bdii 3.9.1-5 bdii-3.9.1-5.noarch.rpm bdii
glite-VOBOX 3.1.6-0 glite-VOBOX-3.1.6-0.i386.rpm gLite metapackage (glite-VOBOX)
glite-jdl-api-cpp 3.1.12-1.slc4 glite-jdl-api-cpp-3.1.12-1.slc4.i386.rpm org.glite.jdl.api-cpp v. 3.1.12

The RPMs can be updated using yum via

Service reconfiguration after update

Not needed.

Service restart after update

Not needed.

How to apply the fix

  1. Update the RPMs (see above)
  2. Update configuration (see above)
  3. Restart the service if necessary (see above)