Subject: | |
From: | |
Reply To: | |
Date: | Sun, 29 Jan 2017 16:34:17 -0800 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
I am not using a local repo. I'm trying a "repo clean all" and then an update.
{^_^}
On 2017-01-29 16:15, Bill Maidment wrote:
> Hi
> I got the same issue, but when I deleted repodata from my local repo and resynced from the rsync master, it sorted itself out.
> I believe this may have been caused by the firefox update which was released about the same time as 7.3
> Anyway, I no longer have the problem (for now).
>
> Cheers
> Bill
>
>
> -----Original message-----
>> From:jdow <[log in to unmask]>
>> Sent: Monday 30th January 2017 10:30
>> To: [log in to unmask]
>> Subject: Anacron has an upset tummy over sl-security
>>
>> /etc/cron.daily/0yum-daily.cron:
>>
>> Not using downloaded repomd.xml because it is older than what we have:
>> Current : Wed Jan 25 11:54:42 2017
>> Downloaded: Wed Jan 25 11:54:25 2017
>> Update notice SLBA-2015:2562-1 (from sl-security) is broken, or a bad duplicate,
>> skipping.
>> You should report this problem to the owner of the sl-security repository.
>> Update notice SLBA-2016:1445-1 (from sl-security) is broken, or a bad duplicate,
>> skipping.
>> Update notice SLBA-2016:1526-1 (from sl-security) is broken, or a bad duplicate,
>> skipping.
>> ... many more
>>
>>
>>
>> I thought this was supposed to be fixed. This suggests there still is some form
>> of problem with the sl-security repo.
>>
>> {^_^} Joanne
>>
>>
>
|
|
|