From nobody Sat Feb 28 02:02:17 2026 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 4fN7k44NMYz6Tr99 for ; Sat, 28 Feb 2026 02:02:20 +0000 (UTC) (envelope-from agh@riseup.net) Received: from mx0.riseup.net (mx0.riseup.net [198.252.153.6]) (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 (2048 bits) client-digest SHA256) (Client CN "mx0.riseup.net", Issuer "R13" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4fN7k327RSz3DRb for ; Sat, 28 Feb 2026 02:02:19 +0000 (UTC) (envelope-from agh@riseup.net) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=riseup.net header.s=squak header.b=mKY8jVg7; dmarc=pass (policy=none) header.from=riseup.net; spf=pass (mx1.freebsd.org: domain of agh@riseup.net designates 198.252.153.6 as permitted sender) smtp.mailfrom=agh@riseup.net Received: from fews04-sea.riseup.net (fews04-sea-pn.riseup.net [10.0.1.154]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mx0.riseup.net (Postfix) with ESMTPS id 4fN7k150nqz9sjB for ; Sat, 28 Feb 2026 02:02:17 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=riseup.net; s=squak; t=1772244137; bh=wKxD0/ad05Pd7IG0k868lcCl7PmhuUIFp+Vzfoz+1O4=; h=Date:From:To:Subject:In-Reply-To:References:From; b=mKY8jVg7fbKVuFAJKRR+Er0RYK13900iCpfKeuP7U+FoMuuGG/iHOhtA5qtHzXVBP xCq+fVHQJkVTLcilPKVHAzmtk0dxQkR9auKlEREb1XT1voAI2nM/wgcMfZWyZCllER q/3pQ9oebTnVSZh3kN2e4uieSD0zfEtlWorqqOsI= X-Riseup-User-ID: E623A9AFA9D7FF3BCA74D13058A99C7490A655660BFA9FB42B82F92BD26ABC1D Received: from [127.0.0.1] (localhost [127.0.0.1]) by fews04-sea.riseup.net (Postfix) with ESMTPSA id 4fN7k13qq1z5wVX for ; Sat, 28 Feb 2026 02:02:17 +0000 (UTC) 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 Date: Sat, 28 Feb 2026 02:02:17 +0000 From: Alastair Hogge To: freebsd-current@freebsd.org Subject: Re: pkgbase and customised builds via ${SRC}/release/release.sh In-Reply-To: References: <20fb908c0954e62977dffdcd4a883678@riseup.net> Message-ID: Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Spamd-Result: default: False [-3.08 / 15.00]; SUBJECT_HAS_CURRENCY(1.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.98)[-0.980]; DMARC_POLICY_ALLOW(-0.50)[riseup.net,none]; R_SPF_ALLOW(-0.20)[+a:mx0.riseup.net]; R_DKIM_ALLOW(-0.20)[riseup.net:s=squak]; MIME_GOOD(-0.10)[text/plain]; RCVD_IN_DNSWL_LOW(-0.10)[198.252.153.6:from]; DKIM_TRACE(0.00)[riseup.net:+]; RCVD_TLS_ALL(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; RECEIVED_HELO_LOCALHOST(0.00)[]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; MISSING_XM_UA(0.00)[]; ASN(0.00)[asn:16652, ipnet:198.252.153.0/24, country:US]; TO_DN_NONE(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; MID_RHS_MATCH_FROM(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; RCVD_VIA_SMTP_AUTH(0.00)[]; DWL_DNSWL_NONE(0.00)[riseup.net:dkim] X-Rspamd-Queue-Id: 4fN7k327RSz3DRb X-Spamd-Bar: --- On 2025-12-23 18:38, Lexi Winter wrote: Hi Lexi, > Alastair Hogge wrote in <20fb908c0954e62977dffdcd4a883678@riseup.net>: >> pkg: Unable to open plist file: >> /usr/obj/usr/src/amd64.amd64/kernelstage/kernel/kernel.FAFNIR-dbg.plist >>[...] >> What is the method for using release.sh to custom build a pkgbase, that >> also supports tarballs, and install images? > > as far as i'm aware, we don't support building a pkgbase release with > a kernel other than GENERIC. even if the build succeeded, you wouldn't > be able to install using the resulting media since bsdinstall only knows > how to install GENERIC. I have made some progress, yes, it looks like the GENERIC kernel is built and installed, even tho another kernel was the only one configured. > my suggestion for now would be to build the release media with GENERIC, > then put the custom kernels in your base repository and install them > after booting with GENERIC. Thanks, I will see about that. > this is definitely something we want to fix in the future, it just > wasn't critical enough to make the 15.0 release. i have a couple > of other release things i want to fix first, then i'll see about > fixing this, since i also want custom kernels on install media. The biggest problem I had come across, was the "tags=package={foo}" declarations in ${SRC}/etc/mtree/*.dist. I had to remove a couple of these from a 2 or 3 mtree dists. What is going on in this part of the build infrastructure? There is a history of similar commits[1][2][3], to the changes I now have to keep locally, yet, des@ recently added[4] more tags. >From what I understand when investigating this, the build infra uses both the mtree dists, and ${SRC}/release/packages/generate-set-ucl.lua to generate the pkgbase sets? Is that correct? Does that mean there is duplicated work here, and one of these paths is redundant? I also noted that a few WITHOUT_foo options had no effect on the World building stage 1.2, bootstrap tools. Here, when WITHOUT_KERBEROS is defined, it is still built. I even still have a Kerberos KDC pkgbase component. 1: https://codeberg.org/FreeBSD/freebsd-src/commit/00352ef6d2a013650f0ab2a4c9b016c22552ed25 2: https://codeberg.org/FreeBSD/freebsd-src/commit/1fbdb149aa486961c5d9d6403065e90123b3f5fe 3: https://codeberg.org/FreeBSD/freebsd-src/commit/2a8a6179eb6cef8ba1a417a4c8a1f7063c704533 4: https://codeberg.org/FreeBSD/freebsd-src/commit/d4f6cb75424950ee776833ebc6b57855c094a610