"
pkg_add: Installed package `postgresql14-client-14.23' conflicts with `postgresql1[0-35-9]-client-[0-9]*' when trying to install `postgresql16-client-16.14'.
"

Wait. What?

#pkgsrc

@jspath55 Wow. Never seen that before, ... and can't reproduce it here :( (NetBSD aarch64 11.99.6, pkg_admin 20260227):

> pkg_admin pmatch 'postgresql1[0-35-9]-client-[0-9]*' 'postgresql14-client-14.23' && echo match
>

What version of the pkg_install tools do you have?

#pkgsrc

@agc Can't find a version numbers, but late 2024?

-r-xr-xr-x 1 root wheel 117568 Dec 16 2024 /usr/sbin/pkg_admin

I have an issue with PGSQL versions conflicting with #QGIS installs, where it seems to only like version 16. Long story, starting with testing QGIS 4 from pkgsrc work in progress.

Most likely a local glitch. :/

Edit:

For:
$ pkgin show-deps "qgis" | grep -i client

I get:
postgresql16-client>=16.0nb1

(implying v14 won't work, but 16, 17, *or* 18 *should* be okay.)

@jspath55 pkg_admin -V should help with the version info.

Sorry, but I don't know much about pkgin, that's more @jperkin so I may be completely off base about the #pkgsrc tools in use here?

Glad you found out why it's forcing postgresql 16 though 😃

@agc @jspath55 that's a limitation with how dependencies are currently done for postgresql (and mariadb/mysql), where they only depend on the default. I've had a branch for ages that fixes this for my repositories, but have not yet summoned the courage to propose integrating it. #pkgsrc
@jperkin @agc @jspath55 that's a big windmill, but worth the tilt...
@abs0 @jperkin @agc I started with trying out #QGIS4 and opened several worm cans/holes since. Checking out the geo-PDF feature is impending.
I took screenshots before I reverted the wip. Write-up here:
https://jspath55.blogspot.com/2026/06/forward-with-qgis-4-and-netbsd-11-and.html
Forward with QGIS 4 and NetBSD 11 and more

 A week ago, based on a tip from Greg T, I build QGIS 4.0 on a NetBSD 10.1 system. It worked, after arranging the work-in-progress snapshot....