[CentOS] CentOS6.6 installation failure

Mon Apr 20 13:48:23 UTC 2015
lhecking at users.sourceforge.net <lhecking at users.sourceforge.net>

 
> I would say to eliminate issues, the first thing to make sure is that
> your mailcap package is, indeed, good.

 Summary: it's a good package, but the wrong package for the location.

 I downloaded the package from a different mirror, and the install proceeds
 past it. However, now it stops at redhat-logos, with the same error

 An interesting observation: I now have several copies of the mailcap package
 on my system. When I compare md5sums, I see this:

 CentOS 6.4 tree:

029213d1c7b79c0dfa4f6d8063dbdce6  mailcap-2.1.31-2.el6.noarch.rpm (i386)
65e231403f819bea3dce22adee5cb373  mailcap-2.1.31-2.el6.noarch.rpm (x86_64)

 CentOS 6.6 tree, where the x86_64 version was replaced with a fresh copy:

029213d1c7b79c0dfa4f6d8063dbdce6  mailcap-2.1.31-2.el6.noarch.rpm (i386)
029213d1c7b79c0dfa4f6d8063dbdce6  mailcap-2.1.31-2.el6.noarch.rpm (x86_64)
65e231403f819bea3dce22adee5cb373  mailcap-2.1.31-2.el6.noarch.rpm.dist (previous)

 The packages in 6.4 are different for each arch, but in 6.6 they are the same.
 It appears this relates to how precisely you guys build a distribution?

 IIRC I took a shortcut when upgrading my repositories from 6.x -> 6.x+1
 by pre-populating the directories with the previous version to save some b/w.
 This could be the reason for what I see here.

 Now, if there were checksum files for everything, I knew which rpms I need
 to download again, but there aren't. Looks like the noarch packages are a
 good start, though.