Date: Tue, 12 May 2026 07:21:53 -0700 From: Mark Millard <marklmi@yahoo.com> To: =?UTF-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@FreeBSD.org> Cc: freebsd-pkgbase@freebsd.org Subject: Re: pkgbasify and pkg, pkgbase installs/upgrades where kernel functionality has changed/grown: not fully handled Message-ID: <55f9b1cd-bff7-43d0-874e-cb569329f12f@yahoo.com> In-Reply-To: <868q9prlfh.fsf@ltc.des.dev> References: <ffd74c1f-0d4a-45aa-9ad5-27a26ff9c846@yahoo.com> <868q9prlfh.fsf@ltc.des.dev>
index | next in thread | previous in thread | raw e-mail
On 5/12/26 03:06, Dag-Erling Smørgrav wrote: > Mark Millard <marklmi@yahoo.com> writes: >> I recently did a pkgbasify to get to 14.4-STABLE from notably older >> media by content --but from after 14.0 was branched. > > I really don't recommend that. Upgrade to 15 first, then pkgbasify. > > DES Understood as a general procedure. I normally avoid 14.* and pkgbase, even for poudriere-devel jails. Also, in my normal upstream pkgbase usage procedures I do upgrade kernels and such and then reboot to use them before doing the pkgbase world install: I normally still follow the old procedures in that respect. But I also tend to sometimes do experiments that might produce results to report on. In this case, I expected that I remembered a kernel change would show up for the world install for what I tried and wanted to see how/if it was handled. It was not handled. If such was a 15.* context with a kernel change that the install procedure would try to put to use, it still would have failed from doing things in the wrong order for such a a context. Most of my normal activity is with main, not stable/* or releng/*.* . I do use pkgbase for 15.* poudriere-devel jails. After the experiment that I reported on, I did a pkgbase upgrade to main via my normal procedures so I no longer have a pkgbase 14.* context active. -- === Mark Millard marklmi at yahoo.comhome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?55f9b1cd-bff7-43d0-874e-cb569329f12f>