On Thu, 2022-04-21 at 12:35 -0700, Troy Dawson wrote:
Hi Sérgio,
We aren't sure if you saw this or not, but you have permission to
move ahead with the re-builds.
Let us know if you need help with anything.
Hi, thank you , I'm aware, I will try do it this weekend .
I have a issue in email client ( evolution ) which me prevents me to
select text, in my remote desktop, which limits me to write emails
properly ...
Best regards,
On Wed, Apr 13, 2022 at 3:06 PM Carl George <carl(a)redhat.com>
wrote:
> On Fri, Apr 8, 2022 at 5:17 PM Troy Dawson <tdawson(a)redhat.com>
> wrote:
> >
> >
> >
> > On Fri, Apr 8, 2022 at 3:00 PM Sérgio Basto <sergio(a)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(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
> >>
> >>
> >>
> >> we got 82 reported on bugzilla
> >>
>
https://bugzilla.redhat.com/buglist.cgi?bug_status=NEW&bug_status=ASS...
> >
> >
> > 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
> >
> >
> > _______________________________________________
> > 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
>
> This was approved [0] in today's EPEL Steering Committee meeting.
> Please continue with the process for incompatible upgrades from
> step 4
> forward [1].
>
> [0]
>
https://meetbot.fedoraproject.org/teams/epel/epel.2022-04-13-20.00.html
> [1]
>
https://docs.fedoraproject.org/en-US/epel/epel-policy-incompatible-upgrad...
>
--
Sérgio M. B.