"
Looks like you're in a much better place now. The downgrade/reinstall path you followed is basically the correct recovery procedure when pkg gets replaced by the FreeBSD version instead of the OPNsense-maintained one. The locked package was probably what kept the system stuck in that broken state and prevented normal upgrades from fixing themselves automatically.
The remaining "database version 37 is newer than libpkg(3) version 36" warnings are pretty normal after forcing pkg backwards. Usually they disappear after the next proper pkg update cycle once everything is aligned again. The important thing is that your health audit now completes without repository mismatch or dependency errors.
I'd probably run another reboot just to ensure no stale libraries or processes are hanging around, then do another update check afterwards. If the segfaults are gone and the repo mismatch stays resolved, you should be fine.
Also worth checking that none of the FreeBSD repos are enabled anywhere under pkg config. That's often how these situations start in the first place, especially after experimenting with plugins or third-party instructions.
The remaining "database version 37 is newer than libpkg(3) version 36" warnings are pretty normal after forcing pkg backwards. Usually they disappear after the next proper pkg update cycle once everything is aligned again. The important thing is that your health audit now completes without repository mismatch or dependency errors.
I'd probably run another reboot just to ensure no stale libraries or processes are hanging around, then do another update check afterwards. If the segfaults are gone and the repo mismatch stays resolved, you should be fine.
Also worth checking that none of the FreeBSD repos are enabled anywhere under pkg config. That's often how these situations start in the first place, especially after experimenting with plugins or third-party instructions.
