Jochen Sprickerhof
2019-04-14 10:40:03 UTC
Reply
PermalinkOn Sun, 28 Oct 2018 22:53:56 +0100 =?UTF-8?Q?Gero_M=c3=bcller?=
This bug was apparently "fixed" in version 20170929 but then the change
was reverted in 20170930. Both versions were marked as fixed. The
severity is still "serious" and it is not clear from reading the
changelog whether version 20170930 addresses the problem
@Matthias
Can this bug report be closed or should it be reassigned to OpenJDK? You
reverted the previous fix here
https://salsa.debian.org/java-team/ca-certificates-java/commit/53651f7939e6f35694ee31e5ef0376f1bfce7e55
I wasn't able to reproduce the problem withPackage: ca-certificates-java
Version: 20170531+nmu1
On armhf the server JVM is not available. But the postinst script
assumes so and uses it to setup a temporary configuration in
/etc/java-8-openjdk/jvm-armhf.cfg
The installation of openjdk-8-jre-headless therefore fails!
[...]Version: 20170531+nmu1
On armhf the server JVM is not available. But the postinst script
assumes so and uses it to setup a temporary configuration in
/etc/java-8-openjdk/jvm-armhf.cfg
The installation of openjdk-8-jre-headless therefore fails!
This bug was apparently "fixed" in version 20170929 but then the change
was reverted in 20170930. Both versions were marked as fixed. The
severity is still "serious" and it is not clear from reading the
changelog whether version 20170930 addresses the problem
@Matthias
Can this bug report be closed or should it be reassigned to OpenJDK? You
reverted the previous fix here
https://salsa.debian.org/java-team/ca-certificates-java/commit/53651f7939e6f35694ee31e5ef0376f1bfce7e55
openjdk-11-jre-headless:armhf.
Can this be closed?
Cheers Jochen