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 1Q3AlM-0005a3-58 for garchives@archives.gentoo.org; Fri, 25 Mar 2011 17:25:28 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 78E2B1C013; Fri, 25 Mar 2011 17:23:42 +0000 (UTC) Received: from minas.ics.muni.cz (minas.ics.muni.cz [147.251.4.40]) by pigeon.gentoo.org (Postfix) with ESMTP id 119A91C013 for ; Fri, 25 Mar 2011 17:23:41 +0000 (UTC) Received: from anxur.fi.muni.cz (anxur.fi.muni.cz [147.251.48.3]) by minas.ics.muni.cz (8.13.8/8.13.8/SuSE Linux 0.8) with ESMTP id p2PHNdWI000515 for ; Fri, 25 Mar 2011 18:23:40 +0100 Received: from palantir.doma (89-24-146-54.adsl.tmcz.cz [89.24.146.54]) by anxur.fi.muni.cz (Postfix) with ESMTP id 5EA4570042 for ; Fri, 25 Mar 2011 18:23:39 +0100 (CET) Date: Fri, 25 Mar 2011 18:23:40 +0100 From: Roman Zilka To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Problem with python-updater ? Message-Id: <20110325182340.81473ac2.zilka@fi.muni.cz> In-Reply-To: <4D8CC025.6050307@numericable.fr> References: <4D8CC025.6050307@numericable.fr> X-Mailer: Sylpheed 3.0.2 (GTK+ 2.22.1; x86_64-pc-linux-gnu) 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 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Muni-Spam-TestIP: 147.251.48.3 X-Muni-Envelope-From: zilka@fi.muni.cz X-Muni-Virus-Test: Clean X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (minas.ics.muni.cz [147.251.4.35]); Fri, 25 Mar 2011 18:23:41 +0100 (CET) X-Archives-Salt: X-Archives-Hash: 623f268ffc90dda629a785750bff9c36 Jacques Montier (Fri, 25 Mar 2011 17:17:41 +0100): > Hi all, > > I upgraded python2.6 to python2.7, > then i run eselect python set python2.7, > then python-updater. > > Here is the python-updater output : > > * Starting Python Updater... > * Main active version of Python: 2.7 > * Active version of Python 2: 2.7 > * Active version of Python 3: 3.1 > * Adding to list: app-emulation/emul-linux-x86-baselibs:0 > * Adding to list: app-emulation/virtualbox-bin:0 > * Adding to list: app-office/libreoffice-bin:0 > * Adding to list: dev-libs/boost:1.42 > * check: manual [Added to list manually, see CHECKS in manpage for > more information.] > * Adding to list: sys-libs/tdb:0 > * Adding to list: x11-libs/vte:0 > * check: manual [Added to list manually, see CHECKS in manpage for > more information.] > * emerge -Dv1 --keep-going app-emulation/emul-linux-x86-baselibs:0 > app-emulation/virtualbox-bin:0 app-office/libreoffice-bin:0 > dev-libs/boost:1.42 sys-libs/tdb:0 x11-libs/vte:0 > ............................... > Ok, everything emerge fine. > > If i run python-updater again, then i get exactly the same output as > before (emerging emul-linux-x86-baselibs:0, BOOST:1.42, etc...) > > What's wrong ?? According to the list of checks python-updater performs it's indeed weird that it's happening. But maybe python-updater has some undocumented, hidden intelligence.:) If you run emerge or something written in python, do you see (in the process listing) /usr/bin/python2.7 being the interpreter in action? If so, try moving away /usr/lib/python2.6 and /usr/bin/python2.6 (just moving away, not deleting). Does still everything run? Then I believe you can safely get rid of python 2.6 and python-updater will probably stop trying to re-emerge everything. -rz