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
