The following Fedora EPEL 7 Security updates need testing:
Age URL
6 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-ce8d5824ad
halibut-1.3-3.el7
5 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-aaaeae50ce
rubygem-jmespath-1.3.1-1.el7
The following builds have
The following Fedora EPEL 8 Security updates need testing:
Age URL
6 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-287b3b64f6
halibut-1.3-3.el8
The following builds have been pushed to Fedora EPEL 8 updates-testing
python-bottle-0.12.21-2.el8
tio-1.39-1.el8
Details
The following Fedora EPEL 9 Security updates need testing:
Age URL
5 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-1fbc5ebf38
python-elasticsearch-7.17.4-1.el9
The following builds have been pushed to Fedora EPEL 9 updates-testing
pam_radius-2.0.0-1.el9
On Mon, Jun 13, 2022, 4:17 PM Chris Adams wrote:
> Once upon a time, Josh Boyer said:
> > If the dependency is only needed at build time, which is what CRB
> > content is intended for
>
> If that's the intent, then it's not implemented correctly. For example,
> there are well over 100 perl
On Mon, Jun 13, 2022 at 5:03 AM Josh Boyer wrote:
> However, if a package needs something
> at runtime it would be better to first inquire about putting that
> dependency in BaseOS or AppStream rather than just blindly using it
> from CRB.
>
My first attempt as requesting a critical runtime CRB
Once upon a time, Josh Boyer said:
> If the dependency is only needed at build time, which is what CRB
> content is intended for
If that's the intent, then it's not implemented correctly. For example,
there are well over 100 perl modules in CRB 9. They may only be used
_by Red Hat_ in
On Mon, 13 Jun 2022 at 10:44, Troy Dawson wrote:
> It was a configuration mix up that pulled in ALL the modules instead of
> just the default ones.
> It only lasted a week (I think) and has been fixed.
> It was just bad timing, nothing you could have done to prevent, or fix it.
>
> I thought
On Mon, 2022-06-13 at 07:41 -0400, Josh Boyer wrote:
> On Sun, Jun 12, 2022 at 6:50 AM Sérgio Basto
> wrote:
> >
> > On Sun, 2022-06-05 at 00:54 +0200, Neal Gompa wrote:
> > > Let me start with examples that I get *regularly*: Pagure fails
> > > to
> > > install from EPEL on
It was a configuration mix up that pulled in ALL the modules instead of
just the default ones.
It only lasted a week (I think) and has been fixed.
It was just bad timing, nothing you could have done to prevent, or fix it.
I thought we'd caught all the packages that were built that might have been
On Mon, 2022-06-13 at 09:34 +0200, Petr Pisar wrote:
> V Sun, Jun 12, 2022 at 12:29:06AM +0100, Sérgio Basto napsal(a):
> > On Sat, 2022-06-11 at 17:25 +, bugzi...@redhat.com wrote:
> > > https://bugzilla.redhat.com/show_bug.cgi?id=2095649
> >
> > Hi,
> > for some reason the build on epel 8
Am 13.06.22 um 13:41 schrieb Josh Boyer:
On Sun, Jun 12, 2022 at 6:50 AM Sérgio Basto wrote:
On Sun, 2022-06-05 at 00:54 +0200, Neal Gompa wrote:
Let me start with examples that I get *regularly*: Pagure fails to
install from EPEL on RHEL/CentOS/Alma/etc. because python3-markdown
is
not
On Sun, Jun 12, 2022 at 6:50 AM Sérgio Basto wrote:
>
> On Sun, 2022-06-05 at 00:54 +0200, Neal Gompa wrote:
> > Let me start with examples that I get *regularly*: Pagure fails to
> > install from EPEL on RHEL/CentOS/Alma/etc. because python3-markdown
> > is
> > not available. KDE Plasma fails to
V Sun, Jun 12, 2022 at 12:29:06AM +0100, Sérgio Basto napsal(a):
> On Sat, 2022-06-11 at 17:25 +, bugzi...@redhat.com wrote:
> > https://bugzilla.redhat.com/show_bug.cgi?id=2095649
>
> Hi,
> for some reason the build on epel 8 to update ImageMagick-6.9.12 from
> 48 to 50 (
>
13 matches
Mail list logo
