upon a request I updated my glibc 2.2.5-177 to 2.3.2-1 on suse 8.1 using an rpm I found on rpmseek.com Now I have a bunch of broken dependencies! how can I reinstall the original glibc? I have tried rpm -Uvh --oldpackage with no success! is there a way to do it from source with make? Regards, paul
This is a shot in the dark... but can someone please zip/tar the following
files from suse 8.1 and send them to me... these are the files I am now
missing since the disaster...
-p
/lib/ld-2.2.5.so
/lib/libdb.so.3
/lib/libnss_dns6.so.2
/usr/bin/db2_archive
/usr/bin/db2_checkpoint
/usr/bin/db2_deadlock
/usr/bin/db2_dump
/usr/bin/db2_dump185
/usr/bin/db2_load
/usr/bin/db2_printlog
/usr/bin/db2_recover
/usr/bin/db2_stat
please please please... will only take you a second........
----- Original Message -----
From: "sdcoyote"
On Saturday 07 June 2003 02.30, sdcoyote wrote:
upon a request I updated my glibc 2.2.5-177 to 2.3.2-1 on suse 8.1 using an rpm I found on rpmseek.com Now I have a bunch of broken dependencies! how can I reinstall the original glibc? I have tried rpm -Uvh --oldpackage with no success! is there a way to do it from source with make? Regards, paul
rpm2cpio oldglibc.rpm > glibc.cpio cd / cpio -i < /path/to/glibc.cpio ldconfig rpm -Uvh --oldpackage /path/to/oldglibc.rpm I had a similar situation when I upgraded from 8.1 to 8.2. The above procedure (or a similar one) rescued me
On Saturday 07 June 2003 02.30, sdcoyote wrote:
upon a request I updated my glibc 2.2.5-177 to 2.3.2-1 on suse 8.1 using an rpm I found on rpmseek.com Now I have a bunch of broken dependencies! how can I reinstall the original glibc? I have tried rpm -Uvh --oldpackage with no success! is there a way to do it from source with make? Regards, paul
rpm2cpio oldglibc.rpm > glibc.cpio cd / cpio -i < /path/to/glibc.cpio ldconfig rpm -Uvh --oldpackage /path/to/oldglibc.rpm
I had a similar situation when I upgraded from 8.1 to 8.2. The above
Hi Anders,
I am a little confused about that procedure... can you explain it a little
more... glibc.cpio ... what is that?
thank you...
-Paul
----- Original Message -----
From: "Anders Johansson"
(or a similar one) rescued me
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On Saturday 07 June 2003 06.16, sdcoyote wrote:
Hi Anders, I am a little confused about that procedure... can you explain it a little more... glibc.cpio ... what is that? thank you...
cpio is a package format much like tar, where all the files are basically streamed together in one big file. It is the internal package format used in rpm files. With the command rpm2cpio you can extract the cpio contents from an rpm package rpm2cpio oldglibc.rpm > glibc.cpio will do that, and put the cpio archive in a file called glibc.cpio cd / to go to the root of the file system cpio -i < /path/to/where/you/created/glibc.cpio will extract the contents of glibc to your file system, so you get the old glibc back rpm -Uvh /path/to/oldglibc.rpm won't do much with your file system, but you'll get a nice and tidy rpm database, so the rpm dependencies aren't broken. It was my experience when I upgraded from 8.1 to 8.2 that rpm from 8.1 wasn't compatible with glibc 2.3, but both rpm2cpio and cpio were, so the above procedure should work to get you back to a working system Next time take more care before trying to upgrade the glibc. It is probably the most difficult thing to get right of all the things you can do with a linux system. A kernel upgrade is a piece of cake by comparison
On Saturday 07 June 2003 06.16, sdcoyote wrote:
Hi Anders, I am a little confused about that procedure... can you explain it a
more... glibc.cpio ... what is that? thank you...
cpio is a package format much like tar, where all the files are basically streamed together in one big file. It is the internal package format used in rpm files. With the command rpm2cpio you can extract the cpio contents from an rpm package
rpm2cpio oldglibc.rpm > glibc.cpio
will do that, and put the cpio archive in a file called glibc.cpio
cd /
to go to the root of the file system
cpio -i < /path/to/where/you/created/glibc.cpio
will extract the contents of glibc to your file system, so you get the old glibc back
rpm -Uvh /path/to/oldglibc.rpm
won't do much with your file system, but you'll get a nice and tidy rpm database, so the rpm dependencies aren't broken.
It was my experience when I upgraded from 8.1 to 8.2 that rpm from 8.1 wasn't compatible with glibc 2.3, but both rpm2cpio and cpio were, so the above procedure should work to get you back to a working system
Next time take more care before trying to upgrade the glibc. It is
This is the error I am getting...
cpio -i < /popper_temp/glibc.cpio
cpio: lib/ld-linux.so.2 not created: newer or same age version exists
7452 blocks
----- Original Message -----
From: "Anders Johansson"
the most difficult thing to get right of all the things you can do with a linux system. A kernel upgrade is a piece of cake by comparison
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On Saturday 07 June 2003 06.29, sdcoyote wrote:
This is the error I am getting... cpio -i < /popper_temp/glibc.cpio cpio: lib/ld-linux.so.2 not created: newer or same age version exists 7452 blocks
ok, make it cpio -iud < /popper_temp/glibc.cpio
participants (2)
-
Anders Johansson
-
sdcoyote