On 05/26/2016 08:42 AM, 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. Note that my original diagnosis of needing to set --revision I believe now was incorrect and that the timestamp of the repo is determined by the newest metadata file listed in repomd.xml. -- Orion Poplawski Technical Manager 303-415-9701 x222 NWRA, Boulder/CoRA Office FAX: 303-415-9702 3380 Mitchell Lane [log in to unmask] Boulder, CO 80301 http://www.nwra.com