Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: Support Rocky 9 #801

Open
JamesXNelson opened this issue Jan 22, 2024 · 5 comments
Open

Feature Request: Support Rocky 9 #801

JamesXNelson opened this issue Jan 22, 2024 · 5 comments
Assignees

Comments

@JamesXNelson
Copy link

There are both rocky 8 and rhel9 rpm distributed to jfrog, but no rocky9. This makes it harder for consumers who support multiple OS to standardize how we install java (the typical workaround is to dangerously use the rocky 8 repo in rocky 9).

Please build for rocky 9 as well as 8. If this is something a random contributor can do, I'd be happy to help.

@JamesXNelson
Copy link
Author

Any word on whether I can / should contribute this myself?

I'm not exactly familiar w/ building/contributing, but I'm pretty sure I could figure it out from previous PRs for similar things.

@karianna
Copy link
Contributor

See #501 for a longer running issue on this (that'll take some time to untangle)

@sxa sxa removed the PMC-agenda label Jan 31, 2024
@sxa
Copy link
Member

sxa commented Jan 31, 2024

Removing PMC-agenda as we did discuss this last week - apologies that we didn't respond in a comment here. @gdams has an action to find an intermediate way of improving this without us needing to upload multiple versions to the artifactory server that hosts the packages - specifically he plans to identify and prototype using some form of symlink equivalent for now.

Also to be clear there is no difference in the rpms across distributions - we do not build specifically for each RHEL-like distrubution. You can just set your repository to 8 instead of 9 as an intermediate solution and it will do the right thing (The issue that @karianna referred to above will involve pointing everyone at a distribution-neutral location for the repository when it is implemented)

@sxa sxa assigned gdams Feb 8, 2024
@sxa
Copy link
Member

sxa commented Feb 8, 2024

Assigning George as he's looking at experimenting with short term options for this

@JamesXNelson
Copy link
Author

fwiw, a single distribution-neutral location would be awesome.

Our mirror of your repos has to maintain 7 different sources of the same files, and I know artifactory hosting is not cheap, so thanks for looking into this!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants