Date: Fri, 19 Sep 2025 16:48:11 +0100 From: Lexi Winter <ivy@freebsd.org> To: Mark Millard <marklmi@yahoo.com> Cc: Baptiste Daroussin <bapt@freebsd.org>, FreeBSD-pkgbase@freebsd.org Subject: Re: An odd vital FreeBSD-set-* result? Message-ID: <aM17O4zQDo606x9V@amaryllis.le-fay.org> In-Reply-To: <780BB42C-1EBE-4847-ADE6-F8F6730617B8@yahoo.com> References: <780BB42C-1EBE-4847-ADE6-F8F6730617B8.ref@yahoo.com> <780BB42C-1EBE-4847-ADE6-F8F6730617B8@yahoo.com>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --]
Mark Millard wrote in <780BB42C-1EBE-4847-ADE6-F8F6730617B8@yahoo.com>:
> # pkg-static install -U -rFreeBSD-base -g 'FreeBSD-*'
>
> Afterwards I tried deleting FreeBSD-set-* without force
> being requested and it reported only 4 as vital and
> allowed the others to be deleted:
are you able to reproduce this on a clean system (e.g., in a chroot)?
if so, the particular sequence of commands that triggers it would be
useful to have.
also, please show the output of this command on the affected system:
pkg info | awk '/^FreeBSD-set-/ { print $1 }' | xargs pkg query '%n %V'
i've tested this here and even if FreeBSD-set-src isn't marked as vital
prior to the upgrade, it becomes vital after updating, which seems to be
the expected behaviour from a quick inspection of the pkg(8) source.
[-- Attachment #2 --]
-----BEGIN PGP SIGNATURE-----
iHUEABYKAB0WIQSyjTg96lp3RifySyn1nT63mIK/YAUCaM17OAAKCRD1nT63mIK/
YHHaAP0ZYB8+nkPVMk6gWiYrii5KCFVK/DIT4wpvorM8UIDjVwEAyB4pqymwlK37
RYnwwnOYDd2oZU8Yct/h/LIDvDT9DgU=
=A0/l
-----END PGP SIGNATURE-----
help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?aM17O4zQDo606x9V>