Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-5063669

RPM uninstall of Tiger builds before b50 removes GNOME associations.

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not an Issue
    • Icon: P3 P3
    • None
    • 5.0
    • install
    • None
    • generic
    • linux

      When uninstalling the Tiger JRE/JDK RPM on Linux from builds prior to b50 (i.e. the directory name change), the GNOME association files can be removed even if a post b50 Tiger build is still installed.

      This happens when there are only b49- and b50+ RPM builds installed. If there is also a 1.4.2 RPM installed when the b49- build is removed, then this does not occur.

      What happens is that when the RPM uninstall is run (ex.: rpm -e j2re), a check is made to determine if there are any remaining supported JRE/JDK installs. Prior to b50, this test checks for supported installs by looking in /usr/java for directories with the patterns j2re<version> and/or j2sdk<version>, and accepting version 1.4.2 or higher. This check does not recognize the new directory name patterns of jre<version> and jdk<version>, so when these older RPM installations are removed, they incorrectly remove the GNOME association files.

      The GNOME association files are:

          ${GNOMEDIR}/share/mime-info/java-archive.keys
          ${GNOMEDIR}/share/mime-info/java-archive.mime
          ${GNOMEDIR}/share/application-registry/java-archive.applications
          ${GNOMEDIR}/share/mime-info/java-web-start.keys
          ${GNOMEDIR}/share/mime-info/java-web-start.mime
          ${GNOMEDIR}/share/application-registry/java-web-start.applications

      If GNOMEDIR is not set, it defaults to /usr.

            mromanchsunw Michael Romanchuk (Inactive)
            mromanchsunw Michael Romanchuk (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved:
              Imported:
              Indexed: