Package Details: jdk17-temurin 17.0.13.u11-1

Git Clone URL: https://aur.archlinux.org/jdk17-temurin.git (read-only, click to copy)
Package Base: jdk17-temurin
Description: Temurin 17 (OpenJDK 17 Java binaries by Adoptium, formerly AdoptOpenJDK)
Upstream URL: https://adoptium.net/
Licenses: custom
Provides: java-environment, java-environment-openjdk, java-runtime, java-runtime-headless, java-runtime-headless-openjdk, java-runtime-openjdk, jdk-openjdk, jdk17-openjdk, openjdk-src, openjdk17-src
Submitter: Bevan
Maintainer: Bevan
Last Packager: Bevan
Votes: 20
Popularity: 0.061308
First Submitted: 2022-04-20 19:27 (UTC)
Last Updated: 2024-10-18 06:45 (UTC)

Required by (2841)

Sources (4)

Latest Comments

TheRainbowSheep commented on 2024-04-17 06:31 (UTC)

@Bevan Thanks!

Bevan commented on 2024-04-16 16:14 (UTC)

TheRainbowSheep: You are right. This also affects jdk11-temurin. I'll push updates to both of them soon.

TheRainbowSheep commented on 2024-04-15 09:40 (UTC)

I think that due to the change in JDK/JRE policy (https://archlinux.org/news/incoming-changes-in-jdk-jre-21-packages-may-require-manual-intervention/), jre*-openjdk and jre*-openjdk-headless should be removed from provides, to prevent conflicts with jdk17-openjdk.

HarmfulBreeze commented on 2023-03-07 10:37 (UTC)

@Bevan thank you!

Bevan commented on 2023-03-06 22:31 (UTC)

@HarmfulBreeze: This was suggested in a comment on jdk-temurin because the stripping causes issues with some debugging tools. It's also an open request on Arch's official openjdk packages: https://aur.archlinux.org/packages/jdk-temurin#comment-904494

I think for these packages !strip makes sense because the packages are meant as a convenient way to install the Temurin binary distribution and we should not mess with the binaries. The package size is only increased by 4-5 MB, so by around 1.5%.

HarmfulBreeze commented on 2023-03-06 21:53 (UTC)

Hi, why disable the stripping of the binaries? (just wondering)

Equiphract commented on 2022-08-10 17:11 (UTC)

That seems to have been the problem, the service has not ran since then. To solve this issue I executed mandb as root and after that I was able to access Java's man page using man java. Thanks for the hint! I was not even aware that man-db.timer and man-db.service existed...

Bevan commented on 2022-07-31 19:25 (UTC)

You should be able to access them by adding -temurin17 as suffix, e.g.:

$ man java-temurin17

I'm not entirely sure why man java usually works but it looks like that feature depends on an up-to-date mandb index. That is updated once per day by man-db.timer which triggers man-db.service. Can you check if that service ran since you installed this package?

Equiphract commented on 2022-07-31 13:02 (UTC)

I am not able to access the man pages for java, javac etc. with this package:

$ man java
No manual entry for java