| 1 |
>> I've emerged python-2.5 in the new slot, but I can't upgrade from |
| 2 |
>> python-updater-0.2 to python-updater-0.5 until I un-emerge python-2.3. |
| 3 |
> |
| 4 |
> That shouldn't happen; there's no rationale in this, unless I'm missing |
| 5 |
> something. |
| 6 |
> |
| 7 |
>> Should I run python-updater-0.2 now, or un-emerge python-2.3, update |
| 8 |
>> to python-updater-0.5, and run that? If it depends on if I have |
| 9 |
>> python-2.4 installed or not, how can I check on that? |
| 10 |
> |
| 11 |
> You shouldn't unmerge old python unless the new one is made fully |
| 12 |
> functional. Post the exact error emerge gives when you try to update |
| 13 |
> python-updater. |
| 14 |
|
| 15 |
# emerge -pv python-updater |
| 16 |
|
| 17 |
These are the packages that would be merged, in order: |
| 18 |
|
| 19 |
Calculating dependencies... done! |
| 20 |
[ebuild U ] app-admin/python-updater-0.5 [0.2] 6 kB |
| 21 |
[blocks B ] <dev-lang/python-2.3.6-r2 (is blocking |
| 22 |
app-admin/python-updater-0.5, app-admin/python-updater-0.2) |
| 23 |
|
| 24 |
Total: 1 package (1 upgrade, 1 block), Size of downloads: 6 kB |
| 25 |
|
| 26 |
- Grant |
Archives