On 30/03/2016 4:40 AM, Pat Riehecky wrote:
> On 03/29/2016 09:55 AM, Orion Poplawski wrote:
>> Is there something going on in the SL staging process causing this?
> 
> There is not, once the files are published they remain unmodified until
> the next publication.

I get this all the time too:
Not using downloaded repomd.xml because it is older than what we have:
  Current   : Sat Mar 26 01:53:25 2016
  Downloaded: Sat Mar 26 01:53:13 2016

From two different VMs on two different networks. That's just in the
space of an hour.

I have local repos at both sites that I mirror hourly with:
rsync -akSH --delete-after
rsync://rsync.scientificlinux.org/scientific/7rolling/x86_64/updates/
/repos/7x/x86_64/updates/
rsync -akSH --delete-after
rsync://rsync.scientificlinux.org/scientific/7rolling/x86_64/os/
/repos/7x/x86_64/os/

Sadly, it never tells me *which* repo it gets this error on.

On a semi-related note, is 7rolling fastbugs the correct one to be used?
It doesn't seem to have had anything hit it since Jan 26 06:18 (UTC+11).

-- 
Steven Haigh

Email: [log in to unmask]
Web: https://www.crc.id.au
Phone: (03) 9001 6090 - 0412 935 897