LinuxQuestions.org - Completely hosed.

- Linux - Newbie (https://www.linuxquestions.org/questions/linux-newbie-8/)

- - Completely hosed. (https://www.linuxquestions.org/questions/linux-newbie-8/completely-hosed-49441/)

Completely hosed.

I was just trying to update gcc (from 2.96 to 3.2.1) and glibc (from 2.2.5 to 2.3.1) trying to make sure I didn't do anything stupid. I knew that some of my packages wouldn't make it through that upgrade so I was going to have to an rpm -U --nodeps at some point, but I was able to go through most things without a --nodeps.

Well I eventually did do something stupid and somehow had glibc-xx-2.2.5 _and_ glibc-xx-2.3.1 so I figured I should just
rpm -e the old version. Then I got the following error:

Code:

error: execution of %postun scriptlet from glibc-2.2.5-34 failed, exit status 255

Now I can't do much of anything. E.g.,

Code:

% ls

ls: Command not found.

% rpm -qa | grep glibc

grep: Command not found.

-qa: No such file or directory

% which \ls

/bin/ls

% /bin/ls

/bin/ls: Command not found.

Luckily I had mozilla open so that I can post this. I know I won't be able to log in again because I did Ctrl-Alt-F2 and tried to log in and couldn't. I guess I should be able to boot from a CD and backup my data and reinstall, but I hoped other people had some
brighter ideas before that.

Is rpm still working?If so just reinstall the old version.Other than that - no idea.I hosed python and glibc once on a gentoo box and was able to get it back up with rpm's.

I get this interesting error:

Code:

% rpm -i --test glibc-2.2.5-34.i686.rpm glibc-common-2.2.5-34.i386.rpm glibc-devel-2.2.5-34.i386.rpm

error: failed dependencies:

        glibc < 2.3.1 conflicts with glibc-common-2.3.1-36

        glibc > 2.2.5 conflicts with glibc-common-2.2.5-34

Seems rather paradoxical to me. If I try to force it:

Code:

% rpm -i --nodeps glibc-2.2.5-34.i686.rpm glibc-common-2.2.5-34.i386.rpm glibc-devel-2.2.5-34.i386.rpm



Many lines that look like

file /usr/share/info/libc.info-9.gz from install of glibc-devel-2.2.5-34 conflicts with file from package glibc-devel-2.3.1-36

you should be UPGRADING ( -U ) not installing these packages.

I was upgrading for the most part until I messed up at one point.
This is probably what led to my having both glibc-2.3.1 _and_
glibc-2.2.5. Now I can't upgrade because it will complain about
already having a newer version of glibc:

Code:

% rpm -U --nodeps glibc-2.2.5-34.i686.rpm \

glibc-common-2.2.5-34.i386.rpm glibc-devel-2.2.5-34.i386.rpm 

package glibc-2.3.1-36 (which is newer than glibc-2.2.5-34) is \ 

already installedpackage glibc-common-2.3.1-36 (which is newer \

than glibc-common-2.2.5-34) is already installed 

package glibc-devel-2.3.1-36 (which is newer than \

glibc-devel-2.2.5-34) is already installed

well use --oldpackage (check man page for exact name) or just plain install the new version properly.

I just noticed that I have the i686 version of glibc and i386 of glibc-commoon and glibc-devel. Could this be a problem?

Thank you, everyone! Things are working now. I used
--oldpackage to put the old version on and the _upgraded_ to the
new version of glibc. All the programs that I expected to be running
are running, _and_ I can compile stuff. I appreciate it very much.