On 13/01/2025 11:52, Clemens Lang wrote:
I don’t think EPEL can reasonably add stability guarantees that
> upstream does not provide except by pinning a package at an old
> version, but that would mean that EPEL would essentially package
> unsupported software.
That's been the practice so far, to my knowledge. I was even smacked
myself here by users on this list for upgrading OpenVPN 2.3 to OpenVPN
2.4 (that is a major upgrade in OpenVPN context) in some of the EPEL
branches. In OpenVPN the command line options are the same as the
configuration file options, and there where option changes breaking
several setups. People where not happy - and I fully understand that -
and had to apply additional changes to restore some critical options
being removed.
That's also the reason why OpenVPN 2.4 is still provided in EPEL-8,
despite upstream project has EOLed the 2.4 releases. And that's why I'm
maintaining separate Fedora Copr repositories for newer major releases -
for those wanting something newer - to access newer features. For the
EPEL repos with the 2.4 release - I need to pay attention if there are
important security issues appearing in newer releases - and consider
backporting those fixes if needed.
The docs you point at puts the command line interface in the API
category. I agree it would be good to have some kind of "application
compatibility level" classification of packages in EPEL. Also having
some kind of announcements when there is expected breakage, as indicated
in the existing "incompatible upgrades policy".
--
kind regards,
David Sommerseth
--
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to 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/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
