The Package manager "pkg" is incompatible and needs a reinstall

[blizzard97]

***GOT REQUEST TO UPGRADE***
Currently running OPNsense 26.1.11_10 (amd64) at Wed Jul 15 09:28:13 PDT 2026
Fetching packages-26.7-amd64.tar: ............................................................................................. done
Fetching base-26.7-amd64.txz: ........... done
Fetching kernel-26.7-amd64.txz: ....... done
Flushing temporary package files... done
Extracting packages-26.7-amd64.tar... done
Extracting base-26.7-amd64.txz... done
Extracting kernel-26.7-amd64.txz... done
Please reboot.
>>> Invoking upgrade script 'sanity.sh'
The Package manager "pkg" is incompatible and needs a reinstall.
>>> Error in upgrade script '10-sanity.sh'
The upgrade was aborted due to an error.
***DONE***

[franco]

# pkg lock -y pkg
# opnsense-revert pkg

[wincent]

Just like my situation, I encountered this error while upgrading from 26.1.11_10 to 26.7. After running the command:

Code Select Expand

# pkg lock -y pkg
# opnsense-revert pkg
I successfully upgraded to 26.7, but still encountered pkg compatibility issues, and then I try to reinstall it again, still warning!

Code Select Expand

pkg-static: warning: database version 38 is newer than libpkg(3) version 36, but still compatible

[franco]

> pkg-static: warning: database version 38 is newer than libpkg(3) version 36, but still compatible

It doesn't go away since the newer version tainted the database. In practice that's ok unless it complains about not being compatible. In this case only opnsense-bootstrap will help.


Cheers,
Franco

[wincent]

Okay, then forget about it. I don't want to reinstall all core system packages.

[franco]

Yeah I think you're fine.  We're aiming to udate the package manager for 26.7.x in 6-8 weeks.  The reason why we are so slow is to avoid major upgrade problems with new introduced versions upstream.  Can't afford to catch a regression at the end/beginning of a major cycle.