Date: Fri, 16 Jan 2026 06:47:48 +0000 From: bugzilla-noreply@freebsd.org To: pkgbase@FreeBSD.org Subject: [Bug 291806] The pkgbase release of 15.0-RELEASE is missing the MINIMAL kernel and several other packages Message-ID: <bug-291806-36141-bKMFswpxe9@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-291806-36141@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=291806 --- Comment #8 from ivy@FreeBSD.org --- i raised this internally with releng and no one seems to have an objection to building multiple kernels, so we're going to start by adding both GENERIC and GENERIC-NODEBUG to the 16.0 snapshot builds and see how that goes. if there are no issues, we'll add GENERIC and GENERIC-DEBUG to the build for 15.1 (hopefully, depending on timing - don't take this as a commitment to doing that). i don't plan to add MINIMAL right now for the reasons in my previous comment; if you want this, i suggest raising it on the arch@ mailing list to see what people think. personally i'm not strongly opposed to it, but i'm also nervous about providing it as part of the release pkgbase builds until it's "ready", since that implies a certain level of support we might not want to commit to. but, if there is consensus on arch@ to add MINIMAL, testing with GENERIC-(NO)DEBUG will make that a lot easier to do. re: bsdinstall, i forgot i fixed the multi-kernels bug already, but it was late enough in the 15.0 release cycle that we couldn't have changed the kernel we ship anyway. (this doesn't allow selecting the kernel in bsdinstall, it just means it doesn't crash if the repository contains more than one.) > The process that builds 15-STABLE makes the minimal kernel package. the packages for STABLE and CURRENT are built by an individual developer and we (releng) aren't involved in that, so the selection of kernels there might differ from what we ship in a release build. > As for the orphaned packages, other packages get deleted by pkg, so why not these listed ones? pkg doesn't normally delete packages on upgrade unless there's a conflict. in this case, the selection of packages you have installed didn't cause a conflict. > Is there some way to tell pkg to go ahead and remove them? you can list the affected packages with "pkg orphans" and remove them with "pkg autoremove". aside from scripting that (which would be fairly trivial) i don't know of a way to do that automatically, but i'm not an expert on pkg. > Just because it is labeled experimental doesn't really mean we should throw up our hands and say too bad, so sad. We can address the shortcomings and make it work better. i can assure you that no one is "throwing up their hands". we did a huge amount of work on pkgbase to get it ready for 15.0 release, and that work is continuing to improve it for 16.0 (and maybe 15.1, depending on what we decide to backport). if you'd like to contribute, there are several open reviews in Phabricator (D54282 and D54542 in particular) related to this, and patches for other improvements would certainly be welcome. -- You are receiving this mail because: You are the assignee for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-291806-36141-bKMFswpxe9>