I'm not mixing ports and pkgs (only pkgs) and have only one server following -RELEASE, but I seem to be trying to answer the same question ("why does pkg upgrade want to install this seemingly unrelated pkg"), so this might be a simpler scenario to consider for the same outcome.
I'm currently using PostgreSQL v15.1 server and client, and "pkg upgrade" wants to install postgresql16-client v16.6. Why? I presume it's because the upgrade version for one of the packages already installed has itself a dependency on v16 of the postgresql client.
Looking at the list of pkgs that "pkg upgrade" wants to upgrade, php81-pdo_pgsql seems the likely suspect and indeed freshports.org reports the latest version has a dependency on postgresql16-client:
I assume the installed version of php81-pdo_pgsql has a dependency on postgresql15-client (since I don't have postgresql16-client installed), but am getting lost trying to figure out from the repo exactly when the dependency change from PostgreSQL v15 to v16 happened.
For now, I'm going to "pkg lock" php81-pdo_pgsql, upgrade everything else, and plan an upgrade from PostgreSQL v15 to v16 before things get any worse.
Did I miss anything?
I'm currently using PostgreSQL v15.1 server and client, and "pkg upgrade" wants to install postgresql16-client v16.6. Why? I presume it's because the upgrade version for one of the packages already installed has itself a dependency on v16 of the postgresql client.
Code:
dale@whizzer:/usr/local/www/weberp $ pkg info | grep -i postgres
postgresql15-client-15.10 PostgreSQL database (client)
postgresql15-server-15.10 PostgreSQL is the most advanced open-source database available anywhere
Code:
dale@whizzer:/usr/local/www/weberp $ sudo pkg upgrade
Updating FreeBSD repository catalogue...
FreeBSD repository is up to date.
All repositories are up to date.
Checking for upgrades (135 candidates): 100%
Processing candidates (135 candidates): 100%
The following 139 package(s) will be affected (of 0 checked):
New packages to be INSTALLED:
hwdata: 0.390,1
openh264: 2.3.0,2
openjph: 0.18.2
postgresql16-client: 16.6
Installed packages to be UPGRADED:
ImageMagick7: 7.1.1.26_5 -> 7.1.1.26_6
aom: 3.10.0_1 -> 3.11.0
apr: 1.7.3.1.6.3_1 -> 1.7.5.1.6.3_3
<snip>
php81-pdo_pgsql: 8.1.29 -> 8.1.31
<snip>
webp: 1.4.0_1 -> 1.5.0
x265: 3.6 -> 3.6_1
xmlsec1: 1.3.5 -> 1.3.6
xxd: 9.1.0764 -> 9.1.0984
Installed packages to be REINSTALLED:
apache24-2.4.62 (required shared library changed)
serf-1.3.10_1 (required shared library changed)
Number of packages to be installed: 4
Number of packages to be upgraded: 133
Number of packages to be reinstalled: 2
The process will require 35 MiB more space.
543 MiB to be downloaded.
Proceed with this action? [y/N]: n
dale@whizzer:/usr/local/www/weberp $Looking at the list of pkgs that "pkg upgrade" wants to upgrade, php81-pdo_pgsql seems the likely suspect and indeed freshports.org reports the latest version has a dependency on postgresql16-client:
Code:
Library dependencies:
libpq.so.5 : databases/postgresql16-clientI assume the installed version of php81-pdo_pgsql has a dependency on postgresql15-client (since I don't have postgresql16-client installed), but am getting lost trying to figure out from the repo exactly when the dependency change from PostgreSQL v15 to v16 happened.
For now, I'm going to "pkg lock" php81-pdo_pgsql, upgrade everything else, and plan an upgrade from PostgreSQL v15 to v16 before things get any worse.
Did I miss anything?
