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, -- ⢀⣴⠾⠻⢶⣦⠀ Sébastien Villemot ⣾⠁⢠⠒⠀⣿⡁ Debian Developer ⢿⡄⠘⠷⠚⠋⠀ https://sebastien.villemot.name ⠈⠳⣄⠀⠀⠀⠀ https://www.debian.org
signature.asc
Description: This is a digitally signed message part
