| 1 |
I did python-updater as said by the ebuild. |
| 2 |
After it I did emerge -a --depclean which removed python 2.6 |
| 3 |
Boy I was I happy that I have daily backups. |
| 4 |
portage did not work anymore. |
| 5 |
|
| 6 |
Changing the active python version before running python-updater gives a lot |
| 7 |
more packages. I did portage by hand. Just don't want to restore a backup |
| 8 |
two times a day. |
| 9 |
|
| 10 |
Dale wrote: |
| 11 |
|
| 12 |
> Mark Knecht wrote: |
| 13 |
>> One of my machines just saw a python-2.7 update and the ebuild was |
| 14 |
>> good enough to remind me to run python-updater, but it didn't suggest |
| 15 |
>> that I run eselect python and set the active version to 2.7. |
| 16 |
>> |
| 17 |
>> Should this new version python be selected first as the active python |
| 18 |
>> 2 version and then run python-updater? |
| 19 |
>> |
| 20 |
>> Thanks, |
| 21 |
>> Mark |
| 22 |
>> |
| 23 |
>> |
| 24 |
> |
| 25 |
> And if we should set python to 2.7, should we remove python-2.6? I |
| 26 |
> don't think we want to break something, portage in particular. ;-) |
| 27 |
> |
| 28 |
> Dale |
| 29 |
> |
| 30 |
> :-) :-) |
Archives