I've recently done a few pkg upgrades using pkgin, primarily on
amd64 and i386 systems, where the previous update was done some
60 days ago or so.
Some of these end up wanting to install python313, but that fails by
pkg_add because the mpdecimal package could not be installed. But
... isn't that exactly what pkgin is supposed to sort out on its own?
If I manually install mpdecimal before doing "pkgin fug", things go
better.
It's as if the python313 package both needs mpdecimal, and that
it's not declared in the pkg_summary file which pkgin uses?
Has anyone else seen this issue?
No?
Typical failure from pkg_install-err.log which pkgin leaves
behind:
2026-01-22T14:16:55Z [535/539] refreshing p5-GraphViz-2.24nb8...
pkg_add: no pkg found for 'mpdecimal>=4.0.0', sorry.
pkg_add: Can't install dependency mpdecimal>=4.0.0
pkg_add: python313-3.13.11: expected dependency mpdecimal>=4.0.0 still missing
pkg_add: Can't install dependency python313>=3.13
pkg_add: graphviz-12.2.1nb5: expected dependency python313>=3.13 still missing
pkg_add: Can't install dependency graphviz-[0-9]*
pkg_add: p5-GraphViz-2.24nb8: expected dependency graphviz-[0-9]* still missing
pkg_add: 1 package addition failed
Manually installing it seems to bring things along:
# pkgin in mpdecimal
calculating dependencies...done.
1 package to install:
mpdecimal-4.0.1
0 to remove, 0 to refresh, 0 to upgrade, 1 to install
114K to download, 690K of additional disk space will be used
proceed ? [Y/n]
[1/1] mpdecimal-4.0.1.tgz 100% 114KB 114.0KB/s 00:00
[1/1] installing mpdecimal-4.0.1...
pkg_install warnings: 0, errors: 0
reading local summary...
processing local summary...
#
So the repository has it.
But ... why can't pkgin figure out by itself that the
python313-3.13.11 package needs mpdecimal and install it before
trying (and failing) to install python313?