That sort of appears to be the case. I tried nuking it. There is still a 
libasound.so..... file from other RPMs. So it's likely still workable. This WAS 
the main gateway machine to the Internet here for a dozen or so 'thingies' on 
the network. At the moment all it is doing is spamassassin filtering for my 
partner. I've migrated (migrained?) the other functions off to the newer $400 
wonder running 7.3 (as of today). This is fortunate. The disk in the older 
machine is starting to throw SMART pending sector errors. So now I can clear 
that disk off and donate the machine, perhaps with a recent FC on it, to the 
local SF club or something. Heh, donate it to the local home for people my age 
or older who can't get around but like really good puzzles. {^_-}

It's not so bad risking things like nuking a library from the system when it's 
not an important machine anymore.

{^_^}   Joanne

On 2017-01-27 23:43, Andrew C Aitchison wrote:
> On Fri, 27 Jan 2017, jdow wrote:
>
>> Ran yum --releasever=6.7 update sl-release
>>
>> Same error going 6.6 to 6.7 as 6,6 to 6.x (6.8).
>>
>> Transaction Check Error:
>>  file /lib64/libasound.so.2.0.0 from install of alsa-lib-1.1.0-4.el6.x86_64
>> conflicts with file from package libasound2-1.0.24.1-35.el6.x86_64
>
> I can't find libasound2 in the SL tree, although it is in ATrpms.
>
> You may be trying to mix too many repos ...
>
>> What now?
>> {^_^}
>>
>> On 2017-01-27 15:03, jdow wrote:
>>>  It gets through downloading a half gigabyte, trundles a bit and whines:
>>>
>>>  Transaction Check Error:
>>>    file /lib64/libasound.so.2.0.0 from install of
>>>  alsa-lib-1.1.0-4.el6.x86_64
>>>  conflicts with file from package libasound2-1.0.24.1-35.el6.x86_64
>>>
>>>  <grumble><mumble><bitch alot>
>>>  Trying a hail Mary.... yum --releasever=6.11 update sl-release
>>>
>>>  {o.o}
>>>
>>
>