From owner-freebsd-pkg@FreeBSD.ORG Sat May 30 02:44:04 2015 Return-Path: Delivered-To: freebsd-pkg@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 27EC1ECB for ; Sat, 30 May 2015 02:44:04 +0000 (UTC) (envelope-from jeffreybouquet@yahoo.com) Received: from nm24-vm0.bullet.mail.bf1.yahoo.com (nm24-vm0.bullet.mail.bf1.yahoo.com [98.139.213.161]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id DC020137D for ; Sat, 30 May 2015 02:44:03 +0000 (UTC) (envelope-from jeffreybouquet@yahoo.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1432953667; bh=MBo1J6at7VGPYCodYYDUv1oDh7kUQQ9RHuvhHKuiAV4=; h=Date:From:To:Subject:References:In-Reply-To:From:Subject; b=apXuzPYRcKtmffBe8uiBFNdH0yQ/hFVS1OLXd5gCI4a+CfWmB/9MCUzlu+hLSKFPJXEA4uEvToUnuPXF5EKCjhN/REswU7FR86X6k/Wwf1DJ14rn3JXM1PzLKf2kxsYRUsyPATaeb5h6RjqOBQqXYyGHX0ocxmq20Q4xOFRzkxVsHZa/XuT2f4sc8pRXu35B49dogW1LpN3lS6xUuId7grPd6LeCWPpXy0P1ZZK2/jXoSbs8g4abX5CARTexqia++2e+Relv0PFLYmMIGFBd317KwLUHZAB274Nw8nimNEmWN4IFCGCmFn/OFtRr9QKAuIekmhiZ78tC+n7G8DEhsg== Received: from [98.139.170.182] by nm24.bullet.mail.bf1.yahoo.com with NNFMP; 30 May 2015 02:41:07 -0000 Received: from [98.139.211.201] by tm25.bullet.mail.bf1.yahoo.com with NNFMP; 30 May 2015 02:41:07 -0000 Received: from [127.0.0.1] by smtp210.mail.bf1.yahoo.com with NNFMP; 30 May 2015 02:41:07 -0000 X-Yahoo-Newman-Id: 35798.41451.bm@smtp210.mail.bf1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: gswVeyIVM1ke5MMtXG_x2NMw5lB1rVKomW8Eow7acOJUPmH ISmWicwXIqEGte_crhxPZyAWkMMmLrH43X0YTy1OJmMmPZSecP7sJ8l6MRX0 n902kLnzw7XirqEZ8lbpTRlVe_CxpAx6xQ75cuRIgCH2aMRnpW.wdT4DMPv1 5o87xp.lCDoSfDNXKJQIoNtN_ZfQaDQFNjAzLprbQTD.jvzcAMw0JdQq0hfI L6iE6WZVA6c.56VeUSSiaZQ3IPD7eWD16PSUriatjhUR5slfDAERJPjwTGLn rqfhkxrHaOozBFl0jksorIUI4kVCPR2niVFkmjk_BT756rZ_LpxzrBzNpMDE 0fGbvX469RyliCYEvihlZHY7NDs_SraejoUWZsclW0FYxtzBybn9YtD83nEP YlgecpTHCpCXjVmJIuOkZi1PrELLG8ed2Xt7TXkJNQTYVE7_jOPNrHQMOkYV bHrjvW0b6yDjwzsp1vSO08zKgNeCjHv5ec4NgSamLU2oHrNuxNwbcM2SahFd pBV_RcDL_yZMkahDBsyyviknPIx8oJzPbAgXZ X-Yahoo-SMTP: 6IZaPQyswBAeyzp3urHRlQfBxGxx4Js3YAIn Message-ID: <556922F5.6030407@yahoo.com> Date: Fri, 29 May 2015 19:39:49 -0700 From: Jeffrey Bouquet User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: freebsd-pkg@freebsd.org Subject: Re: SOLVED pkg problem again (pkg upgrade, specifically) References: <5568B9FE.6000106@yahoo.com> In-Reply-To: <5568B9FE.6000106@yahoo.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit 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: Sat, 30 May 2015 02:44:04 -0000 On 05/29/15 12:11, Jeffrey Bouquet via freebsd-pkg wrote: > I can install packages but not use package upgrade, it piecemeal wants > to remove AFAIK practically all of the ports, which I can then reinstall > with portupgrade: > portupgrade -PP -i -f zinf > > ........................................................ > Script started on Fri May 29 12:00:41 2015 command: > /usr/local/sbin/pkg-static upgrade Updating FreeBSD repository > catalogue... FreeBSD repository is up-to-date. All repositories are > up-to-date. Checking for upgrades (1824 candidates): 0% Checking for > upgrades (1824 candidates): 0% Checking for upgrades (1824 candidates): > 1% Checking for upgrades (1824 candidates): 2% Checking for upgrades > (1824 candidates): 3% Checking for upgrades (1824 candidates): 4% > Checking for upgrades (1824 candidates): 5% Checking for upgrades (1824 > candidates): 6% Checking for upgrades (1824 candidates): 7% Checking for > upgrades (1824 candidates): 8% Checking for upgrades (1824 candidates): > 9% Checking for upgrades (1824 candidates): 10% Checking for upgrades > (1824 candidates): 11% Checking for upgrades (1824 candidates): 12% > Checking for upgrades (1824 candidates): 13% Checking for upgrades (1824 > tes): 47% Checking for upgrades (1824 candidates): 48% Checking > 1824 candidates): 13% Processing candidates (1824 > ates): 47% Processing candidates (1824 candidates): 48% Processing > ccandidates (1824 candidates): 97% Processing candidates (1824 > candidates): 100% > > pkg-static: Cannot solve problem using SAT solver: upgrade rule: upgrade > local xpn-1.2.6_5 to remote xpn-1.2.6_5 > cannot install package xpn, remove it from request? [Y/n]: n > pkg-static: cannot solve job using SAT solver Script done on Fri May 29 > 12:01:04 2015 > > ....................................................................................... > So xpn, pkg cannot , delete xpn > then AFAIK twenty x.... ports need removal > then twenty w.... > then twenty v... > approximate of course, but since I already "pkg check -Ba " and "pkg > update -f " etc... > This was working in the v10 before the upgrade to v11, AND was working > on the v11 system > the upgrade (/usr/src and /usr/obj) were used for. So why when all was > in place for an > upgrade, would "pkg upgrade" be unworkable again? > > To complicate matters, the database file is (3xxx ports) too large to > send for debugging AFAIK. > I suppose "pkg upgrade" could be enhanced to due more before halting, or > print a more > precise error. Even twenty lines of debugging to be posted somewhere... > > .............................................................. > Also I thought, pkg should itself have an UPDATING file, since > the rewrite of configuration files, possible bootstrap, commands which > work better and > which work worse across major updates, etc etc. It appears even maybe pkg > "forgot" about installed ports upon a simple v10 > v11 upgrade, > luckily I had the previous > backup to list the ports from and do some shell pipes so most (not all) > are reinstalled as I > write this. Although I have not double checked. > ..................................................................... > _______________________________________________ I ran pkg upgrade with the DEBUG_LEVEL=4. File resulting was too large to send by email. I grepped out "remote" to a text file, ran that file through a pipe to just get the port [ abi change update] [grep, awk ...] >> next file, then looped through that one updating.................................. "pkg update" works again. [lines containing remote contained the ABI ports needing updating ] Did not get to test: can not solve >> pkg install just one can not solve >> pkg install just one ... etc to see if that would fix the pkg upgrade command by use of the pkg install command. That may have been another way. Unsure. Another quirk updating v10 > v11, which fixed perl here, To update by package one port, hundreds were removed unequivocally. So I scripted that, so had a list from which to reinstall. No time to reinstall all of those at the moment, unfortunatly, too many p5-... Next, I used a backup v10 local.sqlite and a new v11 local.sqlite, ran pkg query on them both, and used the 'diffp' (a MOVED obsolete command) to install piecemeal the ones on the left pane (sort of like mergemaster) [diffp on the resulting text files from each database, 2 total...] So it seems all fixed here for now. Sorry to not provide context in more detail for the procedure/fixes above. No time.