I have been doing updates to EPEL on my spare time at best effort basis, usually
coupled to the work on the Go in Fedora. Unfortunately recently I don't have
much spare time to use there.
I have been trying to keep the EPEL on the odd(just arbitrary coincidence)
release of Go for entirety of its life time. Giving EPEL stable version of Go
for roughly a year.
Really from my perspective someone needs to show up to do the work there. EPEL's
golang is de facto orphaned for several years now(4+??). If anyone is
volunteering I will be happy to help with on-boarding/reviewing. Even just PR/MR
will be welcomed.
JC
On Tue, 2021-12-21 at 10:46 +0100, Alejandro Saez Morollon wrote:
For the record, there's an ongoing conversation in this bug about
this topic:
https://bugzilla.redhat.com/show_bug.cgi?id=2013628
On Tue, Dec 21, 2021 at 10:01 AM Alejandro Saez Morollon <asm(a)redhat.com>
wrote:
>
>
> On Mon, Dec 20, 2021 at 12:36 AM Robert-André Mauchin <zebob.m(a)gmail.com>
> wrote:
> > On 12/1/21 20:11, Dave Dykstra wrote:
> > > What will it take to get golang updated on epel7 from the no longer
> > > supported version 1.15? RHEL8.5 reports a long list of security
> > > problems that are fixed in 1.16.
> > >
> > > Dave
> >
> > Jakub or Alex, do you know whose prerogative is this?
> >
> >
>
>
> I think Jakub is more appropriate than me to answer this question because I
> never built EPEL but, as far as I remember, from a conversation with Jakub,
> he was doing major upgrades of odd versions.
> Mainly because a major version is going to be there for ~1 year and that
> gives a little stability to the users of EPEL.
> If what I said is accurate, the lack of 1.17 on Fedora is what made this
> scenario.
>
> Nevertheless, Go 1.15 doesn't have support anymore from upstream so I would
> say that we should upgrade it.
> I have no problems with trying to upgrade it to 1.16 or 1.17.
>
> What do you think?
>
>
>
> > Best regards,
> >
> > Robert-André
> >