that test is wrong in any case.
call java -client|-zero|-server -version and parse the output
On 15.08.24 09:58, Sébastien Villemot wrote:
Le jeudi 15 août 2024 à 09:23 +0200, Matthias Klose a écrit :
Control: severity -1 serious
armel is still a release architecture.
Ok, I see, this bug exists because the default JDK has recently been
switched to OpenJDK 21, which has a different set of default JVMS. It
would have been useful to give that element of context.
Also, you did not answer to my question.
Thanks,
On 13.08.24 09:56, Sébastien Villemot wrote:
Control: severity -1 important
Control: reassign -1 octave 9.2.0-2
Control: affects -1 + octave-io
Control: retitle -1 JVM detection is incorrect on archs where the default is the
"zero" JVM
Le lundi 05 août 2024 à 13:53 +0200, Matthias Klose a écrit :
Package: src:octave-io
Version: 2.6.4-3
Severity: serious
Tags: sid trixie
The package assumes that the default JVM is the server VM. Please don't
make such an assumption.
Failing autopkg tests on all architectures where zero is the default JVM.
[...]
132s autopkgtest [19:09:49]: test xls-poi: [-----------------------
133s Testing POI interface for XLS...
134s error: /usr/lib/jvm/default-java/lib/server/libjvm.so: failed to load
134s Incompatible version or missing dependency?
134s /usr/lib/jvm/default-java/lib/server/libjvm.so: cannot open shared
object file: No such file or directory
134s error: called from
134s javaclasspath at line 66 column 16
134s getinterfaces at line 76 column 11
134s xlsopen at line 204 column 18
134s xlsfinfo at line 127 column 7
134s testhelper at line 12 column 5
Downgrading the severity because as far as I can tell, this problem
does not affect any release architecture. On debci, only loong64 seems
affected.
Also reassigning to octave because this is where the choice of the
default JVM is done.
Actually there is no assumption that the server JVM is the default one
on every architecture. There is a test which decides whether to use the
client or server JVM, see:
https://salsa.debian.org/pkg-octave-team/octave/-/blob/debian/latest/debian/rules?ref_type=heads#L15
It seems that this test is not (or no longer) correct. Can you possibly
tell us what is the correct test to determine the default JVM on a
given architecture?
Best wishes,
