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

RPM internal names must match the standard bundle file name patterns

    XMLWordPrintable

Details

    • b22
    • linux
    • Verified

    Backports

      Description

        The RPM name for both the JDK and JRE does not match the standard bundle file name, and is not unique across releases. This is critical for OEL support.

        $ rpm -qp --qf "%{NAME}\n" jdk-8u5-linux-x64.rpm 2> /dev/null
        jdk
        $ rpm -qp --qf "%{VERSION}\n" jdk-8u5-linux-x64.rpm 2> /dev/null
        1.8.0_05
        $ cd ../ol6_x86_64_JavaSE7_public
        $ rpm -qp --qf "%{NAME}\n" jdk-7u60-linux-x64.rpm 2> /dev/null
        jdk
        $ rpm -qp --qf "%{VERSION}\n" jdk-7u60-linux-x64.rpm 2> /dev/null
        1.7.0_60

        Attachments

          Issue Links

            backported by

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8052897 RPM internal names must match the standard bundle file name patterns

            • P1 - Blocks development and/or testing work, production could not run.
            • Resolved

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8069605 RPM internal names must match the standard bundle file name patterns

            • P1 - Blocks development and/or testing work, production could not run.
            • Resolved

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8046380 RPM internal names must match the standard bundle file name patterns

            • P1 - Blocks development and/or testing work, production could not run.
            • Closed

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8048915 RPM internal names must match the standard bundle file name patterns

            • P1 - Blocks development and/or testing work, production could not run.
            • Closed

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8050292 RPM internal names must match the standard bundle file name patterns

            • P1 - Blocks development and/or testing work, production could not run.
            • Closed

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8050439 RPM internal names must match the standard bundle file name patterns

            • P1 - Blocks development and/or testing work, production could not run.
            • Closed

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8063608 RPM internal names must match the standard bundle file name patterns

            • P1 - Blocks development and/or testing work, production could not run.
            • Closed

            Activity

              People

                pbhat Pranav Bhat (Inactive)
                jmcglynn Joe Mcglynn (Inactive)
                Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved: