Platform is SUSE 10 Enterprise SP2. Bootstrapping fails with the following console output: hash -r export USE="-berkdb -fortran -gdbm -nls -pcre -ssl" emerge --oneshot sed Traceback (most recent call last): File "/local/tmp/e/usr/bin/emerge", line 36, in ? from _emerge.main import emerge_main File "/local/scratch/nightly/2009-08-19/usr/lib/portage/pym/_emerge/main.py", line 51, in ? from _emerge.actions import action_config, action_sync, action_metadata, \ File "/local/scratch/nightly/2009-08-19/usr/lib/portage/pym/_emerge/actions.py", line 45, in ? from _emerge.depgraph import backtrack_depgraph, depgraph, resume_depgraph File "/local/scratch/nightly/2009-08-19/usr/lib/portage/pym/_emerge/depgraph.py", line 1102 finally: ^ SyntaxError: invalid syntax
I don't really understand the backtrace at all, or why it can't see the functions it is in. The only thing which changed is the bootstrapped version of python (2.6.2 instead of 2.5.2).
18:26 < vraptor> I'm following the Jun 19 Prefix Boostrap on Solaris doc, and am getting a syntax error when I try to use emerge for the one shots in step 1.7 onwards 18:27 < vraptor> no other errors prior to that 18:34 < vraptor> it appears to be complaining about "finally:" in depgraph.py, line 1102 18:37 < vraptor> hrm, my /opt/gentoo/tmp/usr/bin/python is a link to python2.5, but the python created by the bootstrap process is /opt/gentoo/tmp/usr/bin/python2.6 18:42 < vraptor> creating the correct link doesn't resolve the issue, though 18:46 < vraptor> well, oddly, if I explicitly call emerge like so: 18:47 < vraptor> python /opt/gentoo/usr/bin/emerge --oneshot <pkg> 18:47 < vraptor> it works 18:47 < vraptor> will dig around some more, must be an environment issue
I think we solved this in bug #282618
Confirmed, bootstrapping from scratch worked again 2009-08-25 and onwards.
