From nobody Tue Sep 9 23:33:40 2025 X-Original-To: freebsd-current@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 4cM0WT6sc4z66cC5 for ; Tue, 09 Sep 2025 23:33:41 +0000 (UTC) (envelope-from brian@sonicboom.org) Received: from sheehan.sonicboom.org (sheehan.sonicboom.org [50.190.118.82]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4cM0WT2YTMz3bJ1 for ; Tue, 09 Sep 2025 23:33:41 +0000 (UTC) (envelope-from brian@sonicboom.org) Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of brian@sonicboom.org designates 50.190.118.82 as permitted sender) smtp.mailfrom=brian@sonicboom.org Received: from [192.168.4.22] (unknown [50.190.118.81]) by sheehan.sonicboom.org (Postfix) with ESMTPSA id ABB663A0007F for ; Tue, 9 Sep 2025 17:33:40 -0600 (MDT) Message-ID: Date: Tue, 9 Sep 2025 17:33:40 -0600 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: source upgrade of OS leaves pkg using pkg.freebsd.org non-functional To: freebsd-current@freebsd.org References: <7FBE1ACB-0F72-4116-98C4-4712B5C63199.ref@yahoo.com> <7FBE1ACB-0F72-4116-98C4-4712B5C63199@yahoo.com> Content-Language: en-US From: Brian In-Reply-To: <7FBE1ACB-0F72-4116-98C4-4712B5C63199@yahoo.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spamd-Bar: / X-Spamd-Result: default: False [0.87 / 15.00]; NEURAL_HAM_SHORT(-1.00)[-1.000]; NEURAL_SPAM_MEDIUM(1.00)[0.999]; NEURAL_SPAM_LONG(0.98)[0.975]; R_SPF_ALLOW(-0.20)[+ip4:50.190.118.82:c]; ONCE_RECEIVED(0.20)[]; MIME_GOOD(-0.10)[text/plain]; ARC_NA(0.00)[]; ASN(0.00)[asn:7922, ipnet:50.128.0.0/9, country:US]; FREEFALL_USER(0.00)[brian]; RCVD_COUNT_ONE(0.00)[1]; MIME_TRACE(0.00)[0:+]; RCPT_COUNT_ONE(0.00)[1]; RCVD_TLS_ALL(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; R_DKIM_NA(0.00)[]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; TO_MATCH_ENVRCPT_ALL(0.00)[]; DMARC_NA(0.00)[sonicboom.org]; RCVD_VIA_SMTP_AUTH(0.00)[] X-Rspamd-Queue-Id: 4cM0WT2YTMz3bJ1 Yep I am using what was normal for me a couple of decades ago, portupgrade -aP, until pkg works again. I do a git pull of ports periodically just to ensure I can build pkg and other tools as needed. Brian On 9/9/2025 1:56 PM, Mark Millard wrote: > oid wrote on > Date: Tue, 09 Sep 2025 17:31:52 UTC : > >> On Tue, Sep 09, 2025 at 06:27:35PM +0100, Lexi Winter wrote: >> >>> yes: ports packages are not available for 16 yet, so you'll have to >>> build from source for now. >> ok, thanks for confirming > Going along with that is that, while, > > https://pkg.FreeBSD.org/FreeBSD:16:amd64/ > > (or other such?) does exist just recently, > > https://pkg.freebsd.org/FreeBSD:16:amd64/kmods_latest/ > and: > https://pkg.freebsd.org/FreeBSD:16:amd64/latest/ > > still have not been created (as of when I looked). > > https://pkg.freebsd.org/FreeBSD:16:aarch64/ > > is still: "404 Not Found" > > as well (as of when I looked). > > But things are in process and you can monitor > such places that happen to be of interest. > > > Other notes: > > If pkg 2.3.0 ends up being released soon enough, > stopping: > > https://pkg-status.freebsd.org/beefy18/build.html?mastername=main-amd64-default&build=p118fb2971704_s4ab64e34911 > (or other such main-* builds) > > and running a build based on pkg 2.3.0 may well > take noticable less overall time than letting > the pkg 2.2.2 based build of main-amd64 > port-packkages continue. > > (pkg 2.[12].* and main-*'s debug poudriere jail > combination makes the builds take a very long > time: 240+ Hrs to 480+ Hrs for beefy18 when most > everything is being rebuilt. ampere2 for aarch64 > takes longer.) > > === > Mark Millard > marklmi at yahoo.com > >