 |
 |
Frederic Schaer wrote: > Right... > I'll prepare the test for the next release anyway... Would it be possible to change the test so that it checks that the CA RPM version number is greater than or equal to the "latest" version defined in the SFT code? For example: if "latest version" is defined to 31, then sites with version number 32 would pass but those with version number 30 would fail. This way sites that are eager to upgrade will not start failing tests. Or would this conflict with the policy of waiting for the LCG CA rpmlist to be updated? Stephen