Re: An odd vital FreeBSD-set-* result?

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

> Mark Millard wrote in <D00275AE-2E13-45AC-AAF4-D5410E07553E@yahoo.com>:
>> But the following indicates that the cached *.pkg files themselves
>> agree with the just-4-vitals status:
> 
> do you build your packages with "make update-packages"?  if so, can you
> try deleting your ${REPODIR} and rebuilding, so all packages are
> recreated?

I never build packages (and I've not done any system builds
in a vey long time, never having packaged one that I did build):
what I use for pkgbase testing is official upstream material
from https://pkg.freebsd.org/ via pkg-static that is using:

# cat /usr/local/etc/pkg/repos/FreeBSD-base.conf 
FreeBSD-base: {
    url: "pkg+http://pkg.FreeBSD.org/${ABI}/base_latest",
    mirror_type: "srv",
    signature_type: "fingerprints",
    fingerprints: "/usr/share/keys/pkg",
    enabled: yes
}

There is no build of mine to be oddly done in some way.

> i'm wondering if adding the vital flag (but not changing anything else)
> doesn't cause update-packages to actually update the package.

Unsure.

>> Also of note is the lack of a new-line between the prior } and the
>> name: for most of the above. An example of a surrounding context is:
>> 
>> categories: [
>>    "base"
>> ]
>> annotations: {
>>    FreeBSD_version: "1600000"
>> }name: "FreeBSD-set-base-dbg"
>> origin: "base"
> 
> it looks the UCL output from 'pkg info' doesn't have a trailing newline.
> i think this is a pkg(8) bug, but it shouldn't have anything to do with
> this issue.
> 
> to confirm, this is the full output i get for the set-src package, using
> 'echo' to force a trailing newline:
> 
> # pkg info -R -F /build/packages/base/FreeBSD:16:amd64/latest/FreeBSD-set-src-16.snap20250919160159.pkg; echo
> name: "FreeBSD-set-src"
> origin: "base"
> version: "16.snap20250919160159"
> comment: "System source code"
> maintainer: "re@FreeBSD.org"
> www: "https://www.FreeBSD.org"
> abi: "FreeBSD:16:amd64"
> arch: "freebsd:16:x86:64"
> prefix: "/"
> flatsize: 0
> licenselogic: "single"
> licenses: [
>    "BSD2CLAUSE"
> ]
> vital: true
> desc: "This metapackage installs source code for the base system and kernel."
> deps: {
>    FreeBSD-src: {
>        origin: "base",
>        version: "16.snap20250919160159"
>    },
>    FreeBSD-src-sys: {
>        origin: "base",
>        version: "16.snap20250919160159"
>    }
> }
> categories: [
>    "base"
> ]
> annotations: {
>    FreeBSD_version: "1600000"
> }
> #
> 
> other than the vital flag, does this match what you have?

Again: the following are from upstream, official builds, not
from me building or packaging anything. Note that it is not
the same snapshot that you show: It is from when I happened
to fetch the official materials of the time. But you can see
the exact snapshot naming, including the timestamp part
below.

 # find -s /var/ -name 'FreeBSD-set-src*.pkg' -print
/var/cache/pkg/FreeBSD-set-src-16.snap20250916221226.pkg
/var/cache/pkg/FreeBSD-set-src-16.snap20250916221226~cfde358ad0.pkg

# pkg info -R -F /var/cache/pkg/FreeBSD-set-src-16.snap20250916221226~cfde358ad0.pkg ; echo
pkg: Warning: Major OS version upgrade detected.  Running "pkg bootstrap -f" recommended
name: "FreeBSD-set-src"
origin: "base"
version: "16.snap20250916221226"
comment: "System source code"
maintainer: "re@FreeBSD.org"
www: "https://www.FreeBSD.org"
abi: "FreeBSD:16:amd64"
arch: "freebsd:16:x86:64"
prefix: "/"
flatsize: 0
licenselogic: "single"
licenses: [
    "BSD2CLAUSE"
]
desc: "This metapackage installs source code for the base system and kernel."
deps: {
    FreeBSD-src: {
        origin: "base",
        version: "16.snap20250916221226"
    },
    FreeBSD-src-sys: {
        origin: "base",
        version: "16.snap20250916221226"
    }
}
categories: [
    "base"
]
annotations: {
    FreeBSD_version: "1600000"
}
#

The snapshot name and the vital line's status seem to be
the differences between your example and mine.

===
Mark Millard
marklmi at yahoo.com