>>> You could do:
>>>
>>> emerge =dev-lang/python-2.6.7-r2
>>>
>>> You should disable "threads" if it doesn't work (there is
>>> something related to it in the portage ebuild). After that,
>>> switch to python 2.6 via eselect and try to update portage. If I
>>> read the ebuilds correctly, that should work.
>>
>> I get:
>>
>> # emerge -av1 =dev-lang/python-2.6.7-r2 [snip] [ebuild NS ]
>> dev-lang/python-2.6.7-r2 [2.5.2-r7] USE="gdbm ncurses readline ssl
>> threads (wide-unicode) xml -berkdb -build -doc -examples -ipv6
>> -sqlite -tk -wininst" 10,840 kB [blocks B ]
>> >=dev-lang/python-2.6.6:2.6 (">=dev-lang/python-2.6.6:2.6" is
>> blocking sys-apps/portage-2.1.6.13) [blocks B ]
>> <sys-apps/portage-2.1.9 ("<sys-apps/portage-2.1.9" is blocking
>> dev-lang/python-2.6.7-r2)
>>
>> Total: 6 packages (5 new, 1 in new slot), Size of downloads: 11,588
>> kB Conflict: 2 blocks (2 unsatisfied)
>>
>> * Error: The above package list contains packages which cannot be *
>> installed at the same time on the same system.
>>
>> ('ebuild', '/', 'dev-lang/python-2.6.7-r2', 'merge') pulled in by
>> =dev-lang/python-2.6.7-r2
>>
>>> Another possibility would be to install a 3.x version of python
>>> and switch portage to that (via the python3 useflag).
>>
>> I get:
>>
>> # emerge -av1 =dev-lang/python-3.1.4-r3 [snip] !!! All ebuilds that
>> could satisfy "=dev-lang/python-3.1.4-r3" have been masked. !!! One
>> of the following masked packages is required to complete your
>> request: - dev-lang/python-3.1.4-r3 (masked by: EAPI 3)
>>
>> The current version of portage supports EAPI '2'. You must upgrade
>> to a newer version of portage before EAPI masked packages can be
>> installed.
>>
>> - Grant
>>
> Could you try:
>
> emerge =python-2.6.6-r2 -v1
I get the same thing unfortunately.
- Grant
