| 1 |
> The root of the problem is really quite simple, you have a system with |
| 2 |
> a python version python-updater doesn't like. The solution is actually |
| 3 |
> quite simple: |
| 4 |
> |
| 5 |
> step 1. update python to 2.5, rebuild cracklib (afaik cracklib is the |
| 6 |
> only system package that requires python), portage, gentookit. |
| 7 |
> step 2. at this point, you can unmerge the old python, some packages |
| 8 |
> *will* break, but you will still have a console that works fine, and |
| 9 |
> your portage is built against the 2.5. |
| 10 |
> step 3. emerge python-updater, since no python-2.3 is present, it'll |
| 11 |
> emerge happily. |
| 12 |
> step 4. run python-updater |
| 13 |
> step 5. voila |
| 14 |
|
| 15 |
A more conservative approach (which shouldn't break anything AFAIK, but will take longer) is; |
| 16 |
1. Run python-updater to move everything from 2.3 to 2.4 |
| 17 |
2. Uninstall python 2.3 |
| 18 |
3. Do your full emerge -uvD to update to python-updater 0.5 and python 2.5 |
| 19 |
4. (optional, you could to it later) run python-updater to move everything from 2.4 to 2.5 |
| 20 |
5. (optional) run prelink again to catch everything that emerge world installed/updated |
Archives