diff --git a/jdk-updates-jdk18u-jdk-18.0.1+10.tar.gz b/jdk-updates-jdk18u-jdk-18.0.2+9.tar.gz similarity index 99% rename from jdk-updates-jdk18u-jdk-18.0.1+10.tar.gz rename to jdk-updates-jdk18u-jdk-18.0.2+9.tar.gz index e754e114d32cff1b4a283cc02aa8fdf6b3198cd1..daf835535e933df190b26d8b7e3d8acc5c57392e 100644 Binary files a/jdk-updates-jdk18u-jdk-18.0.1+10.tar.gz and b/jdk-updates-jdk18u-jdk-18.0.2+9.tar.gz differ diff --git a/openjdk-latest.spec b/openjdk-latest.spec index 8668c5e701fba2ed1efa5fb5fa85e1ce227d0885..3663aada74c757eb40d2ae04119df85dd0acb8e2 100644 --- a/openjdk-latest.spec +++ b/openjdk-latest.spec @@ -155,7 +155,7 @@ # Used via new version scheme. JDK 18 was # GA'ed in March 2022 => 22.3 %global vendor_version_string 22.3 -%global securityver 1 +%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 10 +%global buildver 9 %global rpmrelease 0 # 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 @@ -1754,6 +1754,9 @@ cjc.mainProgram(arg) %changelog +* Tue July 26 2022 noah - 1:18.0.2.9-0-rolling +- Update to jdk-18.0.2+9 + * Sat May 7 2022 noah - 1:18.0.1.10-0-rolling - Update to jdk-18.0.1+10