Page MenuHomeFreeBSD

lang/go121: Update to 1.21.6
AbandonedPublic

Authored by dutra on Feb 1 2024, 3:38 AM.
Tags
None
Referenced Files
Unknown Object (File)
May 4 2024, 1:17 PM
Unknown Object (File)
Apr 27 2024, 9:41 AM
Unknown Object (File)
Apr 27 2024, 9:41 AM
Unknown Object (File)
Apr 27 2024, 8:16 AM
Unknown Object (File)
Apr 26 2024, 3:14 AM
Unknown Object (File)
Apr 14 2024, 5:37 PM
Unknown Object (File)
Apr 7 2024, 12:38 AM
Unknown Object (File)
Feb 8 2024, 11:56 PM
Subscribers
None

Details

Summary

Poudriere log (amd64): https://poudriere.nulldutra.me/data/latest-per-pkg/go121/1.21.6/
Poudriere log (arm64): https://poudriere-arm64.nulldutra.me/data/latest-per-pkg/go121/1.21.6/

portlint:

looks fine.
commit aa52c39d12f0e3e5accc58a51e25cce3461cdaa6 (HEAD -> main)
Author: Gabriel M. Dutra <dutra@FreeBSD.org>
Date:   Thu Feb 1 00:35:12 2024 -0300

    lang/go121: Update to 1.21.6

    ChangeLog: https://go.dev/doc/devel/release#go1.21.6

    Approved by:    dbaio(mentor), garga(mentor)
    Differential Revision:  https://reviews.freebsd.org/D43699

Diff Detail

Repository
R11 FreeBSD ports repository
Lint
Lint Skipped
Unit
Tests Skipped

Event Timeline

dutra requested review of this revision.Feb 1 2024, 3:38 AM
dutra created this revision.
dutra added reviewers: dbaio, garga, dmgk, ygy.

Many ports depend on this one, as you are already aware.

In other ports similar to this, it's common to request an exp-run (via Bugzilla) before updating. However, upon reviewing the commit history of the lang/go* ports, it appears that exp-runs are not being requested.

Maybe @dmgk is handling this independently.

For other substantial ports, I prefer to conduct builds in my poudriere, checking all the ports dependent on it and running a poudriere bulk (at least).
Example:

poudriere bulk -f /tmp/list_of_ports.txt -j $jail -p $ports -b latest

After that, performing a few runtime tests.

Maybe you could do this here as well.

@dmgk, are you ok with this? Or could you guide how @dutra can conduct the necessary tests?

Thank you in advance.

Many ports depend on this one, as you are already aware.

In other ports similar to this, it's common to request an exp-run (via Bugzilla) before updating. However, upon reviewing the commit history of the lang/go* ports, it appears that exp-runs are not being requested.

Maybe @dmgk is handling this independently.

For other substantial ports, I prefer to conduct builds in my poudriere, checking all the ports dependent on it and running a poudriere bulk (at least).
Example:

poudriere bulk -f /tmp/list_of_ports.txt -j $jail -p $ports -b latest

After that, performing a few runtime tests.

Maybe you could do this here as well.

@dmgk, are you ok with this? Or could you guide how @dutra can conduct the necessary tests?

Thank you in advance.

Many ports depend on this one, as you are already aware.

In other ports similar to this, it's common to request an exp-run (via Bugzilla) before updating. However, upon reviewing the commit history of the lang/go* ports, it appears that exp-runs are not being requested.

Maybe @dmgk is handling this independently.

For other substantial ports, I prefer to conduct builds in my poudriere, checking all the ports dependent on it and running a poudriere bulk (at least).
Example:

poudriere bulk -f /tmp/list_of_ports.txt -j $jail -p $ports -b latest

After that, performing a few runtime tests.

Maybe you could do this here as well.

@dmgk, are you ok with this? Or could you guide how @dutra can conduct the necessary tests?

Thank you in advance.

Hi, dbaio

Sorry for the delay.

I built three ports with golang 1.21.6: www/grafana, sysutils/terraform, sysutils/terragrunt.
Poudriere compiles all without any problems

See the logs:

AMD64 - 14.0-RELEASE:

AMD64 - 15.0-CURRENT:

ARM64 - 14.0-RELEASE:

AMD64 - 15.0-CURRENT: