> Yes, I see /var/db/pkgin/pkgin.db is an sqlite3 database, but > being entirely unfamiliar with its use and its schema, can > someone please supply some commands to inspect the dependency > information for a given package as stored in that database? I > assume that this is the place where the information from > pkg_summary.bz2 is being stored as part of "pkgin up", and is > subsequently used to compute what to do during execution of > "pkgin fug"? To answer myself: # sqlite3 /var/db/pkgin/pkgin.db SQLite version 3.26.0 2018-12-01 12:34:55 Enter ".help" for usage hints. sqlite> select PKG_ID from [REMOTE_PKG] where PKGNAME = "llvm"; 6257 sqlite> select * from remote_depends where pkg_id=6257; 6257|libxml2>=2.14.2nb1|libxml2 6257|python312>=3.12.0|python312 6257|zstd>=1.3.6|zstd sqlite> This is from a pkg installation which was last updated on December 12, 2025. For good measure I've taken a copy of this pkgin.db for posterity on this "new" NetBSD/amd64 10.0 system which is slated for a 2025Q3 to 2025Q4 pkg upgrade. Subsequently I did: # pkgin up processing remote summary (https://cdn.NetBSD.org/pub/pkgsrc/packages/NetBSD/amd64/10.0/All)... pkg_summary.bz2 100% 4224KB 422.4KB/s 00:10 # (and took a copy of the resulting pkgin.db) and a new sqlite3 session: # sqlite3 /var/db/pkgin/pkgin.db SQLite version 3.26.0 2018-12-01 12:34:55 Enter ".help" for usage hints. sqlite> select PKG_ID from [REMOTE_PKG] where PKGNAME = "llvm"; 6297 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> sqlite> select PKG_ID from [REMOTE_PKG] where PKGNAME = "python313"; 19631 sqlite> select * from remote_depends where pkg_id=19631; 19631|libffi>=3.4.2nb3|libffi 19631|libuuid>=2.18|libuuid 19631|mpdecimal>=4.0.0|mpdecimal 19631|readline>=6.0|readline 19631|sqlite3>=3.49.1nb3|sqlite3 sqlite> which all looks quite normal, i.e. mpdecimal is among the recursive dependencies of llvm according to the updated sqlite3 database. Trying at this point to do a "pkgin fug" appears it's going to bomb, because python313 isn't included in what needs to be installed to refresh llvm: # pkgin fug 4 packages to refresh: libuuid-2.40.2 llvm-19.1.7 pkg_install-20250417 readline-8.3nb1 4 packages to upgrade: pkgin-25.10.0 python311-3.11.14 python312-3.12.12 sqlite3-3.51.1 0 to remove, 4 to refresh, 4 to upgrade, 0 to install 135M to download, 485K of additional disk space will be used proceed ? [Y/n] and I aborted this suggestion by answering "n". I think this is the stage where we need to inspect a bit more what pkgin is up to, and why it's not picking up that python313 (and then mpdecimal) needs to be installed before llvm can be "refreshed". At this stage I'm using: # pkgin -v pkgin 25.7.0 (using SQLite 3.50.4) # Regards, - Havard