Re: rolling back 2 rpms which were installed with rpm --nodeps

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



* sting sting <qwejohn@xxxxxxxxxxx> [08/12/2003 1047EST]:
> i did rpm -e --justdb glibc
> i did rpm -e --justdb glibc-common
> and then
> rpm -Uvh *.rpm from a folder with these only older 2 rpm's
> I got the following message:
> package glibc-2.3.2-27.9.7 (which is newer than glibc-2.2.5-34)
> is already installed
> and similiar about glibc-common
> So I did not succeed installing the old rpms 
> (glibc-2.2.5-34,glibc-common-2.2.5-34)
> I want to add that  both
> i did rpm -e --justdb glibc
> i did rpm -e --justdb glibc-common
> gave dependencied error  messages.

How about
rpm -e --justdb --nodeps glibc
rpm -e --justdb --nodeps glibc-common

That's a shot in the dark on my part. :)  Obviously {in,unin}stalling
glibc is a dangerous venture.  If you do --justdb, you will leave
the old libs around (extra crud).  It would be safer to boot the
system with a boot/rescue CD or the like, mount your real system and
then do a real removal (rpm -e --nodeps) and real install of the new
stuff (rpm -ivh).

Just my US$0.02.

Ciao,
krjw.
-- 
Keith R. John Warno                  [k r j w  at  optonline dot net]


_______________________________________________
Rpm-list mailing list
Rpm-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/rpm-list

[Index of Archives]     [RPM Ecosystem]     [Linux Kernel]     [Red Hat Install]     [PAM]     [Red Hat Watch]     [Red Hat Development]     [Red Hat]     [Gimp]     [Yosemite News]     [IETF Discussion]

  Powered by Linux