On Tue, Apr 20, 2021 at 11:01:14PM -0400, Felix Kaechele wrote: > Hi there, > > I think this has been discussed at committee meetings before: nginx's > procedure of immediately dropping a release series when a new one hits the > stable branches is essentially forcing us to upgrade along with it, unless > someone is willing to backport patches. > > I personally am not willing to do backports as I do not use EL7 at this > point and only continue maintaining the package as a courtesy to the > community. > > I therefor intend to make the following changes to the nginx package in > EPEL7: > - Update to 1.20.0 > - build against OpenSSL 1.1 to enable TLS1.3 support > > Do I require additional permission do move forward with this in this manner? > There should not be any breaking changes or incompatible changes to config > syntax. But I'll admit that I do not have complex config scenarios as > testcases. > > EPEL8 is not affected as nginx doesn't have an EPEL build for EL8. It is > maintained upstream. > There are, however, modules with certain streams (1.18 and mainline, for > example) available from EPEL. I think this sounds fine, but you might want to send a note to 'epel-announce@xxxxxxxxxxxxxxxxxxxxxxx' once its in updates-testing and again when it goes to stable. kevin
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
