gLite 3.0
glite-FTS_oracle - Update to version 3.0.13-3
edg-mkgridmap
The new version of edg-mkgridmap (2.9.0) fixes the interoperability problem with axis (1.2.1) and voms-admin (>1.2.20). There are also updates and fixes in the man pages, for example, a valid support email address has been added.
glite-yaim
The new version of glite-yaim adds support for DGAS logging on lcg-CE.
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.
glite-FTS_oracle - Update to version 3.0.13-3
Date | 30.04.07 |
---|---|
Priority | Normal |
Description
edg-mkgridmap
The new version of edg-mkgridmap (2.9.0) fixes the interoperability problem with axis (1.2.1) and voms-admin (>1.2.20). There are also updates and fixes in the man pages, for example, a valid support email address has been added.
glite-yaim
The new version of glite-yaim adds support for DGAS logging on lcg-CE.
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 |
---|---|
#24043 | edg-mkgridmap man page support e-mail address not valid |
#24053 | edg-mkgridmap man page does not mention X509_USER_PROXY |
#24343 | edg-mkgridmap does not respect the voms-admin WSDL (i.e., is not interoperable with axis 1.2.1 and voms-admin >1.2.20) |
Updated rpms
Name | Version | Full RPM name | Description |
---|---|---|---|
edg-mkgridmap | 2.9.0-1 | edg-mkgridmap-2.9.0-1.noarch.rpm | A tool to build the grid-mapfile |
glite-BDII | 3.0.2-9 | glite-BDII-3.0.2-9.noarch.rpm | gLite BDII node |
glite-FTS_oracle | 3.0.13-3 | glite-FTS_oracle-3.0.13-3.noarch.rpm | gLite FTS Oracle node |
glite-yaim | 3.0.1-12 | glite-yaim-3.0.1-12.noarch.rpm | glite-yaim |
The RPMs can be updated using apt via
- via apt: apt-get dist-upgrade
- or via a download from:
http://glitesoft.cern.ch/EGEE/gLite/APT/R3.0/rhel30/RPMS.updates/
Service reconfiguration after update
Not needed.
Service restart after update
Not needed.
How to apply the fix
- Update the RPMs (see above)
- Update configuration (see above)
- Restart the service if necessary (see above)