epel-announce September 2023

epel-announce@lists.fedoraproject.org

4 participants
4 discussions

Re: [EPEL-devel] Re: Take the EPEL user and contributor survey 2023!
by Diego Herrera 14 Sep '23

14 Sep '23

> The link is incorrect and should be https://fedoraproject.limequery.com/epelsurvey2023 Yes, my mistake. The correct link is https://fedoraproject.limequery.com/epelsurvey2023 :) > None of them is available, it seems. We had some problems with Fedora's LimeSurvey account that limited the amount of responses we could receive per day. This problem has been addressed, so you should be able to take the survey without problems now. Just to clarify on this, none of the already made entries were lost in this process, so we do not believe it will be necessary to extend the duration of the survey for now. On Sat, Sep 2, 2023 at 6:26 AM Michael J Gruber <mjg(a)fedoraproject.org> wrote: > > Am Fr., 1. Sept. 2023 um 22:09 Uhr schrieb Stephen Smoogen > <ssmoogen(a)redhat.com>: > > > > > > > > On Fri, 1 Sept 2023 at 16:03, Diego Herrera <dherrera(a)redhat.com> wrote: > >> > >> Hello, everyone > >> > >> The Fedora EPEL SIG is asking for feedback to improve EPEL via this survey! > >> > >> * https://fedoraproject.limequery.com/2023 > >> > > > > The link is incorrect and should be https://fedoraproject.limequery.com/epelsurvey2023 > > > None of them is available, it seems. > > Cheers > Michael > _______________________________________________ > epel-devel mailing list -- epel-devel(a)lists.fedoraproject.org > To unsubscribe send an email to epel-devel-leave(a)lists.fedoraproject.org > 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@lists.fedoraprojec… > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

1 0

Retiring Zim
by Otto Liljalaakso 10 Sep '23

10 Sep '23

I am retiring Zim from EPEL. As specified by the retirement policy [0], I sent notification to epel-devel already two months ago [1]. To continue using Zim, probably the best way is to use the flatpak from Flathub [2]. [0]: https://docs.fedoraproject.org/en-US/epel/epel-policy-retirement/#process_n… [1]: https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraprojec… [2]: https://flathub.org/apps/org.zim_wiki.Zim

1 0

Take the EPEL user and contributor survey 2023!
by Diego Herrera 01 Sep '23

01 Sep '23

Hello, everyone The Fedora EPEL SIG is asking for feedback to improve EPEL via this survey! * https://fedoraproject.limequery.com/2023 The survey is targeting EPEL users and contributors. It asks about how you use EPEL, how you contribute to it, and on what would you need to improve that experience. If you're someone who uses or works on Extra Packages for Enterprise Linux, please participate. Survey closes at the end of September! Thank you for your contribution!

2 1

incompatible update of caddy in EPEL 9
by Carl George 31 Aug '23

31 Aug '23

I am performing an incompatible upgrade of the caddy package in EPEL 9. In accordance with the incompatible upgrade policy [0], I proposed this upgrade just over a week ago on the epel-devel mailing list [1]. For reasons detailed in the previous email, it is no longer possible to update the package at the current version, preventing me from resolving known CVEs. Today the EPEL Steering Committee voted to approve this upgrade [2]. This upgrade will take the package from version 2.4.6 to 2.6.4. This includes a few backwards-incompatible changes. I believe these changes are on the milder side, and most users shouldn't notice a difference. Here are the most notable removals/changes: - Reverse proxy: Incoming X-Forwarded-* headers will no longer be automatically trusted, to prevent spoofing. - Logging: Removed the deprecated common_log field from HTTP access logs, and the single_field encoder. - Logging: The remote_addr field has been replaced by remote_ip and remote_port fields in HTTP access logs, which split up the two parts of the remote address. - Caddyfile: The reverse_proxy directive's handle_response subdirective has had its status replacement functionality moved to a new replace_status subdirective. There are also a few additional changes to features labeled as experimental, and some deprecations (not yet removed). For a full list, see the upstream release notes [3][4]. If you are able, please test and provide karma for the update [5]. [0] https://docs.fedoraproject.org/en-US/epel/epel-policy-incompatible-upgrades/ [1] https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraprojec… [2] https://meetbot.fedoraproject.org/fedora-meeting/2023-08-23/epel.2023-08-23… [3] https://github.com/caddyserver/caddy/releases/tag/v2.5.0 [4] https://github.com/caddyserver/caddy/releases/tag/v2.6.0 [5] https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-8849a14e7f -- Carl George

1 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

epel-announce September 2023