Re: python313 dependency mismatch?

[Havard Eidnes <he%NetBSD.org@localhost>]

> Read thoroughly:
>
>   https://www.pkgsrc.org/pkgdb-change/
>
> For bonus points, set the wayback machine to January of 2021
> and read it then :-)

Please be a bit more specific.

As I understand it, the problem I am observing is caused by pkgin
not adhering to the declared "remote" pkg dependencies.

The web page above about the location of the local pkg database
and its move to /usr/pkg/pkgdb/ only affects the *local* storage
of package install list and pkg dependencies.

So to my mind obviously "getting the locally installed list of
packages" by pkgin depends on it looking in the right spot (it
does appear to do so), but either there's something wrong with
the "only install pkgin, pkg_install and its dependencies"
operation which somehow mistakenly includes llvm in the list of
packages to install, or it fails to properly include the
recursive remote dependencies of llvm which includes python313
and mpdecimal.

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.

I would not be surprised if I'm "too alone" in having llvm
installed, and that being caused by having rust installed...

Regards,

- Håvard