Packages Cmake (base) And Metis (epel) Conflict With Each Other

Home » CentOS » Packages Cmake (base) And Metis (epel) Conflict With Each Other
CentOS 3 Comments

[root@build6 ~]# cat /etc/redhat-release CentOS release 6.5 (Final)
[root@build6 ~]#
[root@build6 ~]# uname -a Linux build6 2.6.32-431.23.3.el6.x86_64 #1 SMP Thu Jul 31 17:20:51 UTC 2014
x86_64 x86_64x86_64 GNU/Linux

[root@build6 ~]# yum clean all Loaded plugins: fastestmirror, security Cleaning repos: base extras updates Cleaning up Everything Cleaning up list of fastest mirrors
[root@build6 ~]#
[root@build6 ~]# yum –enablerepo=epel install cmake metis Loaded plugins: fastestmirror, security Determining fastest mirrors
* base: mirror.keystealth.org
* epel: mirrors.solfo.com
* extras: mirror.san.fastserv.com
* updates: repos.lax.quadranet.com base | 3.7 kB 00:00
base/primary_db | 4.4 MB 00:00
extras | 3.4 kB 00:00
extras/primary_db | 19 kB 00:00
updates | 3.4 kB 00:00
updates/primary_db | 4.7 MB 00:00
Setting up Install Process Resolving Dependencies
–> Running transaction check
—> Package cmake.x86_64 0:2.6.4-5.el6 will be installed
—> Package metis.x86_64 0:5.1.0-1.el6 will be installed
–> Processing Conflict: metis-5.1.0-1.el6.x86_64 conflicts cmake < 2.8 --> Finished Dependency Resolution Error: metis conflicts with cmake-2.6.4-5.el6.x86_64
You could try using –skip-broken to work around the problem You could try running: rpm -Va –nofiles –nodigest
[root@build6 ~]#

I don’t recall ever running into a conflict between packages in base and packages in epel repositories.

Anyone else getting the same error?

Thanks,

— Peter

3 thoughts on - Packages Cmake (base) And Metis (epel) Conflict With Each Other

  • I see it here, too. It’s clearly a packaging bug, probably due to the fact that the more recent Red Hattish Linuxes use CMake 2.8+.

    EPEL has a cmake28 package. Installing it doesn’t placate the dependency checker, but you could force the install, then link the
    “cmake28” binary to “cmake”.

    Or, you could try it with the platform CMake, and hope 2.6 is sufficient. It may well be. CMake is fairly stable from a feature standpoint.

  • If you would, please file a bug against the package in epel at bugzilla.redhat.com. This shouldn’t happen.

  • Sure. I will file a bug.

    Just to close this thread I used:
    yum –enablerepo=epel install cmake28 metis

    This works as long as one doesn’t need cmake from the base repository. Or, as Warren suggested, one can probably force install cmake and it will not conflict with cmake28.

    Thanks,