On 10/29/2014 03:59 AM, wwp wrote:
Hello there,
I'm checking if I can upgrade safely from CentOS6.5 to 6.6 using yum, and here's what it says:
===================== [snip] --> Finished Dependency Resolution --> Running transaction check ---> Package kernel.x86_64 0:2.6.32-431.23.3.el6.centos.plus will be erased ---> Package kernel-devel.x86_64 0:2.6.32-431.23.3.el6.centos.plus will be erased ---> Package mpich2.x86_64 0:1.2.1-2.3.el6 will be obsoleted --> Processing Dependency: libmpich.so.1.2()(64bit) for package: hdf5-mpich2-1.8.5.patch1-7.el6.x86_64 --> Processing Dependency: libmpichf90.so.1.2()(64bit) for package: hdf5-mpich2-1.8.5.patch1-7.el6.x86_64 --> Processing Dependency: mpich2 for package: hdf5-mpich2-1.8.5.patch1-7.el6.x86_64 Package mpich2 is obsoleted by mpich, but obsoleting package does not provide for requirements --> Finished Dependency Resolution Error: Package: hdf5-mpich2-1.8.5.patch1-7.el6.x86_64 (@epel) Requires: mpich2 Removing: mpich2-1.2.1-2.3.el6.x86_64 (@base) mpich2 = 1.2.1-2.3.el6 Obsoleted By: mpich-3.1-4.el6.x86_64 (base) Not found Error: Package: hdf5-mpich2-1.8.5.patch1-7.el6.x86_64 (@epel) Requires: libmpichf90.so.1.2()(64bit) Removing: mpich2-1.2.1-2.3.el6.x86_64 (@base) libmpichf90.so.1.2()(64bit) Obsoleted By: mpich-3.1-4.el6.x86_64 (base) Not found Error: Package: hdf5-mpich2-1.8.5.patch1-7.el6.x86_64 (@epel) Requires: libmpich.so.1.2()(64bit) Removing: mpich2-1.2.1-2.3.el6.x86_64 (@base) libmpich.so.1.2()(64bit) Obsoleted By: mpich-3.1-4.el6.x86_64 (base) Not found You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest =====================
Those packages depend on mpich2.x86_64:
boost-graph-mpich2 x86_64 1.41.0-18.el6 @base 440 k boost-mpich2 x86_64 1.41.0-18.el6 @base 353 k boost-mpich2-python x86_64 1.41.0-18.el6 @base 44 k hdf5-mpich2 x86_64 1.8.5.patch1-7.el6 @epel 6.8 M mpich2-devel x86_64 1.2.1-2.3.el6 @base 6.8 M
I presume it's the dep from hdf5mich from epel which is blocking.. Any hint about what I could do now?
This is a known epel problem, they are working on it: