I'd try using the --force.
Like, wow. I made a funny. Seriously, though, maybe --force the new one in.
It sounds like the rpm database took a little hosing.
Derek Stark
IT / Linux Admin
eSupportNow
xt 8952
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Chris Spackman
Sent: Friday, January 19, 2001 8:01 AM
To: Mandrake Expert List
Subject: [expert] glibc upgrades and accidental reboot
Here's an enjoyable one:
I was upgrading the glibc packages today when I accidently hit the reboot
button (stupid, but many accidents are). Just as
glibc-profile-whatever was finishing. glibc-whatever-version was already
done, as was glibc-devel-whatever, but as I said, glibc-profile was in the
middle of being upgraded.
Once everything came back up,
rpm -qa | grep glibc showed the new version on plain glibc, the new and the
old version of glib-devel-whatever, and showed only the old version of
glibc-profile-whatever. Just to be sure, I tried rpm -e
glibc-devel-oldversion, but it replied that the package was not installed.
glibc-profile installed no problem. Kpackage does not show
glibc-devel-oldversion as installed.
Question - do I need to worry about this? Is there some way to fix the
-devel-oldversion problem? I don't like the idea of rpm thinking that
something is installed when it actually isn't.
--
Chris and Yoshiko Spackman
[EMAIL PROTECTED] (English)
[EMAIL PROTECTED] (Japanese)
www.openhistory.org
"I will not be pushed, filed, stamped, indexed, briefed, debriefed, or
numbered. My life is my own."
-The Prisoner
