On Tue, 11 Jan 2011 20:34:45 +0100, Sebastian Pipping wrote:
On 01/11/11 20:13, Jeremy Olexa wrote:
Both of those threads were on new installs. There was a regression
in
stage building for some time that set python3 as the default system
python. That was fixed here:
5 01 Jan 2011; Jorge Manuel B. S. Vicetto
<jmbsvice...@gentoo.org>
6 python-2.6.6-r1.ebuild:
7 Non-maintainer commit.
8 Reverting commit that broke stage generation for
python-2.6.6-r1
as it wasn't
9 reverted before - bug 347867.
10 This commit was accepted by Arfrever.
See also, bug 330655. FWIW, I have recently confirmed that there is
expected behavior now in the stage3-amd64-20110106 tarball.
The commit that was reverted was the one breaking the stages (my
fault).
You may be mixing something up.
Jorge's "revert" fixed the overall issue that I mentioned and the
issues that Paweł and Dale are referring to in the very recent
troubleshooting mediums. I may be mixing up some of the bug numbers, but
it is hard to keep track of all the python3/stage3 issues. So, at least
the week of 20101228 stage3's had python3 set as default python and the
week of 20110106 stage3's had python2.6 again, based on my personal
testing.
15:06 <@darkside_> jmbsvicetto: mr releng. :) the 20101228 i{4,6}86
stages have python-3.1 set as the default system python. is this
intended?
15:07 < jmbsvicetto> darkside_: no :\
15:08 < jmbsvicetto> darkside_: and that would explain some of the
recent mails
15:08 < jmbsvicetto> darkside_: I'll do more tests tonight to see if we
can fix that
<... some days elapsed>
13:50 < jmbsvicetto> darkside_: python-2.6.6-r1 hadn't been reverted.
Now that it is, stage3 shouldn't have python-3.1 as default
-Jeremy
