I have a specific question, which I think leads into a more generic one about understanding
I'm in the midst of upgrading a system from 13.0 to 13.1, and
I'm puzzled, because I don't understand why pkg wants to install openldap24-client. Checking with
This isn't out of the blue, because the machine does have openldap26-client and -server (ie, later versions) installed from ports:
But I don't see the logic that means that the presence of those portmaster-installed ports leads
I would have thought that
I am aware that the handbook does say ‘it is generally ill-advised’ to use pkg and ports together (quarterly vs HEAD, etc), but I'm also aware, from these forums and elsewhere, that it's OK in practice more often than not, and I do seem to have got away with this (convenient) configuration in the past.
So the questions are:
* Why is pkg trying to install openldap24-client?
* Is this in fact indicating that my pkg-vs-ports luck has run out? If so, what is pkg saying that makes that explicit, and how do I work out what the precise nature of that out-of-luck is? (that last question is really ‘am I really going to have to have another go with poudriere?’)
* How do I get pkg to be a little more forthcoming about the logic of its conclusions?
Thanks for any pointers,
Norman
pkg logic.I'm in the midst of upgrading a system from 13.0 to 13.1, and
pkg upgrade tells me
Code:
The following 17 package(s) will be affected (of 0 checked):
New packages to be INSTALLED:
libpsl: 0.21.1_4
openldap24-client: 2.4.59_4
Installed packages to be UPGRADED:
bash: 5.1.12 -> 5.1.16
ca_root_nss: 3.71 -> 3.78
curl: 7.80.0 -> 7.84.0
gettext-tools: 0.21 -> 0.21_1
icu: 70.1_1,1 -> 71.1,1
libltdl: 2.4.6 -> 2.4.7
lmdb: 0.9.29,1 -> 0.9.29_1,1
mercurial: 6.0 -> 6.1.4
nss-pam-ldapd-sasl: 0.9.11_1 -> 0.9.12_1
portmaster: 3.20 -> 3.21
py38-setuptools: 57.0.0 -> 62.1.0_1
python38: 3.8.12_1 -> 3.8.13_2
sudo: 1.9.8p2 -> 1.9.11p3
zsh: 5.8 -> 5.9
Installed packages to be REINSTALLED:
dialog4ports-0.1.6_1 (option removed: ACCESSLOG)I'm puzzled, because I don't understand why pkg wants to install openldap24-client. Checking with
pkg info -d, none of the currently installed packages have a dependency on it. In the absence of a --why-on-earth-would-you-want-to-do-that option for pkg, I'm scratching my head.This isn't out of the blue, because the machine does have openldap26-client and -server (ie, later versions) installed from ports:
Code:
% pkg lock -l
Currently locked packages:
cyrus-sasl-2.1.27_2
cyrus-sasl-saslauthd-2.1.27_2
openldap26-client-2.6.1
openldap26-server-2.6.1_1But I don't see the logic that means that the presence of those portmaster-installed ports leads
pkg update to try to downgrade them. Is pkg perhaps spotting the presence of files installed by openldap26-{client,server} and jumping to the conclusion that they were put there by openldap24, which it's therefore repairing? That seems... unlikely.I would have thought that
pkg info -d <packagename> would have represented all of the information that pkg uses for its upgrade decisions, but that's clearly not the case.I am aware that the handbook does say ‘it is generally ill-advised’ to use pkg and ports together (quarterly vs HEAD, etc), but I'm also aware, from these forums and elsewhere, that it's OK in practice more often than not, and I do seem to have got away with this (convenient) configuration in the past.
So the questions are:
* Why is pkg trying to install openldap24-client?
* Is this in fact indicating that my pkg-vs-ports luck has run out? If so, what is pkg saying that makes that explicit, and how do I work out what the precise nature of that out-of-luck is? (that last question is really ‘am I really going to have to have another go with poudriere?’)
* How do I get pkg to be a little more forthcoming about the logic of its conclusions?
Thanks for any pointers,
Norman
