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