From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1M381G-0006MI-US for garchives@archives.gentoo.org; Sun, 10 May 2009 12:20:39 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 423B8E01AF; Sun, 10 May 2009 12:20:37 +0000 (UTC) Received: from smtpout.karoo.kcom.com (smtpout.karoo.kcom.com [212.50.160.34]) by pigeon.gentoo.org (Postfix) with ESMTP id 047F5E01AF for ; Sun, 10 May 2009 12:20:36 +0000 (UTC) X-IronPort-AV: E=Sophos;i="4.40,323,1238972400"; d="scan'208";a="96526205" Received: from unknown (HELO compaq.stroller.uk.eu.org) ([213.152.39.90]) by smtpout.karoo.kcom.com with ESMTP; 10 May 2009 13:20:35 +0100 Received: from [192.168.1.71] (unknown [192.168.1.71]) by compaq.stroller.uk.eu.org (Postfix) with ESMTP id 2E022137CB2 for ; Sun, 10 May 2009 13:20:33 +0100 (BST) Message-Id: <6CE63CF5-9432-4ED4-A4CB-ACF8A49E29DA@stellar.eclipse.co.uk> From: Stroller To: gentoo-user@lists.gentoo.org In-Reply-To: <1430318F-36A1-4095-B8DE-014A1915AC67@gmail.com> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org Mime-Version: 1.0 (Apple Message framework v930.3) Subject: Re: [gentoo-user] how to recover a portage that wasn't in use for very long time Date: Sun, 10 May 2009 13:20:31 +0100 References: <1430318F-36A1-4095-B8DE-014A1915AC67@gmail.com> X-Mailer: Apple Mail (2.930.3) X-Archives-Salt: ce7b6973-fa9a-4794-bf4d-cf1b067e6d9b X-Archives-Hash: 965bd3ff3bcf2ec748757b1b60e4d795 On 10 May 2009, at 01:58, Alexey Luchko wrote: > ... > But then I've got the following collision. Obviously, a portage > update is required. But it is confused by dependencies: > colinux ~ # emerge portage --pretend --tree > > These are the packages that would be merged, in reverse order: > > Calculating dependencies... done! > [nomerge ] sys-apps/portage-2.1.6.11 [2.1.2.2] > [ebuild U ] app-shells/bash-3.2_p39 [3.1_p17] USE="-examples% - > plugins%" > [ebuild U ] sys-apps/portage-2.1.6.11 [2.1.2.2] > [ebuild U ] dev-python/pycrypto-2.0.1-r6 [2.0.1-r5] > [ebuild U ] sys-apps/sandbox-1.6-r2 [1.2.17] > [ebuild N ] app-arch/lzma-utils-4.32.7 USE="-nocxx" > [ebuild N ] app-admin/eselect-news-20080320 > [ebuild U ] app-admin/eselect-1.0.11-r1 [1.0.7] USE="-vim- > syntax%" > [ebuild U ] app-misc/pax-utils-0.1.19 [0.1.15] > [blocks B ] bash-3.2_p39) > colinux ~ # Hi there, I have done some similar kinds of updates. Once stuff has been removed from the tree it becomes a bit painful. I have had success, however, reading the blocked ebuilds to find which versions of dependency ebuilds are required, and then getting them from Gentoo's CVS "attic" . You can place these in your local overlay and then `emerge =category/package-version` to overcome the blocker. This is probably a fair bit of work - one machine here is so old that I accept I'll never get it updated (and a reinstall will be required, when I get around to it), on another the work is not complete. On that latter machine I have successfully updated some important packages to the latest version (previously updated September 2007) by using this method, but it required at least 2 or 3 blockers manually resolved this way, and it did "feel" ugly. I suggest frequent use of `revdep- rebuild`, `python-updater` and whatever else you can think of. `emerge -pv --update world` on that machine still shows 202 packages in need of updating, so this will need repeating a number of times. I think a number of people here would tell you that this isn't worthwhile, to back up /home directories & config files and to reinstall, but personally I'm reluctant to do that in the case of a working system on which users depend. So it _does_ appear possible to upgrade using this tedious method. In your case, I think you would first try to emerge =sys-apps/ portage-2.1.5, in order to unblock app-shells/bash-3.2_p39. This will (surely) result in another blocker - resolve that first, then emerge =sys-apps/portage-2.1.5 then try again to upgrade to the latest portage. Good luck! Stroller.