On 12/18/25 06:58, Alan Somers wrote:
On Wed, Dec 17, 2025 at 6:54 PM Colin Percival <[email protected]> wrote:
On 12/17/25 15:34, Alan Somers wrote:
On Thu, Nov 27, 2025 at 3:55 PM Colin Percival <[email protected]> wrote:
Due to recent changes in FreeBSD.org infrastructure, systems still running
15.0-{PRERELEASE,ALPHA*,BETA*} (aka anything running 15.0 which hasn't
upgraded to -RC* yet) will find that 'pkg upgrade -r FreeBSD-base' fails,
since the https://pkg.freebsd.org/FreeBSD:15:foo/base_release_0/ repository
(which used to be nightly builds signed with "pkg" keys) has been replaced
by what used to be on pkgbase.freebsd.org.
At present the best path forward for you is probably to use git to check out
the src tree (head, stable/15, or releng/15.0; doesn't matter in this case)
and run the commands
# cp /usr/src/usr.sbin/pkg/FreeBSD.conf.quarterly-release \
/etc/pkg/FreeBSD.conf
# cp -R /usr/src/share/keys/pkgbase-15 /usr/share/keys/pkgbase-15
to get the updated configuration file and signing keys.
I have a system running 15.0-BETA5 with pkgbase. Before I followed
your advice, "pkg upgrade -r FreeBSD-base" simply reported that "Your
packages are up to date", possibly because /etc/pkg/FreeBSD.conf
didn't have any entry for FreeBSD-base (but
/usr/local/etc/pkg/repos/FreeBSD-base.conf did). After running these
commands, now "pkg update" fails with "pkg: No trusted public keys
found". Could you please help me?
What do you have in /usr/local/etc/pkg/repos/FreeBSD-base.conf ?
FreeBSD-base: {
url: "pkg+https://pkg.FreeBSD.org/${ABI}/base_release_0";,
mirror_type: "srv",
signature_type: "fingerprints",
fingerprints: "/usr/share/keys/pkg",
enabled: yes
}
Ah, that explains it. Right, you need to remove everything from there
except the "enabled: yes" part. Otherwise you're overriding the 15.0
release configuration and pointing back at the keys used on BETA5.
--
Colin Percival
FreeBSD Release Engineering Lead & EC2 platform maintainer
Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid
