Sometimes policies are not enough.
It is currently possible for a packager to accidentally release a module in EPEL with the same module name and stream name as a module in RHEL. Due to an accident, we have seen how easy it is to accidentally do this.
Create a build / update / release procedure that prevents EPEL modules from having the same module name and stream name as RHEL modules.
There has already been discussion about automatically changing the stream names, such as adding -epel to the end of them all. (ie: 12-epel) This was ruled out because it would cause the inter-module dependencies to be unpredictable.
Current Proposal
At the last EPEL Steering Committee meeting it was agreed that we would try to find a solution through bodhi and/or gating.
Make it so that either bodhi wouldn't accept updates if there was a conflict, or perhaps allow the update to be created but then fail gating tests.
In the end, a solution wasn't able to be found and/or implemented. Since we are retiring modules in EPEL8, I am closing this issue.
Metadata Update from @tdawson: - Issue close_status updated to: Unable to Fix - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.