The following Fedora EPEL 7 Security updates need testing:
Age URL
6 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-3cb841c5f0
chromium-123.0.6312.105-1.el7
1 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-a8b1cd8e52
perl-Clipboard-0.29-1.el7
The following
Thank you for the followup.
On Thu, Apr 11, 2024 at 7:51 PM David Trudgian via epel-devel <
epel-devel@lists.fedoraproject.org> wrote:
> The singularity-ce incompatible upgrade has now been pushed to stable.
>
> This is the final announcement prescribed by the EPEL Incompatible
> Upgrades
I have just submitted for testing
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-ce142428af,
which updates llhttp in EPEL9 from 9.1.3 to 9.2.1 and fixes
CVE-2024-27982[1], an HTTP request smuggling vulnerability. Version
9.2.0 also included a number of bug fixes[2]. This is an
The singularity-ce incompatible upgrade has now been pushed to stable.
This is the final announcement prescribed by the EPEL Incompatible Upgrades
Policy:
https://docs.fedoraproject.org/en-US/epel/epel-policy-incompatible-upgrades/
Cheers,
DT
On 9 Feb 2024, at 10:45, David Trudgian wrote:
Dear all,
Django 4.2 (the only currently supported LTS series) requires asgiref >=
3.6, so I would like to propose updating python-asgiref in EPEL 9 at
least to 3.6.0, but ideally to 3.8.1 for future proofing.
The affected packages (maintainers bcc:ed) are python-django3 (which I
maintain, and
Hi all,
With the recent EOL of the Django 3.2 LTS series[^1], and Django being a
key component of our mailing list infra for both Fedora and CentOS, I
would like to propose the following plan to maintain Django in both
Fedora and EPEL:
- Fedora: `python-django` maintained as currently, not
