Hi All,
EPEL2RHEL is part of the RHEL 8 and 9 new package workflow. When a RHEL
maintainer wants to add a package to RHEL 8 or 9 they start a "new package
workflow". There are several automations that happen when they start that
workflow. One of them is checking if the package is already in
On Wed, 31 Aug 2022 at 17:08, Stephen Smoogen wrote:
>
> When EPEL-8 was launched, it came with some support for modules with the
> hope that a module ecosystem could be built from Fedora packages using RHEL
> modules as an underlying tool. This has never happened and we have ended up
> with a
When EPEL-8 was launched, it came with some support for modules with the
hope that a module ecosystem could be built from Fedora packages using RHEL
modules as an underlying tool. This has never happened and we have ended up
with a muddle of modular packages which will 'build' but may not install
The following Fedora EPEL 7 Security updates need testing:
Age URL
3 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-cf9b662b60
tcpreplay-4.4.2-1.el7
The following builds have been pushed to Fedora EPEL 7 updates-testing
btrbk-0.31.3-2.el7
shdoc-1.1-1.el7
Details
The following Fedora EPEL 8 Security updates need testing:
Age URL
42 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-89ad385971
chromium-103.0.5060.114-1.el8
3 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-00b4829e45
tcpreplay-4.4.2-1.el8
The following builds
