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
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
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 (
>
