Date: Fri, 16 Jan 2026 21:46:01 +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-MDS0vqcZN6@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 #15 from Mark Millard <marklmi26-fbsd@yahoo.com> --- (In reply to Graham Perrin from comment #14) Well, re@ never releases any *.0-CURRENT (a.k.a. main), just like they do not release any *.*-STABLE . (snapshots are not the same as a release for the criteria, by the way.) That is a good hint that 15.0-STABLE: pkg query '%m %v' FreeBSD-runtime re@FreeBSD.org 15.snap20260101223705 and main: # pkg query '%m %v' FreeBSD-runtime re@FreeBSD.org 16.snap20260103091340 are just wrong. The *.snap* naming is another hint. There is not even a releng/16.* branch in git existing yet and 15.0-STABLE is based on the stable/15 git branch, not the releng/15.0 git branch. That, in turn, suggests that such output for 14.* and its pkgbase status of being experimental and not supported is also not correctly reflected int any (query or rquery) # pkg query '%m %v' FreeBSD-runtime output. I.e., only for 15.0-RELEASE is such correct output. re@ never does automated twice a day builds and releases. That would like be far off from their criteria for any release. They are always manually involved and not so frequent. pkgbase starts its official re@ status with 15.0-RELEASE releases and updates [-p?] as I understand, not before. And only for -RELEASE[-p?] . -- 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-MDS0vqcZN6>