| [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] |
I managed to resolve this with a leap of faith:
rpm -ivh --replacefiles glibc-2.2.5-42.i686.rpm \
glibc-common-2.2.5-42.i386.rpm
A check with:
rpm -q glibc
rpm -q glibc-common
revealed that yes, both old (redundant) versions were still there, and the
new (correct) version was also there for each of these packages.
I then followed up with:
rpm -e --allmatches glibc-common-2.2.5-34 glibc-2.2.5-34
and then confirmed that the desired result had completed with:
rpm -q glibc
rpm -q glibc-common
A final check with the following verification gave me the warm fuzzies, when
it returned with no problem:
rpm -V glibc-common glibc
-=-=-=-=-=-=-
Honourable mentions to:
- Sven Heinicke for suggesting:
rpm --rebuilddb
(which I'd neglected to mention in my original e-mail that I'd tried, to no
avail)
and to:
- Carter Baltimore for suggesting I update to a later version of glibc.
jc
-----Original Message-----
From: Carroll, Jim P [Contractor]
Sent: Friday, February 14, 2003 2:20 PM
To: 'linuxmanagers@linuxmanagers.org'
Subject: Q: rpm - resolving multiple pkg instances
This should describe the problem pretty quickly:
$ cat /proc/version
Linux version 2.4.18-3 (bhcompile@daffy.perf.redhat.com) (gcc version 2.96
20000731 (Red Hat Linux 7.3 2.96-110)) #1 Thu Apr 18 07:37:53 EDT 2002
$ rpm -q glibc
glibc-2.2.5-34
glibc-2.2.5-34
$ rpm -q glibc-common
glibc-common-2.2.5-34
glibc-common-2.2.5-34
As you can see, I've got duplicate entries in the RPM database. I'm
familiar with the --allmatches option for removing packages, but it's
somewhat difficult to remove glibc. :-/
FWIW, I just finished upgrading from an older version of glibc/glibc-common.
I've downloaded version 2.2.5-42 in preparation for another attempt to clean
this up. Previously, there were 2 instances of glibc/glibc-common, but with
different versions.
I suspect that when I run:
rpm -Uvh glibc-2.2.5-42.i686.rpm glibc-common-2.2.5-42.i386.rpm
that I'll end up updating both instances of each package in the RPM
database. I'm hopeful that someone can suggest a better approach.
TIA
jc
submissions: LinuxManagers@linuxmanagers.org
subscribe/unsubscribe:
http://www.linuxmanagers.org/mailman/listinfo/linuxmanagers
_______________________________________________
LinuxManagers mailing list - http://www.linuxmanagers.org
submissions: LinuxManagers@linuxmanagers.org
subscribe/unsubscribe: http://www.linuxmanagers.org/mailman/listinfo/linuxmanagers
[Home] [Kernel List] [Linux SCSI] [Video 4 Linux] [Linux Admin] [Yosemite News] [Motherboards]