Every few months an epel 8 module get's built that has the same name and version number as the modules in RHEL. When this happens dnf likes to combine the two modules, causing problems.
Looking at the various modules that have done this in the past, all of them have been a module maintainer building for "everything". When they do this, they build for not only all Fedora releases, but also all EPEL releases.
This issue is for investigation, and possibly implementation, of a way to fix this.
My initial idea to fix this is to have the "everything" builds, only do Fedora releases, and not epel releases. I do not know how easy or hard that will be, or the impact of it. So this has to be researched before we know if this is a way forward or not.
Maybe it would be better to move EPEL-modularity from the Fedora build system over as either a seperate project or different task to the CentOS Build Service (cbs). This way modules can depend directly on CentOS Stream 8 and CentOS Stream 9 modules so PHP and other items can be built.
I fear that trying to keep EPEL modularity 'working' in Fedora Build System is going to become harder and harder over time and it would be better to look at this in the same way as Playground.. an experiment that was tried, but it would be better done elsewhere long term.
Another side effect is epel-modular packages that are uninstallable, see rhbz#2042653.
I agree with Smooge, I have no problem sunsetting epel-modular, or at least never starting it for el9.
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.