Am 29.06.20 um 17:16 schrieb Troy Dawson:
Hi Felix, I wasn't offended by your tone. I felt the same way when I saw this on Friday. Although dnf sees these as two different modules, since they have same name and stream, dnf lumps them together. When that happens, dnf uses the packages with the highest Name-Version-Release (NVR). In this case, unfortunately, the EPEL package NVR's are higher, and thus dnf is choosing them. This is a known behavior. We were hoping that EPEL module maintainers would avoid these conflicts. But as I said earlier, mistakes happen. When we looked last week, we saw that there were now three modules with the same module and stream names as RHEL modules. Only one was enabled by default, but clearly something needed to be done. We (The EPEL Steering Committee) are working on not only a policy change, but hopefully a solution that will keep this from happening in the future. https://pagure.io/epel/issue/104 I've put this same information in your bugzilla, but I wanted to also put it here, so people don't have to go to the bug to see this information.
For those that have an automated update process in place. What steps are needed to revert this mistake? -- Leon _______________________________________________ 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
