| 1 |
>>>> I'm getting the following from portage on a critical remote system: |
| 2 |
>>>> |
| 3 |
>>>> <dev-lang/python-2.3.6-r2 (is blocking app-admin/python-updater-0.5, |
| 4 |
>>>> app-admin/python-updater-0.2) |
| 5 |
>>>> |
| 6 |
>>>> Am I suppose to un-emerge python? |
| 7 |
>>>> |
| 8 |
>>>> - Grant |
| 9 |
>>>> |
| 10 |
>>>> |
| 11 |
>>> |
| 12 |
>>> Perhaps you should update your python. Version 2.3 will be removed from |
| 13 |
>>> portage and is currently hardmasked. That triggers the depency bump. |
| 14 |
>>> |
| 15 |
>> |
| 16 |
>> 'emerge -pv python' wants to install python-2.5.2-r5 in a new slot. |
| 17 |
>> Should I unmerge python, emerge the new python, and run |
| 18 |
>> python-updater? Will portage work once python has been unmerged? I'm |
| 19 |
>> being cautious because this is a highly critical system for me. |
| 20 |
>> |
| 21 |
>> - Grant |
| 22 |
>> |
| 23 |
> |
| 24 |
> NO, do not unemerge python befor installing the new one!!! |
| 25 |
> |
| 26 |
> It looks like your python is quite old. do you have version 2.4 installed? |
| 27 |
> Then just do emerge -C =dev-lang/python-2.3.6-r2 and run python-updater |
| 28 |
> afterwards. Otherwise try to emerge python 2.5 in the new slot, run the |
| 29 |
> python-updater and remove version 2.3 afterwards. |
| 30 |
> Nevertheless after updating python-updater you should run " python-updater |
| 31 |
> -ee -v -p" to see what should be still updated. |
| 32 |
|
| 33 |
I've emerged python-2.5 in the new slot, but I can't upgrade from |
| 34 |
python-updater-0.2 to python-updater-0.5 until I un-emerge python-2.3. |
| 35 |
Should I run python-updater-0.2 now, or un-emerge python-2.3, update |
| 36 |
to python-updater-0.5, and run that? If it depends on if I have |
| 37 |
python-2.4 installed or not, how can I check on that? |
| 38 |
|
| 39 |
- Grant |
Archives