From owner-freebsd-pkg@FreeBSD.ORG Fri Apr 17 09:42:40 2015 Return-Path: Delivered-To: freebsd-pkg@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 64076BD3 for ; Fri, 17 Apr 2015 09:42:40 +0000 (UTC) Received: from relay2.tomsk.ru (mail.sibptus.tomsk.ru [212.73.124.5]) by mx1.freebsd.org (Postfix) with ESMTP id 7A93521F for ; Fri, 17 Apr 2015 09:42:39 +0000 (UTC) X-Virus-Scanned: by clamd daemon 0.98.5_1 for FreeBSD at relay2.tomsk.ru Received: from admin.sibptus.tomsk.ru ([212.73.125.240] verified) by relay2.tomsk.ru (CommuniGate Pro SMTP 5.1.16) with ESMTPS id 38636944 for freebsd-pkg@freebsd.org; Fri, 17 Apr 2015 15:42:35 +0600 Received: from admin.sibptus.TOMSK.ru (sudakov@localhost [127.0.0.1]) by admin.sibptus.tomsk.ru (8.14.9/8.14.7) with ESMTP id t3H9gXVK045272 for ; Fri, 17 Apr 2015 15:42:35 +0600 (NOVT) (envelope-from vas@mpeks.tomsk.su) Received: (from sudakov@localhost) by admin.sibptus.TOMSK.ru (8.14.9/8.14.7/Submit) id t3H9gX1D045271 for freebsd-pkg@freebsd.org; Fri, 17 Apr 2015 15:42:33 +0600 (NOVT) (envelope-from vas@mpeks.tomsk.su) X-Authentication-Warning: admin.sibptus.TOMSK.ru: sudakov set sender to vas@mpeks.tomsk.su using -f Date: Fri, 17 Apr 2015 15:42:32 +0600 From: Victor Sudakov To: freebsd-pkg@freebsd.org Subject: Re: perl version woe Message-ID: <20150417094232.GB35437@admin.sibptus.tomsk.ru> References: <20150416042738.GA99219@admin.sibptus.tomsk.ru> <552F5FF3.7090908@FreeBSD.org> <20150416080754.GA18442@admin.sibptus.tomsk.ru> <552F7738.1070703@freebsd.org> <20150416164031.GA27284@admin.sibptus.tomsk.ru> <552FEB06.1090800@infracaninophile.co.uk> <20150417035200.GA35437@admin.sibptus.tomsk.ru> <5530D1F3.3050704@infracaninophile.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5530D1F3.3050704@infracaninophile.co.uk> Organization: OAO "Svyaztransneft", SibPTUS X-PGP-Key: http://www.dreamwidth.org/pubkey?user=victor_sudakov X-PGP-Fingerprint: 10E3 1171 1273 E007 C2E9 3532 0DA4 F259 9B5E C634 User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-pkg@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Binary package management and package tools discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Apr 2015 09:42:40 -0000 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@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@sibptus.tomsk.ru