On Fri, Apr 8, 2022 at 12:46 PM Sérgio Basto <sergio(a)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
Troy
_______________________________________________
epel-devel mailing list -- epel-devel(a)lists.fedoraproject.org
To unsubscribe send an email to
epel-devel-leave(a)lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproj...
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
--
Sérgio M. B.