1 |
>>>>> On Mon, 29 Nov 2010, Alex Alexander wrote: |
2 |
|
3 |
> On Mon, Nov 29, 2010 at 04:47:36PM +0100, Arfrever Frehtes Taifersar Arahesis wrote: |
4 |
>> It wasn't any mistake. Please actually read that code: |
5 |
>> |
6 |
>> eselect_python_update() { |
7 |
>> if [[ -z "$(eselect python show --python${PV%%.*})" ]]; then |
8 |
>> eselect python update --python${PV%%.*} |
9 |
>> fi |
10 |
>> } |
11 |
|
12 |
Unfortunately, that doesn't help at all. See below. |
13 |
|
14 |
> I updated two systems and they both switched to 2.7.1 automatically. |
15 |
|
16 |
I guess it is triggered from pkg_postrm() of python-2.6.6-r1 which |
17 |
until two days ago unconditionally called the following eselect |
18 |
action: |
19 |
|
20 |
eselect python update --python2 |
21 |
|
22 |
So unless you had updated your python-2.6 during the last two days, |
23 |
the installed version in your VDB would still contain the above line. |
24 |
|
25 |
> They were working fine with 2.6 before the update. |
26 |
|
27 |
If it ain't broke, don't fix it? ;-) |
28 |
|
29 |
Ulrich |