Description of problem: EPEL Modular provides an application stream for NGINX 1.20, the current stable branch for NGINX. AppStream also contains a stream for NGINX 1.20, which gets replaced by the one provided by EPEL modular. EPEL packages should never replace or conflict with packages in Enterprise Linux distributions. Possible solution: Rename the NGINX 1.20 stream in EPEL Modular to stable or 1.20-epel to avoid replacing the stream provided in the AppStream repository.
I can confirm this bug. Without epel-modular enabled: ======================================================================================================================================= Package Architecture Version Repository Size ======================================================================================================================================= Installing: nginx x86_64 1:1.20.0-2.module+el8.5.0+12317+1b759a19 appstream 592 k Installing dependencies: nginx-filesystem noarch 1:1.20.0-2.module+el8.5.0+12317+1b759a19 appstream 25 k openssl x86_64 1:1.1.1k-4.el8 baseos 708 k redhat-logos-httpd noarch 84.5-1.el8 baseos 29 k Transaction Summary ======================================================================================================================================= With epel-modular enabled: ======================================================================================================================================= Package Architecture Version Repository Size ======================================================================================================================================= Installing: nginx x86_64 1:1.20.1-6.module_el8+12928+992082b2 epel-modular 599 k Installing dependencies: nginx-filesystem noarch 1:1.20.1-6.module_el8+12928+992082b2 epel-modular 26 k openssl x86_64 1:1.1.1k-4.el8 baseos 708 k redhat-logos-httpd noarch 84.5-1.el8 baseos 29 k Installing weak dependencies: logrotate x86_64 3.14.0-4.el8 baseos 86 k Transaction Summary =======================================================================================================================================
Thanks for reporting this! The question is whether there is even value in building the 1.20 stream for EPEL Modular if it is also provided in AppStream. The EPEL Modular 1.20 tracks along with the Fedora 1.20 stream that supports building external modules, which I believe the AppStream version does not. But I would consider this a corner case. I'm not sure of the implications of simply excluding EPEL from the module build. I will get some guidance on this and report back with my intended course of action.
(In reply to Felix Kaechele from comment #2) > Thanks for reporting this! > > The question is whether there is even value in building the 1.20 stream for > EPEL Modular if it is also provided in AppStream. The EPEL Modular 1.20 > tracks along with the Fedora 1.20 stream that supports building external > modules, which I believe the AppStream version does not. But I would > consider this a corner case. > > I'm not sure of the implications of simply excluding EPEL from the module > build. I will get some guidance on this and report back with my intended > course of action. The AppStream version is already built with the "--with-compat" flag enabled in order to support third-party dynamic modules. If you're talking about the nginx-mod-devel subpackage, that should make it into the next minor RHEL 8 release. It's currently in Centos 8 Stream. Since streams in AppStream are already following its upstream application lifecycles (for the most part), it might not make sense for EPEL to provide an nginx-stable stream. Hope this info helps.
> The question is whether there is even value in building the 1.20 stream for EPEL Modular if it is also provided in AppStream. Regardless of whether there is value in this or not, as Karel stated in the first comment, EPEL policy does not allow epel-modular to contain nginx:1.20. Please remove or rename that module stream. https://docs.fedoraproject.org/en-US/epel/epel-policy/#_policy
(In reply to Carl George 🤠 from comment #4) > > The question is whether there is even value in building the 1.20 stream for EPEL Modular if it is also provided in AppStream. > > Regardless of whether there is value in this or not, as Karel stated in the > first comment, EPEL policy does not allow epel-modular to contain > nginx:1.20. Please remove or rename that module stream. > > https://docs.fedoraproject.org/en-US/epel/epel-policy/#_policy Thanks, I did get that part. I have excluded el8 from the modulemd on all of the overlapping streams and opened a releng ticket here: https://pagure.io/releng/issue/10553
*** Bug 2084559 has been marked as a duplicate of this bug. ***
Issue has been resolved: https://pagure.io/releng/issue/10553. EPEL no longer provides the NGINX 1.20 module.