From nobody Mon May 26 12:25:50 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 4b5Zjw6Zkyz5xgf6 for ; Mon, 26 May 2025 12:25:56 +0000 (UTC) (envelope-from dclarke@blastwave.org) Received: from mail.oetec.com (mail.oetec.com [108.160.241.186]) (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 ECDSA (prime256v1) client-digest SHA256) (Client CN "mail.oetec.com", Issuer "E5" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4b5Zjv2CxSz3QL4 for ; Mon, 26 May 2025 12:25:55 +0000 (UTC) (envelope-from dclarke@blastwave.org) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=blastwave.org header.s=default header.b=PjwAWT23; spf=pass (mx1.freebsd.org: domain of dclarke@blastwave.org designates 108.160.241.186 as permitted sender) smtp.mailfrom=dclarke@blastwave.org; dmarc=pass (policy=quarantine) header.from=blastwave.org Received: from [172.16.35.3] (pool-99-253-118-250.cpe.net.cable.rogers.com [99.253.118.250]) (authenticated bits=0) by mail.oetec.com (8.17.1/8.17.1) with ESMTPSA id 54QCPo5r059425 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NOT) for ; Mon, 26 May 2025 08:25:51 -0400 (EDT) (envelope-from dclarke@blastwave.org) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=blastwave.org; s=default; t=1748262351; bh=bJXg73W44zcPGkihONp91O4H6ipILhT4Ih3iWgg6XMs=; h=Date:Subject:To:References:From:In-Reply-To; b=PjwAWT23egwP0yI4r3jNweOVaJPOvlVuvBbA2ztjGN4sy2JLsD6R4xtakmJv6ws1b CQeZxg0itAABgThHlLJwlhJC3AcJl5qxEA3a6xEKg/+cVs8B51qBq7jGOcEu1CXMDG etA90OBYAF61SkdOGSByVw1b9FM6aQ8lojgwE57bRKvztCvarwaL/djeZE7CUC+gJD cDdfvMJggOsI34YIxSX1kt5X1NOorg26jHHc96srYrsVg7CIn8y72tz21lDMH4ihKs WU06W+vE3aAgGwpI6J7oixYJA2KLFLgDV3hHs5YGQuWGzoQyNTcFbIYvCkUQOWLa0s 1N3Ri7a0y5WGA== Message-ID: Date: Mon, 26 May 2025 08:25:50 -0400 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: With poudriere how does one create a jail of a slightly older RELEASE ? Content-Language: en-CA To: freebsd-current@freebsd.org References: From: Dennis Clarke Organization: GENUNIX In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-oetec-MailScanner-Information: Please contact the ISP for more information X-oetec-MailScanner-ID: 54QCPo5r059425 X-oetec-MailScanner: Found to be clean X-oetec-MailScanner-From: dclarke@blastwave.org X-Spam-Status: No X-Rspamd-Queue-Id: 4b5Zjv2CxSz3QL4 X-Spamd-Bar: - X-Spamd-Result: default: False [-1.61 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.997]; NEURAL_SPAM_LONG(0.82)[0.823]; NEURAL_HAM_SHORT(-0.74)[-0.738]; RCVD_DKIM_ARC_DNSWL_MED(-0.50)[]; DMARC_POLICY_ALLOW(-0.50)[blastwave.org,quarantine]; R_SPF_ALLOW(-0.20)[+mx]; R_DKIM_ALLOW(-0.20)[blastwave.org:s=default]; RCVD_IN_DNSWL_MED(-0.20)[108.160.241.186:from]; MIME_GOOD(-0.10)[text/plain]; MIME_TRACE(0.00)[0:+]; HAS_ORG_HEADER(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_ONE(0.00)[1]; ARC_NA(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; TO_DN_NONE(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; DKIM_TRACE(0.00)[blastwave.org:+]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; RCVD_VIA_SMTP_AUTH(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; ASN(0.00)[asn:812, ipnet:108.160.240.0/20, country:CA]; FROM_HAS_DN(0.00)[] On 5/24/25 21:47, Mark Millard wrote: > Dennis Clarke wrote on > Date: Sat, 24 May 2025 22:46:18 UTC : > >> wow ... archive ? Well why not and yes I will give that a whirl. >> >> Still doesn't clear up why I can not build from source but that is a >> whole other matter. > > MFC's do not go back through the whole history I have no idea what "MFC" is supposed to mean. I guess it is a code change that happened somewhere. > making source files compatible with updated > toolchains. Even something like llvm18 can have > where syntax is allowed corrected before llvm19, Got it. The compiler is picky and ever increasingly more picky with each passing year. So stuff from the past that slipped quietly under the radar is now being stomped on as bad stuff. > > In general things are set up to go forward in > small enough jumps, not to go backwards. > So it seems to me that all those branches of stuff named releng/X are going to be just chewing up bandwidth for some values of X. I guess a person could go hunt down that thing called "archive" and install a version of FreeBSD such as 12.2-RELEASE. Then that stuff would be able to build from source. Maybe. Most likely not worth the effort. > The MFC of the source correction to 13.* was made > to 13.3, not to 13.2. See: > > https://cgit.freebsd.org/src/commit/contrib/tzcode/zic.c?h=releng/13.3&id=7ef70d24eee731375fe17a8ef1a30573338d9468 > Nice to know that the change can be found. Way more detail than I would ever need. The first thought that I had after the failure to build a jail was that something much be wrong in 15.0-CURRENT. Turns out that it was something slightly wrong in the code for 13.2-RELEASE. I was able to create the 13.2 jail neatly named 132amd64 and then I took a look at the branch names in ports. Since the 13.2-RELEASE seems to be supported somewhere in mid 2023 it made sense to use package names from a branch such as 2023Q3. That works neatly and I get 481 packages built with zero failures. pluto# uname -a FreeBSD pluto 13.2-RELEASE-p11 FreeBSD 13.2-RELEASE-p11 GENERIC amd64 pluto# pkg query %n\ %v\ %o\ %R\ %a | grep '0$' bind-tools 9.18.19 dns/bind-tools titan 0 bind918 9.18.19 dns/bind918 titan 0 dmidecode 3.5 sysutils/dmidecode titan 0 groff 1.22.4_4 textproc/groff titan 0 iperf3 3.13 benchmarks/iperf3 titan 0 pkg 1.19.2 ports-mgmt/pkg titan 0 smartmontools 7.3_1 sysutils/smartmontools titan 0 tmux 3.3a_1 sysutils/tmux titan 0 pluto# Pretty nifty. The real trick is to upgrade the whole machine but I keep waving my hands at that. I figure 14.3-RELEASE is just days away: https://www.freebsd.org/releases/14.3R/schedule/ So the full upgrade can happen somewhere in June if I can figure out how to deal with the massive zpool this thing is dragging around. There is at least sixteen years of backups of old Sun Solaris stuff as well as a ton of other projects. I am not yet ready to toss that into /dev/null. Thank you again for the great help. I could not get some things done at all if it were not for this mail list. -- -- Dennis Clarke RISC-V/SPARC/PPC/ARM/CISC UNIX and Linux spoken