> -----Original Message----- > From: shrike-list-admin@xxxxxxxxxx > [mailto:shrike-list-admin@xxxxxxxxxx] On Behalf Of William Hooper > Sent: Thursday, November 13, 2003 7:31 PM > To: shrike-list@xxxxxxxxxx > Subject: Re: Latest glibc update ruins system? > > > > Gordon Messmer said: > > Klaasjan Brand wrote: > >> Just download the glibc rpms to the machine (glibc, > -devel, -common > >> and > >> -util) and execute "rpm -Uvh --force glibc*" which will > force rpm to > >> downgrade the packages. > > > > Try to avoid using --force, which may not warn you about dangerous > > thing you may do. In this case, I believe --oldpackage is > sufficient. > > > > Also check out the Errata, because it has been updated to > work with non-RH kernels. > > -- > William Hooper > > > -- > Shrike-list mailing list > Shrike-list@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/shrike> -list > Since they released these packages again, I tried to upgrade, and I too received the errors formentioned. I did NOT downgrade the glibc package, all I did was delete (rm __*) the rpm database files, and when it recreated them, everything worked fine. Either they were corrupted during the upgrade, or as someone mentioned (what I think happened) is that one (or more) of the packages wasn't updated during the first release of the upgrade. After this second upgrade, without even trying to access the rpm database, I removed the files once again and let rpm recreate them. So far no problems. Thanks, Jake McHenry Nittany Travel MIS Coordinator http://www.nittanytravel.com -- Shrike-list mailing list Shrike-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/shrike-list
