!5 upgrade to jdk21.0.2-ga
From: @kuenking111 Reviewed-by: @alexanderbill Signed-off-by: @alexanderbill
This commit is contained in:
commit
d63d0beab0
Binary file not shown.
@ -155,7 +155,7 @@
|
||||
# Used via new version scheme. JDK 19 was
|
||||
# GA'ed in March 2022 => 22.3
|
||||
%global vendor_version_string BiSheng
|
||||
%global securityver 0
|
||||
%global securityver 2
|
||||
# buildjdkver is usually same as %%{majorver},
|
||||
# but in time of bootstrap of next jdk, it is majorver-1,
|
||||
# and this it is better to change it here, on single place
|
||||
@ -175,7 +175,7 @@
|
||||
%global origin_nice OpenJDK
|
||||
%global top_level_dir_name %{origin}
|
||||
%global minorver 0
|
||||
%global buildver 35
|
||||
%global buildver 12
|
||||
%global rpmrelease 1
|
||||
# priority must be 8 digits in total; up to openjdk 1.8, we were using 18..... so when we moved to 11, we had to add another digit
|
||||
%if %is_system_jdk
|
||||
@ -1772,6 +1772,9 @@ cjc.mainProgram(arg)
|
||||
|
||||
|
||||
%changelog
|
||||
* Mon Jan 22 2024 kuenking111 <wangkun49@huawei.com> - 1:21.0.2.12-0
|
||||
- upgrade to jdk21.0.2-ga
|
||||
|
||||
* Fri Jan 5 2024 kuenking111 <wangkun49@huawei.com> - 1:21.0.0.35-2
|
||||
- add add-downgrade-the-glibc-symver-of-log2f-posix_spawn.patch
|
||||
- add add-downgrade-the-glibc-symver-of-memcpy.patch
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user