Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

j2sdk-1_4_0_03 installation problem on Redhat Linux

Status
Not open for further replies.

pat11

Programmer
Aug 23, 2001
3
US
I have jboss-3.0.4_tomcat-4.1.12 application server running on Redhat Linux Advanced Server.I was getting a JBOSS error and read somewhere that it is caused with JDK1.4.1_01 a new version .I was adviced to uninstall that version and install j2sdk-1_4_0_03.I just deleted the JDK1.4.1_01 the new version,removed any references to it in the PATH variable and tried installing j2sdk-1_4_0_03 the older version.
But I am getting an error
" package j2sdk-1.4.1_01-fcs (which is newer than j2sdk-1.4.0_03-fcs) is already installed".

Anybody have an idea why this is happening?Any help would be greatly appreciated.
-pat
 
Have you removed it by 'rpm -e'? If not, then your package database is not consistent. Anyway, you can always use --nodeps and --force arguments.
 
Thanks for the response pupu.
When I try rpm -e I get a message that the "package is not installed".Also I don't want to force installation of the new package.I want to make sure that the old version is completely uninstalled.It's probably the database is not up2date like you said or somewhere in the file system there is a reference to the old version.I have been through some problems in the past when uninstallation is not complete,therefore don't want to install the new package.Any more tips?
Thanks,
-pat
 
If you really want to make sure the old package is removed, try 'rpm -q -p oldpackage.rpm -l' and check listed files. You may IMHO use --force --nodeps without risk; if there are some conflicting files, they will be overwritten or just left to rot without any harm.
 
For less typing try 'rpm -Uvh --oldpackage package.rpm'. Just for tidyness I'd recommend you rebuild your RPM database using 'rpm --rebuilddb' also
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top