First of all thanks for this package. You’ve made my life managing my VPSes a whole lot easier.
I would like to ask about the reason you’ve decided to switch from EPEL build roots in favour of RHEL build roots. It still works on my Rocky VPSes, but dnf copr enable is now broken (since the repo files it installs uses the EPEL chroots). Now users of Rocky/Alma need to manually download the repo files from the Copr page, which is somewhat undesirable.
So yeah, were there any specific benefits with using the RHEL chroots? If not, I think using EPEL chroots is a better idea.
Hi, my choice to switch to the RHEL buildroot was because nothing in this haproxy package depended on EPEL RPMs, so I figured the cleanest root for compatibility across derivative distros would be the one without EPEL.
I didn’t realize that the dnf copr plugin had such a naive preference for the EPEL chroot. I see that now in the Python source:
I will reconfigure to resume building the EPEL buildroot RPMs for x86_64. In the meantime, the issue you’re having can be worked around without going to the webpage, by specifying the chroot at the end of the command: dnf copr enable frederickding/haproxy rhel-9-x86_64. See DNF copr Plugin — dnf-plugins-core 4.3.1-1 documentation .
To any users of the frederickding/haproxy COPR, please be advised that a major version bump is coming when the switch to Fedora 41 RPM sources occurs around the end of October 2024. Fedora 41 includes haproxy version 3.0.x (currently 3.0.3), up from 2.9.x.