Cached JDK25 temurin is broken, the noncached version worked well.

[sblantipodi]

As title.

Nothing changed from my side if not that setup-java action is now using a cached JDK25 temuring.

this is the build that does not use the cache
https://github.com/sblantipodi/firefly_luciferin/actions/runs/18237358040/job/51933513441

this is the one that uses the cached jdk
https://github.com/sblantipodi/firefly_luciferin/actions/runs/18277118242/job/52031677477

as you can see, the cached version is broken.

Can you fix it please? :)

[mvsoder]

You can delete your own caches if that is the problem. Under the Actions tab for your project, cache management is the first option under Management on the left-hand side.

[aparnajyothi-y]

Hello @sblantipodi, Thank you for cresting this issue and we will look into it :)

[sblantipodi]

@mvsoder

@aparnajyothi-y ok thanks, please let us know your findings, thanks.

[jerboaa]

I'll add what I've said in adoptium/installer#1274. Temurin 24+ enables JEP 493 (i.e. uses the run-time image for jlink and doesn't use JMODs by default, though you still can but needs extra installation). This reduces the size of the JDK for most installations.

The failing (cached) setup fails due to:

Error: /usr/lib/jvm/temurin-25-jdk-amd64/lib/ct.sym has been modified

The question is how that file got installed. It's obviously been modified to the verbatim tarball. Note that this file is a glorified jar file and some Linux installers do post-processing on jar files for one reason or another. Maybe that is the root cause, not sure. If that is being done here, then the sha512sum of the file differs from the version that was in the JMODs where the image got created from. To diagnose one could compare the hashsums of lib/ct.sym from the cached version to the version from the JMODs. This blog has some details how to retrieve the JMODs separately and in general how JEP 493 works.

[mvsoder]

I ended up here with a similar problem as @sblantipodi, just a different file:

jlink failed with: Error: /usr/lib/jvm/temurin-25-jdk-amd64/lib/jrt-fs.jar has been modified

What is strange is that it worked for a few days after the Java 25 release, then started having this issue. I can run jpackage locally with a clean temurin JDK so it appears there is something happening between the Temurin JDK resources and the GitHub runner that we don't get much control over.

An example run if it helps: https://github.com/avereon/xenon/actions/runs/18383519044/job/52376276671

[Til7701]

I have the same problem as mvsoder. It broke somewhere between the 2nd and 6th October. On the 2nd building with Temurin JDK 25 worked perfectly. Nothing changed in between those two dates in my setup or dependencies.

[mduft]

Same problem here:

Error: /usr/lib/jvm/temurin-25-jdk-amd64/lib/jrt-fs.jar has been modified

Also my actions have zero caches, so I doubt that I can fix this somehow...

Edit: "or course" ( xD ) everything works locally without any issue. Also the issue only affects Linux x64. The same builds (locally and on GH actions) run fine for Windows x64 and Linux Aarch64 (which is interesting IMHO).

[Til7701]

See the adoptium installer repo issue linked above. I did some more testing and found this is not a setup-java issue, but is a problem with how the deb package is built for the temurin JDK.

[brunoborges]

@aparnajyothi-y

any update on this?