Hi,

I had a port which should have been using go1.24 and that time it wasn't 
available 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 stage 
when go1.24 wasn't available in ports. I guess that your port can build 
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 <[email protected]> wrote:

>  One of the ports I maintain (www/forgejo) is failing in quarterly because 
> the default version of go there appears to be less than 1.24, and the 
> upstream source build setup will try to install go1.24.
>  
>  It seems that some time ago ports were clean up to not request specific go 
> versions. How should I address this issue?
>  
>  
>  Thanks,
>  Stefan
>  
>  --
>  Stefan Bethke <[email protected]>   Fon +49 175 3288861
>  
>  
>

Reply via email to