Draft: openjdk(11-23): security upgrades for oracle CPU october 2024
1 unresolved thread
Merge request reports
Activity
Filter activity
added 8 commits
-
057ac25b...1d5b8d38 - 3 commits from branch
alpine:master
- 87c18383 - community/openjdk11: security upgrade to 11.0.25
- 947e979f - community/openjdk17: security upgrade to 17.0.13
- 34a52e97 - community/openjdk21: security upgrade to 21.0.5
- 09abec0a - testing/openjdk22: upgrade to 22.0.2
- 1f29ef86 - testing/openjdk23: security upgrade to 23.0.1
Toggle commit list-
057ac25b...1d5b8d38 - 3 commits from branch
added 106 commits
-
1f29ef86...3c245c8b - 101 commits from branch
alpine:master
- d08b5df5 - community/openjdk11: security upgrade to 11.0.25
- 527337fd - community/openjdk17: security upgrade to 17.0.13
- af079f48 - community/openjdk21: security upgrade to 21.0.5
- 7d5d8c38 - testing/openjdk22: upgrade to 22.0.2
- 6deaa700 - testing/openjdk23: security upgrade to 23.0.1
Toggle commit list-
1f29ef86...3c245c8b - 101 commits from branch
mentioned in merge request !74045 (merged)
mentioned in merge request !74046 (merged)
mentioned in merge request !74047 (merged)
mentioned in merge request !74048 (merged)
mentioned in merge request !74049 (merged)
OpenJDK2X started placing
libjvm.so
in different subdirectories based on the variant built. Before this it always went into theserver
dir even when building Zero VM, now it goes intozero
instead (for Loongarch).There is a new abuild 3.14.0 requirement that abuild must always be able to determine the location of such
*.so
files, so you will need to adjustldpath=
(probably use$_jvm_variant
instead of a hardcodedserver
(only for OpenJDK2X)).
Please register or sign in to reply