| 1 |
On Sat, 21 Jan 2012 06:57:32 -0800, Grant wrote: |
| 2 |
|
| 3 |
> "If your currently installed version of python reported by python -V |
| 4 |
> is less than 2.6 then you must choose a version of portage that is |
| 5 |
> compatible with it. If you have at least python 2.6 then use |
| 6 |
> portage-2.1.10.41.tar.bz2. If you have python 2.4 or 2.5 then use |
| 7 |
> portage-2.1.6.tar.bz2." |
| 8 |
> |
| 9 |
> I get: |
| 10 |
> |
| 11 |
> # python -V |
| 12 |
> Python 2.5.2 |
| 13 |
> |
| 14 |
> and I'm already on portage-2.1.6.13 which is non-functional since it |
| 15 |
> doesn't have high enough EAPI support for current ebuilds. |
| 16 |
> |
| 17 |
> I think I'm stuck between a python and portage upgrade. I can't |
| 18 |
> update python with my current portage and I can't update portage with |
| 19 |
> my current python. |
| 20 |
|
| 21 |
The blockages you posted relate to Python 2.7 and the latest portage. |
| 22 |
What happens if you install python:2.6, either through portage or a |
| 23 |
tarball. |
| 24 |
|
| 25 |
Try emerge -1a python:2.6 |
| 26 |
|
| 27 |
or put >dev-lang/python-2.7 in package.mask. |
| 28 |
|
| 29 |
... |
| 30 |
|
| 31 |
Thinking about it, judicious use of package.mask to limit portage to |
| 32 |
small incremental upgrades may be the best approach. |
| 33 |
|
| 34 |
-- |
| 35 |
Neil Bothwick |
| 36 |
|
| 37 |
How stupid are people? Send me to find out. |
Archives