| 1 |
On 01/11/11 20:13, Jeremy Olexa wrote: |
| 2 |
> On Tue, 11 Jan 2011 19:30:03 +0100, Paweł Hajdan, Jr. wrote: |
| 3 |
>> I've noticed at least two forums threads that suggest there might be a |
| 4 |
>> bug resulting in automatic "flip" of system python to python3: |
| 5 |
>> |
| 6 |
>> http://forums.gentoo.org/viewtopic-t-859654-highlight-.html |
| 7 |
>> http://forums.gentoo.org/viewtopic-p-6541077.html |
| 8 |
>> |
| 9 |
>> Do you think it may be a bug, and if so, how can we debug it? |
| 10 |
> |
| 11 |
> Both of those threads were on new installs. There was a regression in |
| 12 |
> stage building for some time that set python3 as the default system |
| 13 |
> python. That was fixed here: |
| 14 |
> |
| 15 |
> 5 01 Jan 2011; Jorge Manuel B. S. Vicetto <jmbsvicetto@g.o> |
| 16 |
> 6 python-2.6.6-r1.ebuild: |
| 17 |
> 7 Non-maintainer commit. |
| 18 |
> 8 Reverting commit that broke stage generation for python-2.6.6-r1 |
| 19 |
> as it wasn't |
| 20 |
> 9 reverted before - bug 347867. |
| 21 |
> 10 This commit was accepted by Arfrever. |
| 22 |
> |
| 23 |
> See also, bug 330655. FWIW, I have recently confirmed that there is |
| 24 |
> expected behavior now in the stage3-amd64-20110106 tarball. |
| 25 |
|
| 26 |
The commit that was reverted was the one breaking the stages (my fault). |
| 27 |
You may be mixing something up. |
| 28 |
|
| 29 |
|
| 30 |
|
| 31 |
Sebastian |
Archives