Date: Wed, 29 Apr 2026 09:32:44 -0700 From: Mark Millard <marklmi@yahoo.com> To: Anton Shterenlikht <lists@cmplx.uk> Cc: pkgbase@freebsd.org Subject: Re: [HEADS UP] stable/15: new base packages for PAM, zstd Message-ID: <23d5deac-c35c-44f0-9469-7a22772dd54c@yahoo.com> In-Reply-To: <afIlbEf1NGIJkko9@cmplx.uk> References: <adTq6tMP4GWQS35e@amaryllis.le-fay.org> <aeedOZ7VcQAOsQCV@cmplx.uk> <3847a70c-f2d8-4c4a-a5f0-56a4a90168b0@yahoo.com> <aeh6ddAuDClL4YFn@cmplx.uk> <aek7L4X26D0zQTU-@amaryllis.le-fay.org> <aenUvAuAGC8SgpKi__40328.3866167598$1776932059$gmane$org@cmplx.uk> <700c882a-ae24-403a-a8e0-5ceffed569ae@yahoo.com> <aeslKG5UCOmV0ROY@cmplx.uk> <351d3db5-19d0-4652-a44e-b029a8105937@yahoo.com> <afIlbEf1NGIJkko9@cmplx.uk>
index | next in thread | previous in thread | raw e-mail
On 4/29/26 08:36, Anton Shterenlikht wrote:
> On Fri, Apr 24, 2026 at 03:10:07AM -0700, Mark Millard wrote:
>>>>
>>>> So the conversion to pkgbase started from a pnon-pkgbase 15.0 to produce
>>>> a pkgbase 15.0?
>>>
>>> Not sure, maybe I never converted.
>>> What does it mean to have a "pkgbase" system?
>>
>> It seems that you have some sort of partial update to pkgbase.
>>
>> What do the following show:
>>
>> # pkg -v
>>
>> # pkg repos -d
>>
>> # pkg repos -e
>>
>> # pkg info FreeBSD-\*
>>
>> That last could produce over 500 lines.
>
> $ pkg -v
> 2.6.2
> $ pkg repos -d
> $ pkg repos -e
> FreeBSD-ports: {
> url : "pkg+https://pkg.FreeBSD.org/FreeBSD:15:amd64/quarterly",
> enabled : yes,
> priority : 0,
> mirror_type : "SRV",
> signature_type : "FINGERPRINTS",
> fingerprints : "/usr/share/keys/pkg"
> }
> FreeBSD-ports-kmods: {
> url : "pkg+https://pkg.FreeBSD.org/FreeBSD:15:amd64/kmods_quarterly_0",
> enabled : yes,
> priority : 0,
> mirror_type : "SRV",
> signature_type : "FINGERPRINTS",
> fingerprints : "/usr/share/keys/pkg"
> }
> FreeBSD-base: {
> url : "pkg+https://pkg.FreeBSD.org/FreeBSD:15:amd64/base_release_0",
> enabled : yes,
> priority : 0,
> mirror_type : "SRV",
> signature_type : "FINGERPRINTS",
> fingerprints : "/usr/share/keys/pkgbase-15"
> }
As stands, having "enabled : yes" for FreeBSD-base takes explicit
editing. So likely you did so to allow doing the:
pkg install FreeBSD-set-minimal
That enable should only be set to yes just before doing a conversion to
pkgbase or if pkgbase is already in use. (Note: There can be reasons to
have the status be no by default even for systems based on pkgbase. To
some extent the details depends on how old the live pkg version happens
to be.)
> $ pkg info FreeBSD-\*
> FreeBSD-at-15.0
> FreeBSD-audit-lib-15.0
> FreeBSD-blocklist-15.0p3
> FreeBSD-bootloader-15.0
> FreeBSD-bzip2-15.0
> FreeBSD-bzip2-lib-15.0
> FreeBSD-caroot-15.0
> FreeBSD-certctl-15.0
> FreeBSD-clibs-15.0
> FreeBSD-clibs-lib32-15.0
> FreeBSD-cron-15.0
> FreeBSD-ctf-lib-15.0
> FreeBSD-devd-15.0
> FreeBSD-devmatch-15.0p2
> FreeBSD-dhclient-15.0
> FreeBSD-efi-tools-15.0
> FreeBSD-fetch-15.0
> FreeBSD-firmware-iwm-15.0
> FreeBSD-flua-15.0
> FreeBSD-fwget-15.0
> FreeBSD-geom-15.0
> FreeBSD-hyperv-tools-15.0
> FreeBSD-kerberos-lib-15.0
> FreeBSD-kernel-man-15.0
> FreeBSD-libarchive-15.0
> FreeBSD-libbsdstat-15.0
> FreeBSD-libcasper-15.0
> FreeBSD-libexecinfo-15.0
> FreeBSD-libldns-15.0
> FreeBSD-libmagic-15.0
> FreeBSD-libucl-15.0
> FreeBSD-libyaml-15.0
> FreeBSD-locales-15.0
> FreeBSD-mandoc-15.0
> FreeBSD-natd-15.0
> FreeBSD-ncurses-15.0
> FreeBSD-ncurses-lib-15.0
> FreeBSD-newsyslog-15.0
> FreeBSD-nuageinit-15.0
> FreeBSD-openssl-15.0p2
> FreeBSD-openssl-lib-15.0p2
> FreeBSD-periodic-15.0
> FreeBSD-pkg-bootstrap-15.0
> FreeBSD-powerd-15.0
> FreeBSD-ppp-15.0
> FreeBSD-rc-15.0
> FreeBSD-rescue-15.0p5
> FreeBSD-resolvconf-15.0
> FreeBSD-runtime-15.0p6
> FreeBSD-set-minimal-15.0
> FreeBSD-syslogd-15.0
> FreeBSD-tcpd-15.0
> FreeBSD-ufs-15.0
> FreeBSD-ufs-lib-15.0
> FreeBSD-utilities-15.0p1
> FreeBSD-vi-15.0
> FreeBSD-vt-data-15.0
> FreeBSD-wpa-15.0
> FreeBSD-xz-lib-15.0
> FreeBSD-zfs-15.0
> FreeBSD-zfs-lib-15.0
> FreeBSD-zlib-15.0
> FreeBSD-zoneinfo-15.0
> $
I've not validated all of it but that looks like a probable match to
FreeBSD-set-minimal .
>
>
>>
>>> How can I check?
>>>
>>> BTW, I noticed that my versions diverged somehow:
>>>
>>> # freebsd-version -kru
>>> 15.0-RELEASE-p4
>>> 15.0-RELEASE-p4
>>> 15.0-RELEASE-p6
>>
>> This is what happens when one of the following is true:
>>
>> ) only the world had updates available, the kernel had no changes
>> ) there were kernel updates that were not applied
>>
>>>
>>>>
>>>> Did you use https://github.com/FreeBSDFoundation/pkgbasify to do the
>>>> conversion (no matter which FreeBSD version was the starting point)?
>>>
>>> no
>>>
>>> Does this mean my system is *not* a pkgbase system?
>>
>> You appear to have at least some pkgbase packages installed, but
>> possibly not an appropriate set of them.
>
> yes, likely...
>
> I get this:
>
> # /home/as/pkgbasify.lua
> Error: The system is already using pkgbase.
> Pass --force to run pkgbasify anyway, for example to fix a partial conversion.
>
> I don't remember invoking pkgbasify before.
>
> should I --force it?
Note: I have never used the force option.
A basic question that would direct what you should do . . .
Which do you want as the basis for your environment:
) pkgbase?
) What you had before (reverting the partial pkgbase install to no
longer be registered as pkgbase materials)?
You have the choice of which direction to go.
>
>>
>>> I.e. one must use pkgbasify, as per
>>> https://wiki.freebsd.org/action/show/pkgbase
>>> to convert an non-pkgbase 15.0 to a pkgbase 15.0?
>>
>> For your conversion . . .
>>
>> Did you try to follow the steps of the "Manual initial setup", despite
>> them being older than covering conversion for 15.0?
>
> not yet
I was not trying to suggest that you do so: just trying to be sure of
how you got to where you are.
>
>>
>> Did you instead try one of the U[pgrades proedures (Minor vs. Major?)?
>> "13 to 14"? "Building'?
>>
>
> I just followed the standard freebsd-update route from 14 to 15.
>
>>>
>>> I assumed that all I need is /etc/pkg/FreeBSD.conf
>>> with ports, ports-kmods and FreeBSD-base.
>>
>> You had to use something that involved actual pkg commands in order to
>> have the .pkgsave files generated. Merely having the configuration
>> file(s) present would not cause that.
>
> yes, I used "pkg upgrade", "pkg update", and the usual
> "pkg clean", "pkg autoremove" after upgading to 15.0.
> This upgraded all ports.
> I got into problems only after "pkg install FreeBSD-set-minimal",
That last is what gave you a partial pkgbase system. Prior to that you
had no FreeBSD-* packages installed --and so did not have a system with
any registered base packages. Note the unique naming convention:
FreeBSD- prefixed package names, capitalization being important.
> which I did after reading what Lexi Winter posted:
>
> *quote*
> if you do *not* have set-minimal installed (because you didn't install
> with bsdinstall, or because you removed it after installation), you MUST
> install the FreeBSD-pam package, otherwise you will no longer be able to
> log into the system after updating.
> *end quote*
It is possible to have a system based pkgbase without the
FreeBSD-set-minimal base package being installed at the time. The above
was only intended to cover that specific type of context. It did not
intend to apply to either of:
) systems with no FreeBSD-* base packages installed/registered
) systems with appropriate FreeBSD-* base packages installed that
included FreeBSD-set-minimal being installed (and, so, registered)
>
> Thank you
>
> Anton
>
>
--
===
Mark Millard
marklmi at yahoo.com
home |
help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?23d5deac-c35c-44f0-9469-7a22772dd54c>