From nobody Sat Jun 21 10:03:50 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 4bPVL530dDz5yKRn for ; Sat, 21 Jun 2025 10:03:57 +0000 (UTC) (envelope-from nxjoseph@protonmail.com) Received: from mail-43166.protonmail.ch (mail-43166.protonmail.ch [185.70.43.166]) (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 4bPVL45lvMz3Mkj for ; Sat, 21 Jun 2025 10:03:56 +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=1750500234; x=1750759434; bh=1sXGhn2PJPmvwe0vDCV93jkU6hggYtkIi9fb0sEuhh8=; 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=FxWtsICVmxJB0ivG99jnCCU7OnpTOFpf3PzWd3dKKfADemOPw9mJ18N+5N5G69CEV x19vaMdXd8yhj1rpInTrsKqKFjo28VNGTmYnefqorV1tJwRQzvioQQx6p2pT2fo1Aj aDOYhngfLprZtA62MGVrqzFJbJurisczHPDyg+lEMKrxuH5NfHCZOCwvpQR+Lp//da EClMdVUL3Fg6AWZ6xfDw2MHwu8UjsACQ4ASxo96qK1pE0RwQLj1cCCOzjoaqZYwh1K 6/CdHjRhYFI4IfncTVIGMu5qWrqktipNQKcb9rFLKSRmrRR3UTgZnTsoAI2YBC9Gwg la3Iq4PRRhCFQ== Date: Sat, 21 Jun 2025 10:03:50 +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: <5D53ED2E-FD6A-4F15-A0EA-7041E5795977@lassitu.de> References: <5D53ED2E-FD6A-4F15-A0EA-7041E5795977@lassitu.de> Feedback-ID: 21989843:user:proton X-Pm-Message-ID: 67bac32403711746f8299af8185aed3f2c934369 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: 4bPVL45lvMz3Mkj 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:185.70.43.0/24, country:CH] 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 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 Fon +49 175 3288861 > =20 > =20 >