openjdk team mailing list archive

[Tiago Stürmer Daitx <1771815@xxxxxxxxxxxxxxxxxx>]

Using the test case I confirm that the PATH and JAVA_HOME are now
working as expected and no longer set to invalid values.

The test cases in bug 1771363 and bug 1769013 are also working
correctly.

-- 
You received this bug notification because you are a member of OpenJDK,
which is subscribed to ca-certificates-java in Ubuntu.
https://bugs.launchpad.net/bugs/1771815

Title:
  Please merge ca-certificates-java 20180516 (main) from Debian unstable
  (main)

Status in ca-certificates-java package in Ubuntu:
  Fix Released
Status in ca-certificates-java source package in Bionic:
  Fix Committed
Status in javatools package in Debian:
  Fix Released

Bug description:
  [Original Merge Description]
  There's a new ca-certificates-java package in debian unstable versioned 20180516 which conflicts with Ubuntu's delta in cosmic, version 20180413ubuntu1 [1], and requires a merge.

  The following changes should be kept:
  1) debian/control: Bump javahelper build dependency.
  2) debian/rules: Replace javac arguments '-source 1.7 -target 1.7' with '--release 7'
  as, per JEP-247, it also takes care of setting the right -bootclasspath argument.

  We can only propose both 1) and 2) to Debian after Debian merges
  895230 [2].

  References:
  [1] https://merges.ubuntu.com/main.html?query=ca-certificates-java
  [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895230

  
  [Impact]
  This merge brings fixes for:
  1. debian/jks-keystore.hook.in and debian/postinst.in so the PATH is only updated when a valid JVM is found - previously an invalid path was set, which had no side effect.
  2. the same fix carried by by bug 1769013, which removed an uneccessary jvm config file
  3. the fix from bug 1771363, which converted keystores in PKCS12 format to JKS

  
  [Test Case]
  Same test cases as described in bug 1771363 and bug 1769013.

  Additionally to that one can check that the jks-keystore hook and the
  postinst script from ca-certificates-java no longer causes an invalid
  PATH and JAVA_HOME to be set - this had no side effect, as those were
  set to an invalid value the java binary was search in the remaining
  PATH.

  
  [Regression Potential]
  Besides the regressions discussed in bug 1771363 and bug 1769013 no other regression is expected.

  Not setting PATH/JAVA_HOME or setting them to an invalid value will
  have the same effect in the 'java' calls for both the jks-keystore
  hook and the postinst script: an existing java binary in the remaining
  PATH is called.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ca-certificates-java/+bug/1771815/+subscriptions