golang 1.16 for epel7?

[Dave Dykstra]

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

[Robert-André Mauchin]

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?

Best regards,

Robert-André

[Alejandro Saez Morollon]

On Mon, Dec 20, 2021 at 12:36 AM Robert-André Mauchin 
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é

[Alejandro Saez Morollon]

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 
wrote:
> On Mon, Dec 20, 2021 at 12:36 AM Robert-André Mauchin 
> 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é

[Jakub Čajka]

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 
> wrote:
> > On Mon, Dec 20, 2021 at 12:36 AM Robert-André Mauchin 
> > 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é

[Dave Dykstra]

Jakub,

I volunteer to do golang updates on EPEL7.  I am the maintainer of
singularity for EPEL/Fedora so I know how to use the tools.  Just add
[e-mail].

Dave

On Mon, Jan 03, 2022 at 04:42:24PM +0100, Jakub Čajka wrote:
> 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 
> > wrote:
> > > On Mon, Dec 20, 2021 at 12:36 AM Robert-André Mauchin 
> > > 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é

[Jakub Čajka]

Thank you very much for volunteering. I have added you(dwd) as contributor and committer for EPEL branches. BZs should switch to you.

If you would have any questions or need any help, feel free to ask.

JC

Jan 11, 2022, 18:11 by [e-mail]:
> Jakub,
>
> I volunteer to do golang updates on EPEL7.  I am the maintainer of
> singularity for EPEL/Fedora so I know how to use the tools.  Just add
> [e-mail].
>
> Dave
>
> On Mon, Jan 03, 2022 at 04:42:24PM +0100, Jakub Čajka wrote:
> > 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 
> > > wrote:
> > > > On Mon, Dec 20, 2021 at 12:36 AM Robert-André Mauchin 
> > > > 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é
>
> golang mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> 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/[e-mail]
> Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure

[Dave Dykstra]

Thanks.  I found that I could use the f35 packaging files with only one
minor change, and have requested golang-1.16.13-1 to be promoted to
testing:
    https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-14c15afabc

Dave

On Thu, Jan 13, 2022 at 03:52:33PM +0100, Jakub Čajka wrote:
> Thank you very much for volunteering. I have added you(dwd) as
> contributor and committer for EPEL branches. BZs should switch to you.
>
> If you would have any questions or need any help, feel free to ask.
>
> JC
>
> Jan 11, 2022, 18:11 by [e-mail]:
> > Jakub,
> >
> > I volunteer to do golang updates on EPEL7.  I am the maintainer of
> > singularity for EPEL/Fedora so I know how to use the tools.  Just add
> > [e-mail].
> >
> > Dave
> >
> > On Mon, Jan 03, 2022 at 04:42:24PM +0100, Jakub Čajka wrote:
> > > 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 
> > > > wrote:
> > > > > On Mon, Dec 20, 2021 at 12:36 AM Robert-André Mauchin 
> > > > > 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é
> >
> > golang mailing list -- [e-mail]
> > To unsubscribe send an email to [e-mail]
> > 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/[e-mail] 
> > Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
>
> golang mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> 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/[e-mail] 
> Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure

[Dave Dykstra]

It turned out there were a couple of significant problems with that
first build, but they are fixed in golang-1.16.13-2 which should be
in epel-testing for epel7 by tomorrow.
    https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-246382d5dc
It also now resolves 14 additional outstanding bugzilla CVE-related
tickets.

There are more differences now in the .spec file, but they're still
pretty minimal and all within %if statements so it could certainly be
shared with the Fedora builds.

Dave

On Tue, Jan 18, 2022 at 11:03:30PM +0000, Dave Dykstra wrote:
> Thanks.  I found that I could use the f35 packaging files with only one
> minor change, and have requested golang-1.16.13-1 to be promoted to
> testing:
>     https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-14c15afabc
>
> Dave
>
> On Thu, Jan 13, 2022 at 03:52:33PM +0100, Jakub Čajka wrote:
> > Thank you very much for volunteering. I have added you(dwd) as
> > contributor and committer for EPEL branches. BZs should switch to you.
> >
> > If you would have any questions or need any help, feel free to ask.
> >
> > JC
> >
> > Jan 11, 2022, 18:11 by [e-mail]:
> > > Jakub,
> > >
> > > I volunteer to do golang updates on EPEL7.  I am the maintainer of
> > > singularity for EPEL/Fedora so I know how to use the tools.  Just add
> > > [e-mail].
> > >
> > > Dave
> > >
> > > On Mon, Jan 03, 2022 at 04:42:24PM +0100, Jakub Čajka wrote:
> > > > 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 
> > > > > wrote:
> > > > > > On Mon, Dec 20, 2021 at 12:36 AM Robert-André Mauchin 
> > > > > > 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é
> > > > > > >
> > >
> > > golang mailing list -- [e-mail]
> > > To unsubscribe send an email to [e-mail]
> > > 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/[e-mail]  
> > > Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
> >
> > golang mailing list -- [e-mail]
> > To unsubscribe send an email to [e-mail]
> > 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/[e-mail]  
> > Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
>
> golang mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> 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/[e-mail] 
> Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure

[Jakub Čajka]

Jan 21, 2022, 00:54 by [e-mail]:
> It turned out there were a couple of significant problems with that
> first build, but they are fixed in golang-1.16.13-2 which should be
> in epel-testing for epel7 by tomorrow.
>  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-246382d5dc
> It also now resolves 14 additional outstanding bugzilla CVE-related
> tickets.
>
> There are more differences now in the .spec file, but they're still
> pretty minimal and all within %if statements so it could certainly be
> shared with the Fedora builds.
>
> Dave

Thank you. 
I will try to get around and test it, provide karma.
JC
> On Tue, Jan 18, 2022 at 11:03:30PM +0000, Dave Dykstra wrote:
> > Thanks.  I found that I could use the f35 packaging files with only one
> > minor change, and have requested golang-1.16.13-1 to be promoted to
> > testing:
> >  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-14c15afabc
> >
> > Dave
> >
> > On Thu, Jan 13, 2022 at 03:52:33PM +0100, Jakub Čajka wrote:
> > > Thank you very much for volunteering. I have added you(dwd) as
> > > contributor and committer for EPEL branches. BZs should switch to you.
> > >
> > > If you would have any questions or need any help, feel free to ask.
> > >
> > > JC
> > >
> > > Jan 11, 2022, 18:11 by [e-mail]:
> > > > Jakub,
> > > >
> > > > I volunteer to do golang updates on EPEL7.  I am the maintainer of
> > > > singularity for EPEL/Fedora so I know how to use the tools.  Just add
> > > > [e-mail].
> > > >
> > > > Dave
> > > >
> > > > On Mon, Jan 03, 2022 at 04:42:24PM +0100, Jakub Čajka wrote:
> > > > > 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 
> > > > > > wrote:
> > > > > > > 
> > > > > > > 
> > > > > > > On Mon, Dec 20, 2021 at 12:36 AM Robert-André Mauchin 
> > > > > > > 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é
> > > > > > > >
> > > >
> > > > golang mailing list -- [e-mail]
> > > > To unsubscribe send an email to [e-mail]
> > > > 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/[e-mail] 
> > > > Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
> > >
> > > golang mailing list -- [e-mail]
> > > To unsubscribe send an email to [e-mail]
> > > 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/[e-mail] 
> > > Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
> >
> > golang mailing list -- [e-mail]
> > To unsubscribe send an email to [e-mail]
> > 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/[e-mail] 
> > Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
>
> golang mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> 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/[e-mail]
> Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure