[EPEL-devel] Fedora EPEL 8 updates-testing report

The following Fedora EPEL 8 Security updates need testing: Age URL 11 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-b68969af8c chromium-88.0.4324.96-1.el8 10 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-403074b7e0 seamonkey-2.53.6-1.el8 8

[EPEL-devel] Fedora EPEL 7 updates-testing report

The following Fedora EPEL 7 Security updates need testing: Age URL 49 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-4a9fc09599 openjpeg2-2.3.1-10.el7 12 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-e06cd0281c zabbix30-3.0.31-1.el7 11

[EPEL-devel] Proposal: EPEL9 timeline

This is a proposal. It's mainly writing down what I think most of us agreed on at last weeks EPEL Steering Committee meeting. Feel free to continue to discuss and/or have ideas. I've been asked by a couple places what the plans were, so I'm writing it here. Overall Plan: - epel-next is an epel

[EPEL-devel] Re: how to request access for EPEL-only package which existed in Fedora previously?

On 05. 02. 21 10:11, Felix Schwarz wrote: Hi, I created a review request for python3-configobj which is needed to update certbot in EPEL 7. (certbot now only supports Python 3). The python3-configobj repo was used in Fedora (in ancient history) but I think it can be "reused" to provide an

[EPEL-devel] how to request access for EPEL-only package which existed in Fedora previously?

Hi, I created a review request for python3-configobj which is needed to update certbot in EPEL 7. (certbot now only supports Python 3). The python3-configobj repo was used in Fedora (in ancient history) but I think it can be "reused" to provide an EPEL7-only package. Now my review request