https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=291806
--- Comment #15 from Mark Millard <[email protected]> --- (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 [email protected] 15.snap20260101223705 and main: # pkg query '%m %v' FreeBSD-runtime [email protected] 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.
