| 1 |
>> "If your currently installed version of python reported by python -V |
| 2 |
>> is less than 2.6 then you must choose a version of portage that is |
| 3 |
>> compatible with it. If you have at least python 2.6 then use |
| 4 |
>> portage-2.1.10.41.tar.bz2. If you have python 2.4 or 2.5 then use |
| 5 |
>> portage-2.1.6.tar.bz2." |
| 6 |
>> |
| 7 |
>> I get: |
| 8 |
>> |
| 9 |
>> # python -V |
| 10 |
>> Python 2.5.2 |
| 11 |
>> |
| 12 |
>> and I'm already on portage-2.1.6.13 which is non-functional since it |
| 13 |
>> doesn't have high enough EAPI support for current ebuilds. |
| 14 |
>> |
| 15 |
>> I think I'm stuck between a python and portage upgrade. I can't |
| 16 |
>> update python with my current portage and I can't update portage with |
| 17 |
>> my current python. |
| 18 |
> |
| 19 |
> The blockages you posted relate to Python 2.7 and the latest portage. |
| 20 |
> What happens if you install python:2.6, either through portage or a |
| 21 |
> tarball. |
| 22 |
> |
| 23 |
> Try emerge -1a python:2.6 |
| 24 |
|
| 25 |
I get: |
| 26 |
|
| 27 |
# emerge -1a python:2.6 |
| 28 |
[snip] |
| 29 |
[ebuild NS ] dev-lang/python-2.6.7-r2 [2.5.2-r7] USE="gdbm ncurses |
| 30 |
readline ssl threads (wide-unicode) xml -berkdb -build -doc -examples |
| 31 |
-ipv6 -sqlite -tk -wininst" |
| 32 |
[blocks B ] >=dev-lang/python-2.6.6:2.6 |
| 33 |
(">=dev-lang/python-2.6.6:2.6" is blocking sys-apps/portage-2.1.6.13) |
| 34 |
[blocks B ] <sys-apps/portage-2.1.9 ("<sys-apps/portage-2.1.9" is |
| 35 |
blocking dev-lang/python-2.6.7-r2) |
| 36 |
|
| 37 |
* Error: The above package list contains packages which cannot be |
| 38 |
* installed at the same time on the same system. |
| 39 |
|
| 40 |
('ebuild', '/', 'dev-lang/python-2.6.7-r2', 'merge') pulled in by |
| 41 |
python:2.6 |
| 42 |
|
| 43 |
- Grant |
Archives