[CentOS] Centos 7 Yum conflict libicalss

[david]

At 09:28 PM 12/6/2015, david wrote:
>To: CentOS mailing list <centos at centos.org>, centos at centos.org
>From: david <david at daku.org>
>Subject: Re: [CentOS] Centos 7 Yum conflict libicalss
>In-Reply-To: <1449380359.16567.27.camel at gmail.com>
>References: <201512060139.tB61d88R009873 at telford.daku.org> 
><1449380359.16567.27.camel at gmail.com>
>
>At 09:39 PM 12/5/2015, Earl Ramirez wrote:
>>On Sat, 2015-12-05 at 17:39 -0800, david wrote:
>> > Folks
>> >
>> > My Centos 7 systems are all failing to update because of
>> >
>> > Error: Package: orage-4.10.0-4.el7.x86_64 (@epel)
>> >             Requires: libicalss.so.0()(64bit)
>> >             Removing: libical-0.48-6.el7.x86_64 (@base)
>> >                 libicalss.so.0()(64bit)
>> >             Updated By: libical-1.0.1-1.el7.x86_64 (cr)
>> >                ~libicalss.so.1()(64bit)
>> > Error: Package: orage-4.10.0-4.el7.x86_64 (@epel)
>> >             Requires: libicalvcal.so.0()(64bit)
>> >             Removing: libical-0.48-6.el7.x86_64 (@base)
>> >                 libicalvcal.so.0()(64bit)
>> >             Updated By: libical-1.0.1-1.el7.x86_64 (cr)
>> >                ~libicalvcal.so.1()(64bit)
>> > Error: Package: orage-4.10.0-4.el7.x86_64 (@epel)
>> >             Requires: libical.so.0()(64bit)
>> >             Removing: libical-0.48-6.el7.x86_64 (@base)
>> >                 libical.so.0()(64bit)
>> >             Updated By: libical-1.0.1-1.el7.x86_64 (cr)
>> >                ~libical.so.1()(64bit)
>> >   You could try using --skip-broken to work around the problem
>> >   You could try running: rpm -Va --nofiles --nodigest
>> >
>> >
>> > Is there something I should (not) be doing?
>> > The command was:
>> >    yum update
>> >
>> >
>>
>>Hello David,
>>
>>The conflict is caused by 'orage' from epel, I am not to familiar with
>>that package, you can try and uninstall it and run 'yum clean all' and
>>try to update your box again. Or you can exclude it from epel repo.
>>
>>
>>_________________
>
>Thanks for that.  It appears to have solved the problem.  I just 
>wonder if it should have been taken care of "automatically" without 
>my intervention, running nightly "yum -y update" commands.
>
>David


Newest Information

Having been unable to reproduce the fix, I managed to figure out that 
the offending package is the group Xfce.  It was the only package in 
my system that wanted the earlier copies of libical*.  By avoiding 
Xfce, the problem went away.

David