The debian java/JRE/JDK situation seems insane.
bookworm (stable) is shipping JRE 17, lots of applications require at least 21, Trixie (next stable) is shipping JRE 21, the the current openJDK JRE version is 23
Most of the time if you search for the errors caused by out of date JRE's you get "just install Oracle JDK" with instructions, but as far as I can squint that comes with some licencing payment obligation. All of this feels like putting your head into a alligators mouth!
(Do not reply "use nix/arch")
@benjojo trixie also has jdk 23, which seems pertinent
@benjojo and 24 as well; 25 hit experimental last week, so it may make it in time for the freeze
@nabijaczleweli Yeah but it seems that Debian Trixie (based on what I can observe with testing) picks openjdk-21 by default, even if higher ones are technically installable.
That being said java is mostly a mystery land to me, so I dunno how big of a deal that is of a default
@benjojo yes, the default jdk package on trixie depends on jdk 21; why this isn't jdk 23 is not obvious to me, but one has to assume it's because either (a) IME java isn't actually backwards-compatible so the default is only updated when the entire archive can be built with jdk 23? or (b) it's following Some openjdk stability policy
@benjojo looks like (a); it's not the /entire/ archive but it's a good proportion of it https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=default-java21;users=debian-java@lists.debian.org (https://lists.debian.org/debian-java/2024/07/msg00001.html); I don't see a similar transition for JDK 23 yet
@benjojo @nabijaczleweli 23 has a lifetime of 6 months, for stable we need one with a lifetime of 2+ years, that’s 21 right now
Other version are only useful if you're developing cutting-edge stuff yourself (and very rarely even in that case).
@nabijaczleweli @benjojo trixie?! sid, but not trixie, unless someone fsckd something up
@nabijaczleweli @benjojo ag except perhaps as unsupported "as is" extra for people who need the newer JRE (security support will cover 21 only, obviously) and without stability guarantee
@mirabilos @benjojo yes, both; and this appears deliberate, with a planned severity bump pre-freeze https://bugs.debian.org/1078198