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 -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> 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? What if these fail, and can I be sure no stray files left behind? Thanks __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list
