On Sat, 2003-08-23 at 02:47, Daniel Rubin wrote:
> I temporarily downgraded glibc rpm's to install oracle
> on RedHat 9 using
> this command:
> rpm -Uvh --force glibc-2.3.2-5.i686.rpm
> glibc-common-2.3.2-5.i386.rpm
> glibc-devel-2.3.2-5.i386.rpm
>
> which completed without error; and later, I
> re-upgraded the packages
> with this command:
> rpm -Uvh glibc-2.3.2-11.9.i686.rpm
> glibc-common-2.3.2-11.9.i386.rpm
> glibc-devel-2.3.2-11.9.i386.rpm
>
> I've since learned that doing this was a very bad
> thing, and that I should
> have done rpm -e for all these packages and then rpm
Who told you that?
> -i. But in the meantime,
> I'd like some help recovering from the current mess.
> For these packages, there
> are now parts of both versions present:
>
> rpm -e glibc, shows multiple packages:
> error: "glibc" specifies multiple packages
>
> rpm -qv shows two packages for glibc:
> # rpm -qv glibc
> glibc-2.3.2-5
> glibc-2.3.2-11.9
>
> and it looks like glibc is messed up:
> # rpm -V glibc
> Unsatisfied dependencies for glibc-2.3.2-5:
> glibc-common = 2.3.2-5
> .......T c /etc/rpc
> S.5....T /lib/i686/libc-2.3.2.so
> S.5....T /lib/i686/libm-2.3.2.so
> <snip>
This is because the files can only come from one "incarnation" of glibc,
in your case by the last installed version, 2.3.2-11.9.
>
> So the question is how best to clean up the failed
> glibc install?
> Do I do
> rpm -e glibc-2.3.2-5
> rpm -e glibc-2.3.2-11.9
> and then
> rpm -i glibc-2.3.2-11.9?
No, don't do this. Just "rpm -e glibc-2.3.2-5", otherwise you would
remove a core dependency for pretty much every program on your system
(one of these is rpm).
Nils
--
Nils Philippsen / Red Hat / nphilipp@redhat.com
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety." -- B. Franklin, 1759
PGP fingerprint: C4A8 9474 5C4C ADE3 2B8F 656D 47D8 9B65 6951 3011
Attachment:
signature.asc
Description: This is a digitally signed message part