SCIENTIFIC-LINUX-DEVEL Archives

May 2016

SCIENTIFIC-LINUX-DEVEL@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
David Sommerseth <[log in to unmask]>
Reply To:
David Sommerseth <[log in to unmask]>
Date:
Mon, 30 May 2016 10:07:17 +0200
Content-Type:
text/plain
Parts/Attachments:
text/plain (44 lines)
On 30/05/16 02:49, Steven Haigh wrote:
> On 2016-05-27 00:42, Pat Riehecky wrote:
>> On 05/25/2016 05:06 PM, Orion Poplawski wrote:
>>> On 05/19/2016 06:49 PM, Steven Haigh wrote:
>>>> Just to bang the drum, seems this has come up again:
>>>>
>>>> /etc/cron.daily/0yum-daily.cron:
>>>>
>>>> Not using downloaded repomd.xml because it is older than what we have:
>>>>    Current   : Wed May 18 06:06:41 2016
>>>>    Downloaded: Wed May 18 06:06:39 2016
>>>>
>>>> Sadly the cron job doesn't tell me which repo this was on.
>>>>
>>> It's appeared here again today with the sl7 fastbugs repo.
>>>
>>> I've attached the two different files.
>>>
>>
>> :(
>>
>> I've updated the push process yet again.  At every step of the process
>> it verifies the timestamp is current.
>>
>> In theory this will really really really fix this.
> 
> Bad news - this weekend:
> 
> Not using downloaded repomd.xml because it is older than what we have:
>   Current   : Wed May 25 00:01:12 2016
>   Downloaded: Wed May 25 00:01:10 2016
> 

I am seeing exactly the same on all SL7 boxes, both those using a local
mirror and those using external upstream sources.  The date, minutes and
seconds are exactly identical; I presume the hours are different due to
different time zones.


-- 
kind regards,

David Sommerseth

ATOM RSS1 RSS2