Re: python313 dependency mismatch?

[Greg Troxel <gdt%lexort.com@localhost>]

Havard Eidnes <he%NetBSD.org@localhost> writes:

> 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.

I picked up a hint, perhaps incorrectly, that you had pkgdb confusion.

I am guessing that pkgin does not directly access PKGDB_DIR.  But if it
does, that's another source of potential trouble.

Before you can expect anything to work, you must reduce confusion about
pkgdb location to zero.   That means exactly one database, and both
base tools and pkg tools configured to use that location.  It is not
clear to me that you are in a healthy state.

Due to the high amount of confusion this change has caused, ~everyone
should have PKG_DBIR set in both /etc/pkg_install.conf and
/usr/pkg/etc/pkg_install.conf.

My view is that in 2026, the only healthy state is to have pkgdb in the
standard location, which on NetBSD is /usr/pkg/pkgdb.  

Maybe that's unrelated to your problem, but I think it's best to firmly
take it off the table.