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

David

---

CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos

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

On 7 Dec 2015 05:55, "John R Pierce" pierce@hogranch.com wrote:

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.

Keep in mind the release of 7.2 has happened in the world of RHEL.

This has updated a lot of components and included some that weren't there before.

EPEL tracks RHEL not CentOS, so there is always some uncertainty during these times.

This is one of the reasons it's worth spending some time setting up local mirrors so that they are kept stable during these transitions.

There's a lot of packages in epel-testing right now and now will probably still have to be rebuilt yet. Please file bugs if epel-testing does not already have a working package so maintainers can get notification and work on them.

Remember that EPEL policy is packages at least two weeks in testing so there's still some time before many can be pushed stable - and testers are always welcome!