JDK-5044137 : Error Messages after uninstall of JRE on RH9
  • Type: Bug
  • Component: install
  • Sub-Component: install
  • Affected Version: 5.0
  • Priority: P2
  • Status: Closed
  • Resolution: Fixed
  • OS: linux_redhat_9.0
  • CPU: x86
  • Submitted: 2004-05-07
  • Updated: 2004-06-22
  • Resolved: 2004-06-15
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other
5.0 b56Fixed
Related Reports
Relates :  
JDK-5063681 - GNOME association files can be left behind after RPM uninstall...
Relates :  
JDK-5063669 - RPM uninstall of Tiger builds before b50 removes GNOME associations.
Description
1. Install released JRE (j2re-1.5.0-beta) (rpm)
2. Install JRE Build50      (jre-1.5.0-beta2) (rpm) 
3. rpm -e j2re-1.5.0-beta2
4. rpm -e jre-1.5.0-beta2
Error Messages displayed 
rm: cannot remove `/usr/share/mime-info/java-web-start.keys': No such file or directory
rm: cannot remove `/usr/share/mime-info/java-web-start.mime': No such file or directory
rm: cannot remove `/usr/share/application-registry/java-web-start.applications': No such file or directory
rm: cannot remove `/usr/share/mime-info/java-archive.keys': No such file or directory
rm: cannot remove `/usr/share/mime-info/java-archive.mime': No such file or directory
rm: cannot remove `/usr/share/application-registry/java-archive.applications': No such file or directory

###@###.### 2004-05-07
###@###.### 2004-06-22
Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: tiger-rc FIXED IN: tiger-rc INTEGRATED IN: tiger-b56 tiger-rc VERIFIED IN: tiger-rc
13-09-2004
EVALUATION These error messages are due to the new directory names related to the name change. Beta 1 was released before we even knew there was going to be a name change, it does not know to look for a JRE/JDK in the new directories. Because of this, when Beta 1 is removed, it removes several GNOME files that are still in use by the newer Beta 2 install. There is no way to fix Beta 1, since it is out the door. All builds since b50 have the appropriate code to test for both the old and new JRE/JDK directory names when uninstalling, so there is no change required there. However, it wouldn't hurt to make sure the GNOME files actually exist before trying to remove them. ###@###.### 2004-06-02
02-06-2004
SUGGESTED FIX Add a test for each GNOME files existance before removing it. Also use the -f argument to prevent any unnecessary warnings. ###@###.### 2004-06-02
02-06-2004