rpm command and yum command not found
Hello,
after typing, this command: Code:
rpm -e --nodeps xulrunner |
What is the specific error output from both commands?
|
Quote:
|
we will need a lot more information
like: What is the operating system you are using ? The version of the OS ? And the full error you are getting . I take it you want to install "xulrunner" from the normal user account become "root" in the terminal for CentOS 6.4 Code:
su - unless as a very last resort to manually install xulrunner AND all the needed dependencies FIRST before installing "xulrunner" |
Quote:
The error is Quote:
Quote:
|
well the current RHEL5 is 5.9
and you did buy the required support contract ? right ? can you post the output of Code:
cat /etc/redhat-release the fastest fix will be to reinstall |
1 Attachment(s)
Quote:
If, for example Code:
yum update |
man that is hard to read
please "copy/paste" the text into the forum with this RHEL5 install you do have the support contract you bought have you contacted red hat tech support -- you are paying for it , so you might want to use it you will likely need to manually extract files from the rpm's that you will need to download from RHN ( ftp or in the web browser) and for that you will need there help |
This
Code:
rpm -e --nodeps xulrunner Its likely some other cmd has been used to remove bits of rpm/yum. You could check the root user's history; might show something. In any case, you could ask RH or try to force re-install rpm (& possibly yum) from the install media, but if its been upgraded one or more point releases since the install it might still have issues. You could try downloading the rpm/yum rpms (from RH)for the exact version you have (eg say 5.6) and force installing those. As above, the latest v5 is 5.9. Please post the output of the 'cat /etc/redhat-release' cmd, as requested by JohnVV & check if the install media is the same or not. |
Quote:
Code:
Red Hat Enterprise Linux Server release 5.9 (Tikanga) |
As per my above '...& check if the install media is the same or not.'
|
Quote:
|
# 12.
Quote:
They will most likely advise you to reinstall the OS. Possible workarounds : Use another OS to unpack the rpm package(s) That's $ rpm2cpio <package.rpm> | cpio -idmv ... and then copy the missing files into their locations. I.e. you cannot force install anything with no rpm command. - |
Quote:
|
# 14.
1) Never use 'rpm -e --nodeps ', unless you know what will happen. 2) Use another rpm based Linux OS to unpack the missing files : See #13. |
All times are GMT -5. The time now is 06:03 PM. |