From nobody Sat Jun 21 10:10:30 2025 X-Original-To: freebsd-ports@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4bPVTq72hjz5yKYd for ; Sat, 21 Jun 2025 10:10:39 +0000 (UTC) (envelope-from nxjoseph@protonmail.com) Received: from mail-106101.protonmail.ch (mail-106101.protonmail.ch [79.135.106.101]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "protonmail.com", Issuer "R11" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4bPVTq2RJgz3R0c for ; Sat, 21 Jun 2025 10:10:39 +0000 (UTC) (envelope-from nxjoseph@protonmail.com) Authentication-Results: mx1.freebsd.org; none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail3; t=1750500635; x=1750759835; bh=RM53BFcDbVcaQmq7i1SMBKbPC4BFLCLecwS84EMLgP8=; h=Date:To:From:Cc:Subject:Message-ID:In-Reply-To:References: Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID:BIMI-Selector; b=HZNQ10y4w3kPul/sajsUcWM6LtMNwuzPqqSsYH/X37YrE/UkUZ9ySQ2mrzL1yDaXK lcwWZyQqeK5qUzo/gmCAsdG1iz6+29Ewr9TNMG6LubPIzi8cg/vqqrLXvw1Q0TKS3K HPnXaNpOUHnx8nKk8iZrqvkGHijwyJIoHpNLAmwSuK7BNkNtLPQHzm2XSXcRX2Msx2 yh6/+PaWQJpDZQnycKmF2iOBYpnqCLfOu6y7RzTYRAzHrJpPGSVtoYlGFsNQdDGUUa L/O++VX7LK3QDAhYkEwtWMsKemmbStW0sVKvqKZ+vIqAB/LSFOrbk+yfg7UgauvZuv AcvNtfHNaVB9Q== Date: Sat, 21 Jun 2025 10:10:30 +0000 To: "stb@lassitu.de" From: Yusuf Yaman Cc: "freebsd-ports@freebsd.org" Subject: Re: Requesting go1.24 in quarterly Message-ID: In-Reply-To: References: <5D53ED2E-FD6A-4F15-A0EA-7041E5795977@lassitu.de> Feedback-ID: 21989843:user:proton X-Pm-Message-ID: 2a03be04361b60f9839d2c92656b82dde707f2a3 List-Id: Porting software to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-ports List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-ports@freebsd.org Sender: owner-freebsd-ports@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 4bPVTq2RJgz3R0c X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:62371, ipnet:79.135.106.0/24, country:CH] You are welcome. Do you have a poudriere setup? Then I may suggest trying to use go1.24 with= in quarterly branch so you can see what happens when that port can't find g= o1.24.=20 I don't think that this method is deprecated. I would just use the default go version without specifying a version in USE= S flag and it would fetch the right go version. I'd suggest testing it with poudriere. I get rid of FreeBSD PKG repositories because I am maintaining some ports a= nd if I already use poudriere, my life gets easier to test my ports. I have= a minimalist desktop, though. Sent from Proton Mail Android -------- Original Message -------- On 6/21/25 1:07 PM, Stefan Bethke wrote: > On 21. Jun 2025, at 12:03, Yusuf Yaman wrote: > > > > On 6/21/25 12:59 PM, Stefan Bethke wrote: > > > >> One of the ports I maintain (www/forgejo) is failing in quarterly bec= ause 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 specif= ic go versions. How should I address this issue? > > 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 por= t was set to use go1.24 back then. IIRC, the port was fetching go1.24 in fe= tch 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. > =20 > Thanks, I meant whether it is (still) OK to do USES=3Dgo:1.24, or whethe= r this is now deprecated or been replaces with a different mechanism. > =20 > =20 > Stefan > =20 > -- > Stefan Bethke Fon +49 175 3288861 > =20 > =20 >