On 09.08.25 12:59, Lexi Winter wrote:
Florian Smeets:
Yes, I had the same issue yesterday evening. When the system was back, I was
too tired to summarize and send something to the mailing list.

as a workaround, i suggest anyone upgrading pkgbase split the upgrade
into two steps:

        pkg upgrade -r base     # upgrade base
        pkg upgrade -r FreeBSD  # upgrade ports

replace 'base' with whatever your pkgbase repository is called.

I don't think that's going to help / would have helped. I just checked a couple of things. I disabled my ports package repo before running pkg upgrade for it to prevent those listed packages from being removed. The list just showed FreeBSD-* packages that were supposed to be upgraded.

I uploaded the important part of /var/log/messages here
https://people.freebsd.org/~flo/pkg-upgrade-20250808.txt>
as this problem appears to be triggered by something in ports, this
should ensure you don't end up with a broken base system if you run
into this.

Not sure, I pretty certain that I only had pkgbase repo enabled and maybe FreeBSD-kmods. I cannot say with certainty for the kmods as /etc/pkg/FreeBSD.conf was replaced in my recovery attempts.

Florian

Attachment: OpenPGP_0xEF5BA4DCD5A9F3C0.asc
Description: OpenPGP public key

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature

Reply via email to