gLite > gLite 3.1 > glite-LFC_mysql > Update to glite-LFC_mysql 3.1.36-1.slc4  
 
 

 

 

gLite 3.1

glite-LFC_mysql - Update to version 3.1.36-1.slc4


Date 05.07.2010
Priority Normal

Description



glite-LFC_mysql

New version of LFC mysql v1.7.4

Bug fix release with two new features:

  • SURLs bulk lookup.
  • It also allows an easier installation of 32 and 64 bits libraries on 64 bits platforms.

Updated rpms

Name Version Full RPM name Description
LFC-server-mysql 1.7.4-6sec.slc4 LFC-server-mysql-1.7.4-6sec.slc4.i386.rpm LFC Server for a MySQL database backend
glite-LFC_mysql 3.1.36-1.slc4 glite-LFC_mysql-3.1.36-1.slc4.i386.rpm Metapackage for glite-LFC_mysql
glite-info-provider-release 1.0.0-9 glite-info-provider-release-1.0.0-9.noarch.rpm glite-info-provider-release
glite-security-voms-api-cpp 1.9.10-8.slc4 glite-security-voms-api-cpp-1.9.10-8.slc4.i386.rpm org.glite.security.voms-api-cpp v. 1.9.10.8
glite-security-voms-api 1.9.10-8.slc4 glite-security-voms-api-1.9.10-8.slc4.i386.rpm org.glite.security.voms-api v. 1.9.10.8
glite-yaim-lfc 4.0.6-2 glite-yaim-lfc-4.0.6-2.noarch.rpm glite-yaim-lfc module configures 3.0 LFC.
lcgdm-devel 1.7.4-6sec.slc4 lcgdm-devel-1.7.4-6sec.slc4.i386.rpm LCG Data Management common development libraries and header files.
lcgdm-libs 1.7.4-6sec.slc4 lcgdm-libs-1.7.4-6sec.slc4.i386.rpm LCG Data Management common shared libraries
lfc-devel 1.7.4-6sec.slc4 lfc-devel-1.7.4-6sec.slc4.i386.rpm LCG File Catalogue development libraries and header files
lfc-libs 1.7.4-6sec.slc4 lfc-libs-1.7.4-6sec.slc4.i386.rpm Client shared libraries for LCG File Catalogue
lfc 1.7.4-6sec.slc4 lfc-1.7.4-6sec.slc4.i386.rpm CLI for LCG File Catalogue
perl-lfc 1.7.4-6sec.slc4 perl-lfc-1.7.4-6sec.slc4.i386.rpm Perl interface to LCG File Catalog
python-lfc 1.7.4-6sec.slc4 python-lfc-1.7.4-6sec.slc4.i386.rpm Python interfaces to LCG File Catalog

The RPMs can be updated using yum via

Service reconfiguration after update

Not needed.

Service restart after update

Service must be restarted.

How to apply the fix

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