Apparently, though unproven, at 19:10 on Monday 02 May 2011, Mick did opine thusly:
> On Monday 02 May 2011 17:05:08 Davide Carnovale wrote: > > @alan, no error are printed, where and what should i look for in the > > logs? > > > > @helmut python just returns to the console, without error or effect of > > any sort, does it means python has get unmerged and that's why emerge > > doesn't work anymore? > > I'll guess, since everybody else is, that you updated python to 2.7, then > did *NOT* run python-update, did not use eselect to change to 2.7, but > *DID* run emerge --depclean which removed dev-lang/python-2.6.6-r2. > > So, to find out what happened trawl through /var/log/emerge.log and then > look at the messages you got in /var/log/portage/elog/summary.log for > advice as to what you missed doing. If you have genlop installed, genlop -u python will show if python was unmerged recently. (emerge logs are almost impossible to scan by eye as the timestamps are epoch time) -- alan dot mckinnon at gmail dot com
