Subject: | |
From: | |
Reply To: | |
Date: | Wed, 2 May 2018 09:54:53 -0500 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
It appears that there was a problem in how the updateinfo.xml file was
built for the sl-security repository yesterday, which conflicted with a
similar entry for the SLEA-2017:1977 ID in the sl repository. Whatever
it was seems to have been repaired now, because I'm not seeing this same
error today. That ID no longer appears in sl-security's updateinfo.xml file.
On 05/02/2018 02:04 AM, Maarten wrote:
> Same here.
>
> On 05/02/2018 08:51 AM, Bill Maidment wrote:
>> All my servers are showing this today:
>>
>> /etc/cron.daily/0yum-daily.cron:
>>
>> Update notice SLEA-2017:1977-1 (from sl-security) is broken, or a bad
>> duplicate, skipping.
>> You should report this problem to the owner of the sl-security
>> repository.
>> If you are the owner, consider re-running the same command with
>> --verbose to see the exact data that caused the conflict.
>>
>>
>> Cheers
>> Bill Maidment
--
Gilles R. Detillieux E-mail: <[log in to unmask]>
Spinal Cord Research Centre WWW: http://www.scrc.umanitoba.ca/
Dept. of Physiology and Pathophysiology, Rady Faculty of Health Sciences,
Univ. of Manitoba Winnipeg, MB R3E 0J9 (Canada)
|
|
|