On Fri, Apr 8, 2022 at 3:00 PM Sérgio Basto <sergio@serjux.com> wrote:
On Fri, 2022-04-08 at 13:08 -0700, Troy Dawson wrote:


On Fri, Apr 8, 2022 at 12:46 PM Sérgio Basto <sergio@serjux.com> wrote:
On Thu, 2022-03-31 at 11:54 +0100, Sérgio Basto wrote:
> > This update changes a library soname, which makes it an
> > incompatible
> > upgrade.  It must follow the EPEL incompatible upgrades policy [0].
> > This email can count as step 1 once you reply with the specific
> > CVEs
> > this will address.  Then it must be open for discussion on list for
> > one week (step 2) before being added as an agenda item at next
> > week's
> > EPEL Steering Committee meeting [1] (step 3).
> >
> > [0]
> > https://docs.fedoraproject.org/en-US/epel/epel-policy-incompatible-upgrades/
> > [1] https://calendar.fedoraproject.org/epel/#m9854
>
> OK , thank you


Hi,
have we any new ?

I'd like move on before rhel 8.6 be available .


Thank you 


Hi Sérgio,
Could you list the CVE's that this update addresses.
If that list is fairly long, at least the important ones


we got 82 reported on bugzilla 
https://bugzilla.redhat.com/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&classification=Fedora&component=ImageMagick&list_id=12543908&product=Fedora%20EPEL&query_format=advanced

 Youch!
Next time, lead with that. :)
I joke, but that's really what we were waiting for.
It's a Friday afternoon, and I'm pretty certain we won't get enough of the committee reading this to give a full vote until next week.
But, as for me, I give it a +1.
Troy