Hmm... I have a theory:
In this pkg installation of 2025Q3 from December 12 2025, I have
the following subsection of local dependencies:
sqlite3 is required by:
pkgin
python311
python312 is required by:
llvm
llvm-19.1.7 depends locally on (according to "pkg_info"):
libxml2>=2.14.2nb1
python312>=3.12.0
zstd>=1.3.6
However, as shown earlier, the new "remote" llvm-19.1.7 (note
same version number) depends on
sqlite> select * from remote_depends where pkg_id=6297;
6297|libxml2>=2.14.2nb1|libxml2
6297|python313>=3.13|python313
6297|zstd>=1.3.6|zstd
sqlite>
which is quite different, and python313 in turn depends on the
"new, not locally installed" mpdecimal package.
So ... the sqlite3 upgrade is triggered by a desire to upgrade
pkgin and what it depends on, this triggers the python312
upgrade, which also triggers a refresh of llvm, but the remote
dependencies of the refreshed llvm are evidently not taken into
consideration when computing what needs to be upgraded and
refreshed, and we bomb in the refresh of llvm due to missing
packages.