Your message dated Tue, 23 Feb 2021 15:19:00 +0100
with message-id <4fb58909-b756-4d6c-d598-b0d6eca6e...@debian.org>
and subject line Re: ca-certificates-java: Wrong jvm options for armhf
has caused the Debian Bug report #912187,
regarding Wrong jvm options for armhf
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
912187: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912187
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: 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!
Running hooks in /etc/ca-certificates/update.d...
Error: missing `server' JVM at
`/usr/lib/jvm/java-8-openjdk-armhf/jre/lib/arm/server/libjvm.so'.
Please install or use the JRE or JDK that contains these missing components.
E: /etc/ca-certificates/update.d/jks-keystore exited with code 1.
done.
Errors were encountered while processing:
ca-certificates-java
openjdk-8-jre-headless:armhf
openjdk-9-jre-headless:armhf
E: Sub-process /usr/bin/dpkg returned an error code (1)
Please use the client defaults instead (jvm.cfg-client_default from the
openjdk sources):
-client KNOWN
-server ALIASED_TO -client
Thanks!
--- End Message ---
--- Begin Message ---
On Mon, 28 Jan 2019 20:22:13 +0100 Markus Koschany <a...@debian.org> wrote:
> 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
The code dealing with creating temporary jvm config files is gone.
Andreas
--- End Message ---
