perl version woe

[Victor Sudakov]

Matthew Seaman wrote:
> > However, could you please explain what is happening below and how I
> > should fix this:
> > 
> > [dd]
> > Fetching postgresql92-client-9.2.10_1.txz: 100%  991 MiB 146.2kB/s    00:36 ETA
> > Fetching php5-pdo_pgsql-5.4.39.txz: 100%   17 KiB  17.6kB/s    00:01
> > Checking integrity... done (2 conflicting)
> > pkg: Cannot solve problem using SAT solver:
> > dependency rule: package php5-extensions(r) depends on: php5-ldap(r)php5-ldap(l)
> > dependency rule: package php5-extensions(l) depends on: php5-ldap(r)php5-ldap(l)
> > upgrade rule: upgrade local php5-ldap-5.4.39 to remote php5-ldap-5.4.39
> > cannot install package php5-ldap, remove it from request? [Y/n]: pkg: cannot find php5-ldap in the request
> > pkg: cannot solve job using SAT solver
> > Checking integrity... done (0 conflicting)
> > Conflicts with the existing packages have been found.
> > One more solver iteration is needed to resolve them.
> > [root at gw /]
> 
> Yes, that does seem pretty bizarre.  At a guess the local and remote
> versions of the package, while having the same name and version number
> have different sets of dependencies (maybe different LDAP versions or
> LDAP with and without SASL?)  

You hit the nail on the head!

My repository has net/openldap24-server without SASL support while the
openldap24-server installed on the host did have SASL support (but I
don't need it any more).

Isn't pkg supposed to handle such collisions gracefully?

[dd]

> 
> Do you have more than one pkg repository configured?  'pkg -vv' will
> show the current state.  If so, then it may be the case that pkg is
> choosing a version from a repository with a different set of
> dependencies compiled in than what you want.  To solve that, be sure to
> upgrade to pkg-1.5.1 as that has CONSERVATIVE_UPGRADE enabled now,
> meaning go back to the same repository the package was originally
> installed from.

No, I don't have multiple repositories. But, as I said before, I have
inherited this host, and it has been updated via portmaster
(WITH_PKGNG of course). The sets of options in my repositories and in
the host's /var/db/ports differ significantly.

I thought pkg would just reinstall all the packages which had options
different from those in the repository. In fact, it has happened
mostly as I had expected, with some bizarre exceptions I have reported
here.

-- 
Victor Sudakov,  VAS4-RIPE, VAS47-RIPN
sip:sudakov at sibptus.tomsk.ru