On 05/23/2012 04:41 PM, Timothy Murphy wrote:
> Johnny Hughes wrote:
>
>>> -------------------------------
>>> Error: Protected multilib versions: glibc-2.12-1.47.el6_2.12.x86_64 !=
>>> glibc-2.12-1.47.el6_2.9.i686
>>> ** Found 3 pre-existing rpmdb problem(s), 'yum check' output follows:
>>> bash-4.1.2-9.el6_2.x86_64 is a duplicate with
>>> bash-4.1.2-8.el6.centos.x86_64 glibc-common-2.12-1.47.el6_2.12.x86_64 is
>>> a duplicate with glibc- common-2.12-1.47.el6_2.9.x86_64
>>> glibc-common-2.12-1.47.el6_2.12.x86_64 has missing requires of glibc =
>>> ('0', '2.12', '1.47.el6_2.12')
>>> -------------------------------
>>> I've tried "rpm --rebuilddb" but that did not seem to help.
>>>
>>> Any suggestions or advice gratefully received.
>> You have both the i686 and x86_64 versions of glibc installed. That
>> error means that the repo you are trying to update from has a different
>> version of i686 glibc and x86_64 glibc ... or you are trying to upgrade
>> one (the x86_64 version) and not the other (the i686 version).
>>
>> Since multilib installs share some files (all the Documentation, etc.),
>> that means you must install the same version of each arch if you install
>> both i686 and x86_64 packages.
> Thank you very much for your response.
>
> But I'm afraid I'm not clear what action I can take.
> I don't like to remove any glibc or glibc-common packages,
> as I'm afraid it might have a disastrous effect,
> since they seem to be required by so many other packages,
> including the kernel.
>
> I'm slightly puzzled how the system got in this position,
> as I have never said anything except "yum upgrade",
> and the repos I have enabled all seem harmless,
> though there are several of them:
> [adobe-linux-x86_64, CentOS-CR (cr), epel, kbs-CentOS-Extras, rpmforge.
>
> The system (which is in another country) seems to be running fine.
> If I leave it will it sort itself out in time?
>
>
Based on your errors, what I would do is this:
1. You only need 1 version of glibc-common.x86_64. The only way you
could have gotten into this position is either your machine died in the
middle of a yum update or someone force installed the later glibc-common
via the rpm -i command.
I would first try to install the yum-utils package with this command:
yum install yum-utils
once that is installed, I would try:
yum-complete-transaction
If you do not have any incomplete transactions, then you have some bad
packages force installed.
I would figure out exactly what packages I had installed for glibc and
get them all on one version ... you need to be careful with glibc (and
its sub packages) ... it is the most important package on your machine.
How I would do this is that I would download all the RPMs for the latest
version of all the packages you have installed ... for me that would be:
glibc-devel-2.12-1.47.el6_2.12.x86_64.rpm
glibc-headers-2.12-1.47.el6_2.12.x86_64.rpm
glibc-2.12-1.47.el6_2.12.i686.rpm
glibc-common-2.12-1.47.el6_2.12.x86_64.rpm
glibc-2.12-1.47.el6_2.12.x86_64.rpm
nscd-2.12-1.47.el6_2.12.x86_64.rpm
You may have others.
Once I had them all in the same directory, I would try a:
rpm -Uvh *.rpm
then I would look at the errors
based on those errors (if it does not install) then I would likely do:
rpm -Uvh --force *.rpm
that will LIKELY clean up your rpm issues for glibc ... but if you don't
understand the errors, post those here.
2. For bash, I would:
rpm -e bash-4.1.2-8.el6.centos.x86_64
then I would reinstall the other bash
yum reinstall bash-4.1.2-9.el6_2.x86_64
3. The real issue here is to make sure you figure out HOW you got in
this position and how NOT to get into it again.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 262 bytes
Desc: OpenPGP digital signature
URL: <http://lists.centos.org/pipermail/centos/attachments/20120523/cb4f9e77/attachment-0003.sig>