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

RPM package name has changed (not backward-compatible) and contains versio

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Fix
    • Icon: P3 P3
    • 8u40
    • 8u20
    • install
    • x86
    • linux_redhat_6.0

      FULL PRODUCT VERSION :


      ADDITIONAL OS VERSION INFORMATION :
      Linux kii-static 3.2.22-35.60.amzn1.x86_64 #1 SMP Thu Jul 5 14:07:24 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

      EXTRA RELEVANT SYSTEM CONFIGURATION :
      Happens in any RPM-based system, not specific

      A DESCRIPTION OF THE PROBLEM :
      The rpm package doesn't get upgraded from 1.8u11 to 1.8u20, because the package name changed in latest release in a way that seems unintended to me. Old package name was "jdk" (with 1.8.0_11-fcs version), whereas new package name is "jdk1.8.0_20" (with 1.8.0_20-fcs version). With this change, all the tooling and automation that anyone has for managing deployments with package "jdk" is therefore rendered unusable.

      REGRESSION. Last worked in version 8u11

      ADDITIONAL REGRESSION INFORMATION:
      #Before trying to upgrade:
      $ rpm -qa | grep jdk
      jdk-1.8.0_11-fcs.x86_64


      STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
      # Check current status
      $ rpm -qa | grep jdk
      jdk-1.8.0_11-fcs.x86_64

      # Download jdk 1.8u20 x86_64 rpm
      # Try to upgrade to jdk 1.8u20
      $ sudo rpm -Uvh jdk-8u20-linux-x64.rpm
      # Check
      $ rpm -qa | grep jdk:
      jdk1.8.0_20-1.8.0_20-fcs.x86_64
      jdk-1.8.0_11-fcs.x86_64



      EXPECTED VERSUS ACTUAL BEHAVIOR :
      EXPECTED -
      I would expect that JDK 1.8.0_20 's package name is still "jdk", and then rpm -Uvh would upgrade the package.
      ACTUAL -
      JDK 1.8.0_20 can't upgrade 1.8.0_11

      REPRODUCIBILITY :
      This bug can be reproduced always.

            pbhat Pranav Bhat (Inactive)
            webbuggrp Webbug Group
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: