On 11/16/2016 10:54 AM, Orion Poplawski wrote:
> On 09/06/2016 09:50 AM, Orion Poplawski wrote:
>> Seems to have returned.  Looks like sl-security repo.
>>
>> repodata/updateinfo.xml.bz2 timestamp goes from 1472831996 to 1472837835.89.
>> Looks like the floating point issue.  Some tool is writing bad timestamps.
>>
>>
>> /etc/cron.daily/0yum-daily.cron:
>>
>> Not using downloaded repomd.xml because it is older than what we have:
>>    Current   : Fri Sep  2 09:59:56 2016
>>    Downloaded: Fri Sep  2 09:59:55 2016
>>
> Again today:
>
> Not using downloaded repomd.xml because it is older than what we have:
>    Current   : Tue Nov 15 10:46:00 2016
>    Downloaded: Tue Nov 15 10:44:43 2016
>
> sl-fastbugs repo, still with the added floating point timestamp:
>
>    <timestamp>1479236641.28</timestamp>
>

Fixed... again... again....

Pat