From nobody Wed Mar 11 16:35:31 2026 X-Original-To: freebsd-pkgbase@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 4fWGZd3VPkz6VQ9K for ; Wed, 11 Mar 2026 16:35:37 +0000 (UTC) (envelope-from ivy@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (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 "smtp.freebsd.org", Issuer "R13" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4fWGZd2r3Sz3TXm for ; Wed, 11 Mar 2026 16:35:37 +0000 (UTC) (envelope-from ivy@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1773246937; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=uQQTyMfeEJ1B8yQSXiKmGL2WbvPMqoWBHSQy4dxGU2Y=; b=h5j2LGSpHCJokhQyUszcSQkV1CnAfYNNFaUV1T0CY2q/4ye1pTIbTIsqIsMk2PIfjWenqU wUOLP7jAYkKs/tEP+MIG2ZJZPG4rtN285NdKLcQNtYxSGbRgpGwhhxkfvd9GCvlsU0B4b8 D1iCbCyQhfVenbFuVmz/IUtPZTMYfpEMTHviqR9KmwdAzSU9TtW2pujaYD/k5AQNDzthmP DO/MScdIFrhvTlnsWGUXli5YrrJQdvHgZ5/3DyDn362YRyrRsyrpivynVc+SSYUkxnKMKV 5hzQnGRNh/CRSOaYPHLLGwaAmKu2cfIvOtaRULFJhmrJbSyNPSlRfKjnevzdsA== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1773246937; a=rsa-sha256; cv=none; b=xyaFv2BfJhMmxOqVlZl4N92ukhDq6sAYnR5T+fs4hAN353tr1PuGJ2nJcADNtf5Y/sQuE5 gZmMZSvja20zAGPO2V2eUV4uFyLX6wWJIV3VeJ/MWyMduOkVERZfbvmEs3jDorCgekz5bi 97+X68MPZJvaVk4Mgdq8JMwR5OHbMu2tJlQPelzL8o27g5BhixA06fT7D0PLbnJC3vMTYP O5YALpg7CyxST0y4eQqW4xGDvhMeGVsMIE/nLsI1Pg9GhZuQZZQsz5LhRnL3q5wysnW49+ +5uW//z4Ek7jFL4gIta97ZIicrg+LT1vOwKPIBCbgx725L6LLwEd7GXXnOg87w== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1773246937; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=uQQTyMfeEJ1B8yQSXiKmGL2WbvPMqoWBHSQy4dxGU2Y=; b=oRVjbRmmrzhEYplfUDHurGUw4IREOYDF65Btvt3+EHyp7m5HsXalL9XklR8RulhDLVThYb m6m92ONho6JrA58Pc8R11v1qqDKNKzKu986zuSIi9j9jgYJ+fq2I9frY575bIP0+fKiUIc uK2JW8sOEvLv8uqgxfZqUF9jmKkiUGdLFarazZnIyPib6inXVK3vt9oCf7aKhrYu6KGOBn YLP/61eqhrMRdIV10mJ0nxp/Ha9HfDx+dAqxRfhIfMzyfoX+QT57iIKQC+ExIyCT9AAXl4 VsfyihmF9HFCgunTC3Q14CE/4bkHKkoO0L05P5pK3POqxE6D9XRQHziBGUq/YQ== Received: from amaryllis.le-fay.org (amaryllis.le-fay.org [IPv6:2a00:1098:6b:400::9]) (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 did not present a certificate) (Authenticated sender: ivy/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 4fWGZd0XhrzlrD for ; Wed, 11 Mar 2026 16:35:36 +0000 (UTC) (envelope-from ivy@freebsd.org) Date: Wed, 11 Mar 2026 16:35:31 +0000 From: Lexi Winter To: freebsd-pkgbase@freebsd.org Subject: Re: Patched kernel workflow Message-ID: Mail-Followup-To: freebsd-pkgbase@freebsd.org References: List-Id: Packaging the FreeBSD base system List-Archive: https://lists.freebsd.org/archives/freebsd-pkgbase List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-pkgbase@FreeBSD.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="CA3XIt5Hy349coiJ" Content-Disposition: inline In-Reply-To: --CA3XIt5Hy349coiJ Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable =D0=9C=D0=B8=D0=BA=D0=BE=D0=BB=D0=B0 =D0=9C=D0=B8=D0=BA=D0=BE=D0=BB=D0=B0 w= rote in : > I am the user of FreeBSD 15-STABLE with pkgbase. I have found myself > recently in quick need to modify the sources of kernel in order to > debug/fix issue I was having trouble with. >=20 > I found myself in unpleasant situation where make installkernel complains > about overriding pkgbase kernel and modules, noting that pkg will get out > of sync. >=20 > So I have few questions. First is what exactly happens when pkg gets out = of > sync? because the files on disk no longer match what pkg(8) installed and recorded in its database, it will make incorrect decisions about how to manage those files. for exactly it might incorrectly upgrade or downgrade the kernel, it might install new files that conflict with the currently installed files, or it might leave files on disk when they should be removed. > Second, what is streamlined workflow to build custom kernel and > integrate it into system. =20 if you want to temporary install a different kernel for testing, the simplest way is to use: # make installkernel INSTKERNNAME=3Dtestkernel this will install the new kernel at /boot/testkernel, which will not conflict with your existing pkgbase-managed kernel. you can then boot this new kernel from loader(8) in the usual way. alternatively if you want to manage the kernel yourself and not use pkgbase for it, you can remove the FreeBSD-kernel-generic* packages and run installkernel in the usual way. finally, you could build your own pkgbase repository (see build(7), specifically on "update-packages") and then update from there. > I have heard that you should use Poudriere to build packages, and in my > case it this would mean having custom src git tree and every time new > package needs to be build - a merge should happen in that git tree. some people use poudriere to build pkgbase packages, but it's not the case that you "should" do this. more like, you may choose to do that if it fits into your existing workflow. i personally don't because i think it makes things unnecessarily complicated. > Currently Im viewing options to convert my 15-STABLE from pkgbase to > source-based, i.e. building world and kernel from sources. you can do this using: # pkg unregister -fg 'FreeBSD-*' you will need to disable the FreeBSD-base repository afterwards. make sure you take a backup or BE snapshot being doing that, just in case. --CA3XIt5Hy349coiJ Content-Type: application/pgp-signature; name=signature.asc -----BEGIN PGP SIGNATURE----- iHUEABYKAB0WIQSyjTg96lp3RifySyn1nT63mIK/YAUCabGZzwAKCRD1nT63mIK/ YMqnAP9kaU2V1OfG7ihiqCql9L3A9YkLqkRPtRRajvKOxHlnLAEA1Wb1gY6Y6dGI 1aYQSqnhJlDD7DixK8LhynYKVYY9Lwo= =c9kB -----END PGP SIGNATURE----- --CA3XIt5Hy349coiJ--