Re: 15.0-ALPHA3 update did not update any FreeBSD-set-*.pkg files in https://pkg.freebsd.org/FreeBSD:15:amd64/base_latest/ ?

On Sep 21, 2025, at 10:58, Lexi Winter <ivy@freebsd.org> wrote:

> Mark Millard wrote in <DAB662E4-AE29-4831-821D-EC87EEB50BF7@yahoo.com>:
>> Looking at https://pkg.freebsd.org/FreeBSD:15:amd64/base_latest/ shows
>> 9 files updated to have FreeBSD-*-15.0.a3.*.pkg names. The rest still
>> have FreeBSD-*-15.0.a2.*.pkg names. The 9 FreeBSD-*-15.0.a3.*.pkg are:
> 
> the timestamp on these packages indicate they were built after ALPHA2,
> but before newvers.sh was updated to ALPHA3.  most likely, re@ ran the
> build several times before updating newvers.sh and did not clean the
> package repository in the interim.
> 
> as long as the contents are correct, this has no impact on pkg, and it's
> expected that the base repository will have different package versions
> because we only update packages which actually changed.

I'm confused by that statement. The below example is not
based on 15.0, but some material from prior main 16
reporting related to FreeBSD-set-* vintages and content,
where some FreeBSD-set-* had not been updated, in this
case FreeBSD-set-src :

deps: {
 FreeBSD-src: {
     origin: "base",
     version: "16.snap20250919160159"
 },
 FreeBSD-src-sys: {
     origin: "base",
     version: "16.snap20250919160159"
 }
}

If the FreeBSD-set-src involved for such is
older than the actual FreeBSD-src and
FreeBSD-src-sys distributed, the "version:"
fields are out of date, as they were in the
main 16 example in question.

If they are ignored/unused and do not track
updates, why are they even present?


===
Mark Millard
marklmi at yahoo.com