Date: Sat, 21 Jun 2025 10:03:50 +0000 From: Yusuf Yaman <nxjoseph@protonmail.com> To: "stb@lassitu.de" <stb@lassitu.de> Cc: "freebsd-ports@freebsd.org" <freebsd-ports@freebsd.org> Subject: Re: Requesting go1.24 in quarterly Message-ID: <yarNerHWL_7Sn0zhw447hAUpzcVAl_vqVi0uU06scFGwMuO1EA77E2g09aVyGhywNk5N9UfN0pNOLzB0IdQJ9Xug1WFsy5lKFwBbQimGePM=@protonmail.com> In-Reply-To: <5D53ED2E-FD6A-4F15-A0EA-7041E5795977@lassitu.de> References: <5D53ED2E-FD6A-4F15-A0EA-7041E5795977@lassitu.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, I had a port which should have been using go1.24 and that time it wasn't av= ailable yet but some time after that, go1.24 was available and the port was= set to use go1.24 back then. IIRC, the port was fetching go1.24 in fetch s= tage when go1.24 wasn't available in ports. I guess that your port can buil= d successfully too by fetching go1.24 toolchain in fetch stage. Sent from Proton Mail Android -------- Original Message -------- On 6/21/25 12:59 PM, Stefan Bethke <stb@lassitu.de> wrote: > One of the ports I maintain (www/forgejo) is failing in quarterly becaus= e the default version of go there appears to be less than 1.24, and the ups= tream source build setup will try to install go1.24. > =20 > It seems that some time ago ports were clean up to not request specific = go versions. How should I address this issue? > =20 > =20 > Thanks, > Stefan > =20 > -- > Stefan Bethke <stb@lassitu.de> Fon +49 175 3288861 > =20 > =20 >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?yarNerHWL_7Sn0zhw447hAUpzcVAl_vqVi0uU06scFGwMuO1EA77E2g09aVyGhywNk5N9UfN0pNOLzB0IdQJ9Xug1WFsy5lKFwBbQimGePM=>