On Friday, 25 July, 2003 16:50 Michael Schwendt wrote: > > In my case this is a remote server on which I have only > > ssh access, and thus no option of using a CD. I think > > I need a solution to replace this broken glibc with the > > original one coming with RedHat 7.2, but using only basic > > things I can download. > > > > I guess what I'm trying to do is manually do what > > rpm -Uvh -oldpackage glibc-*-2.2.4-32.i386.rpm > > would accomplish. But I have no idea where to begin. > > If rpm still works, rpm -ivh --force glibc*.i686.rpm > glibc-common*.i386.rpm should be fine. > > What other tools do still work? rpm2cpio maybe?
Rpm doesn't work anymore, or at least segfaults after the "preparing" stage whenever I try to rpm -Uvh or rpm -ivh, whatever package I choose. As for other commands I am not sure. rpm2cpio seems to work, or at least I can issue something like rpm2cpio glibc-common-2.2.4-32.i386.rpm > test and I get a big file test. Can I use this to restore the older glibc2.2.4 on my system without using the rpm command itself? The problem comes in the first place because I used option -nodeps of rpm to force the install of glibc-2.3.2-57, which wouldn't work because of a weird dependency problem with glibc-common-2.3.2-57 : rpmlib(PartialHardlinkSets) <= 4.0.4-1 I'm not sure if I used the i686 or i386 version of glibc when I issued this dreaded command, and I can see I have both version of the package in the directory :/ Thanks a lot for your help! Olivier -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list
