Hi, The packages java-latest-openjdk(-portable) was just pushed to EPEL 10.0 via this update https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-eb6bb14364 however not to EPEL 10.1. This is unexepected, as it means it will be installable in RHEL 10.0 now, but won't be in RHEL 10.1 in 6 months, or in CentOS stream 10 right now. Please push the packages java-latest-openjdk(-portable) to both EPEL 10.0 & 10.1 (and in the future, all active EPEL point releases).
Friendly ping for this request.
I tried to fix this myself, unfortunately it needs some tag magic I am not familiar with, the packager who will take care of this is coming back from his vacation next week. Sorry for the delay.
With my (quite small) knowledge, you have two ways to fix this: either rebuild the packages for EPEL 10.1 (by building the "epel10" branch of your repositories), either ask some special procedure like the Haskell folks did here: https://pagure.io/releng/issue/12722 to tag some EPEL 10.0 packages into 10.1. Still, you might face similar issues with upcoming updates (I am not sure if you really want to update both 10.0 & 10.1, or only the very latest EPEL 10 point release), so there might be some longer term changes required depending on what you wish. FYI, Carl is in CC of this bug, and can help you figuring out the best strategy here.
Unfortunately, JDK packages are built in two stages - first we build portable binaries for the oldest epel (e.g. https://koji.fedoraproject.org/koji/buildinfo?buildID=2699658), those are then apparently being tagged by some special OpenJDK tag (e.g. el10.0-openjdk), but there is no such tag for 10.1 and I am not sure where to get one. After I somehow manage to tag the portable build into 10.1 and it appears in the buildroot, then I can rebuild the actual JDK rpms using the tagged build in koji. I don't think the special tagging of epel10 into 10.1 is necessary, once jvanek is back, he will help me solve this.
Is there any documentation for this special openjdk build/tag workflow? I've looked over the releng ticket that resulting in el10.0-openjdk being created [0], but it's still not clear to me. We will probably need to account for this in the EPEL mass branching process [1]. I'm also unclear on why a "latest" package exists at all. At face value it doesn't seem like it can follow the Fedora or EPEL updates policies [2][3]. Was this ever approved by FESCo or the EPEL Steering Committee? [0]: https://pagure.io/releng/issue/12410 [1]: https://docs.fedoraproject.org/en-US/infra/release_guide/sop_epel_minor_mass_branching/ [2]: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/#stable-releases [3]: https://docs.fedoraproject.org/en-US/epel/epel-policy-updates/
I don't know, I haven't found any, but I wasn't looking very hard to be honest. Jiri is coming back from his vacation next week, he can answer any of your questions then. Or is there some tight deadline we need to meet? Latest packages exist, because it contains the newest STS version of OpenJDK - which has a support span of 6 months and it would be high maintenance to have a separate package for every STS, so we have this rolling release and then branch out any LTS into a separate packages. We included this STS package in EPEL, because there is no equivalent package in RHEL (because it is STS). As for the JDK packages themselves, any significant changes to our build process, which is I admit, not standard, were usually negotiated with FESCO and went through the usual process: Here is the proposal explaining the portable->rpms build process: https://fedoraproject.org/wiki/MoveFedoraJDKsToBecomePortableJDKs And some relevant proposals: https://fedoraproject.org/wiki/Changes/Java25AndNoMoreSystemJdk https://fedoraproject.org/wiki/Changes/ThirdPartyLegacyJdks
> Jiri is coming back from his vacation next week, he can answer any of your questions then. Or is there some tight deadline we need to meet? Short answer: no, there is no tight deadline. I can definitely wait couple of weeks to get the EPEL 10.1 packages. This ticket (and the "latest" JDK) will be my future workaround for another ticket I have opened affecting only LTS version (https://bugzilla.redhat.com/show_bug.cgi?id=2358032) as I wish to upgrade all our Jenkins images to RHEL 10 now that RHEL 10 repos were opened. I will use RHEL beta + EPEL 10.1 for now, as we do miss far too many packages in EPEL 10.0 which are available in EPEL 10.1 (I started building my missing packages too late).
(@Carl: of course it's noted I should not use beta stuff, as we discussed together with Brian, I will do it only until you officially release RHEL 10.1 next November).
hi! We are building the portable jdk once, in oldest live Fedora/epel, and then we are tagging it to elX-openjkdk and fX-openjdk tags, where we build the rpms, and the rpms are then corretly tagged into fC/epelX taga amd fromt here is done update. See; https://fedoraproject.org/wiki/Changes/BuildJdkOncePackEverywhere#shortuct_of_shortcuts For fedoras and epel8 and 9 it wrks fine. For epel10 issues were sicne origin: https://pagure.io/releng/issue/12410 TBH, I'm not sure how to proceed with it. It seems that due to tags inheritance, I can not do anything, before the epel10.1 branch exists, because simple epel10 branch/buildroot ahve no corresponding epel10-openjdk, becasue epel10 is rolling target. I had tried to fill https://pagure.io/releng/issue/12741 to enable building of 10.1 ahead of time.
Hello. I have a buildroot and build seems to be in progres...
here you go: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-2ecf028b7c