But the situation is now that one certificate file (01621954.0) can have
one of two valid checksums, depending on version. Can the SFTs can
handle this case?
Oliver Keeble Information Technology Department
[log in to unmask] CERN
+41 22 76 72360 CH-1211 Geneva 23
Frederic Schaer wrote:
> Hi,
>
> This is because the md5sums used by the SFT haven't been upgraded yet I
> guess...
> This will hopefully be done today
>
> - Piotr : maybe it would be good to find a way to compile these md5sums
> on the fly ?
>
> Frederic
>
> Kyriakos G. Ginis a écrit :
>
>>On Fri, Apr 08, 2005 at 08:31:11AM +0200, Ricardo Graciani wrote:
>>
>>
>>>Hi,
>>>
>>> This morning test reports the following error:
>>>
>>>Checking ca_UKeScience RPM: FAILED: rpm is ca_UKeScience-0.28-1,
>>>checking the file itself (/etc/grid-security/certificates/01621954.0)
>>>/etc/grid-security/certificates/01621954.0: FAILED
>>>md5sum: WARNING: 1 of 1 computed checksum did NOT match
>>>
>>> I went to the machine where the test run and check with rpm
>>>content:
>>>
>>> Everything looks OK with the files.
>>>
>>>
>>
>>Hi,
>>
>>On HG-01-GRNET we have exatly the same problem.
>>
>>--
>>Kyriakos Ginis, PhD Candidate
>>Software Engineering Laboratory
>>National Technical University of Athens
>>
>>
>>
|