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

Enable EPEL10 support #362

Open
mikelolasagasti opened this issue Oct 16, 2024 · 3 comments
Open

Enable EPEL10 support #362

mikelolasagasti opened this issue Oct 16, 2024 · 3 comments

Comments

@mikelolasagasti
Copy link
Contributor

EPEL10 is already available, would be great to have it enabled in Koschei to start tracking packages.

@carlwgeorge
Copy link

To clarify slightly, EPEL 10 is in a "soft launch" period to give packagers a bit more time to prepare their builds. It hasn't officially launched yet.

https://discussion.fedoraproject.org/t/epel-10-status-update/124549

I definitely agree it would be nice to have EPEL 10 in Koschei before we do the launch announcement.

@decathorpe
Copy link

One question that might be good to answer before this is done - which epel10 should be targeted by koschei?

  • epel10 branch against CentOS Stream 10?
  • epel10_0 branch against RHEL 10.0?
  • epel10_1 branch against RHEL 10.1?
  • ...
  • all of the above?

@carlwgeorge
Copy link

The core principle of the EPEL 10 changes is to integrate with RHEL minor versions, including CentOS Stream as the leading minor version. In some places we have to leave out the minor version, such as the leading distgit branch and the leading repo URL, but where we can it makes sense to use the minor version, such as in the koji tags and the bodhi releases. So I think the koschei targets should be EPEL-10.0, then later add EPEL-10.1, and so on.

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

3 participants