Displaying 5 results from an estimated 5 matches for "libicalss".
Did you mean:
libcalls
2015 Dec 06
3
Centos 7 Yum conflict libicalss
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()(64...
2015 Dec 26
0
Centos 7 Yum conflict libicalss
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:
>...
2015 Dec 06
0
Centos 7 Yum conflict libicalss
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)
> R...
2015 Dec 07
3
Centos 7 Yum conflict libicalss
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 (...
2015 Dec 07
0
Centos 7 Yum conflict libicalss
On 12/6/2015 9:28 PM, david wrote:
> 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.
epel needs to fix that package, probably.
--
john r pierce, recycling bits in santa cruz