The EPEL Guidelines and Policy[1] was recently revised to allow EPEL modules to have the same packages as those in RHEL as long as the module wasn't enabled by default, and the user had to specifically enable that module and stream. The updated policies allowed the modules to have both the same module name and stream name as the RHEL modules. Unfortunately, if you do this, and someone enabled that module and stream, then both the RHEL and the EPEL modules are enabled. And when that happens, dnf will choose whichever packages have the higher NVR. During the discussions, it was said that this should never happen. That if it was going to happen, that RHEL should take over the module.[3] But, this idea was never put into the policy. And it has happened (two epel modules with the same module and stream name as the RHEL modules), and now we are cleaning up the mess. I am proposing a change to one sentence, that will state that modules with the same name as RHEL modules cannot have the same stream name as the RHEL modules. Only this line is different "If the RHEL package is in a RHEL module, then the EPEL module must have the same name as the RHEL module, and a different stream name than the RHEL module." Troy [1] - https://fedoraproject.org/wiki/EPEL/GuidelinesAndPolicies#Policy [2] - https://pagure.io/epel/issue/104 [3] - https://lists.fedoraproject.org/archives/list/epel-devel@xxxxxxxxxxxxxxxxxxxxxxx/message/HQHFQHMUMQSE2VSQMC7Q2VYAGSDO6P7E/ _______________________________________________ epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to epel-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@xxxxxxxxxxxxxxxxxxxxxxx
