On Wednesday, August 31, 2022 Troy Dawson wrote:
> 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
On Thu, 1 Sept 2022 at 12:25, Troy Dawson wrote:
>
>
> On Thu, Sep 1, 2022 at 12:19 AM Miro Hrončok wrote:
>
>> On 31. 08. 22 23: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
On Thu, Sep 1, 2022 at 12:19 AM Miro Hrončok wrote:
> On 31. 08. 22 23: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
The following Fedora EPEL 7 Security updates need testing:
Age URL
4 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
python-apprise-1.0.0-1.el7
The following Fedora EPEL 8 Security updates need testing:
Age URL
43 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-89ad385971
chromium-103.0.5060.114-1.el8
4 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-00b4829e45
tcpreplay-4.4.2-1.el8
The following builds
On 01. 09. 22 0:19, Troy Dawson wrote:
** Solution(s)
A - At the very least, we need to change the wording of the bugs. I am
proposing the following
Subject: Remove from epel9 when rhel 9.1 is released
Comment: This package is being added to RHEL 9.1 at the next minor release.
After the
On 31. 08. 22 23: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
muddle of
