Release upgrade using "ca-certificates-java" package from xenial-proposed (part of the current SRU) and upgraded to "ca-certificates-java" from zesty-proposed during the release upgrade.
To simulate the situation once both packages will land in $RELEASE-updates.
The upgrade went well installing "ca-certificates-java" version "20161107ubuntu1" which now depend on openjdk-8 instead of -7-, fixing the trigger failure.
[Xenial]
ii ca-certificates-java 20160321ubuntu1 <== Currently in xenial-proposed
ii openjdk-8-jre-headless:amd64 8u151-b12-0ubuntu0.16.04.2
[Zesty]
ii ca-certificates-java 20161107ubuntu1 <== Currently in zesty-proposed
ii openjdk-8-jre-headless:amd64 8u151-b12-0ubuntu0.17.04.2
[JUSTIFICATION ZESTY] ------- ------- -
-------
Release upgrade using "ca-certificate s-java" package from xenial-proposed (part of the current SRU) and upgraded to "ca-certificate s-java" from zesty-proposed during the release upgrade.
To simulate the situation once both packages will land in $RELEASE-updates.
The upgrade went well installing "ca-certificate s-java" version "20161107ubuntu1" which now depend on openjdk-8 instead of -7-, fixing the trigger failure.
[Xenial] -java 20160321ubuntu1 <== Currently in xenial-proposed 8-jre-headless: amd64 8u151-b12- 0ubuntu0. 16.04.2
ii ca-certificates
ii openjdk-
[Zesty] -java 20161107ubuntu1 <== Currently in zesty-proposed 8-jre-headless: amd64 8u151-b12- 0ubuntu0. 17.04.2
ii ca-certificates
ii openjdk-
- Eric