Metapackage Status
|
gLite 3.1 |
Status |
gLite 3.2 |
Status |
UNSTABLE |
Status |
glite-FTS_oracle |
R_3_1_21_0 |
DONE |
R_3_2_0_0 |
DONE(2) |
UNSTABLE |
ONGOING |
glite-FTA_oracle |
R_3_1_21_0 |
DONE |
R_3_2_0_0 |
DONE(1) |
UNSTABLE |
ONGOING |
glite-FTM |
R_3_1_14_0 |
DONE |
R_3_2_0_0 |
DONE |
UNSTABLE |
ONGOING |
glite-SE_dpm_mysql |
R_3_1_34_0 |
DONE |
R_3_2_4_0 |
DONE |
UNSTABLE |
ONGOING |
glite-LFC_mysql |
R_3_1_33_0 |
DONE |
R_3_2_4_0 |
DONE |
UNSTABLE |
ONGOING |
- The package myproxy conflicts with the one provided by epel, which has the priority but does not provides everything needed. Some problems with some dependencies.
- Some dependencies are provided by other packages that not work, so some manual interaction is needed.
- DONE: The metapackage has been created.
- DONE: The metapackage has been created and the certification tests successfully executed.
- DONE: The metapackage has been created but it only pass some of the certification tests. In the case of FTS+FTA, the problem might be in one or both of them. Wrong configuration?
For the unstable configuration: Some locked version don't work with the current glite_3.2_cert configuration. I have set some properties to force the compilation to be successful, so this should be changed in the future by developers when they want to build a unstable version.