When I try to emerge www-apache/mod_perl using "emerge -av www-apache/mod_perl" I get a trace. Reproducible: Always Steps to Reproduce: 1. emerge -av www-apache/mod_perl 2. 3. Actual Results: Traceback (most recent call last): File "/usr/bin/emerge", line 51, in <module> retval = emerge_main() File "/usr/lib/portage/pym/_emerge/main.py", line 1057, in emerge_main return run_action(emerge_config) File "/usr/lib/portage/pym/_emerge/actions.py", line 4067, in run_action emerge_config.args, spinner) File "/usr/lib/portage/pym/_emerge/actions.py", line 320, in action_build settings, trees, myopts, myparams, myaction, myfiles, spinner) File "/usr/lib/portage/pym/_emerge/depgraph.py", line 8439, in backtrack_depgraph myaction, myfiles, spinner) File "/usr/lib/portage/pym/_emerge/depgraph.py", line 8471, in _backtrack_depgraph success, favorites = mydepgraph.select_files(myfiles) File "/usr/lib/portage/pym/_emerge/depgraph.py", line 3129, in select_files return self._select_files(args) File "/usr/lib/portage/pym/_emerge/depgraph.py", line 3465, in _select_files return self._resolve(myfavorites) File "/usr/lib/portage/pym/_emerge/depgraph.py", line 3620, in _resolve self.altlist() File "/usr/lib/portage/pym/_emerge/depgraph.py", line 6265, in altlist self._resolve_conflicts() File "/usr/lib/portage/pym/_emerge/depgraph.py", line 6392, in _resolve_conflicts self._process_slot_conflicts() File "/usr/lib/portage/pym/_emerge/depgraph.py", line 1241, in _process_slot_conflicts self._solve_non_slot_operator_slot_conflicts() File "/usr/lib/portage/pym/_emerge/depgraph.py", line 1159, in _solve_non_slot_operator_slot_conflicts forced.add(nodes[0]) IndexError: tuple index out of range Expected Results: The ebuild should be emerged like any other Portage 2.2.12-r1 (python 3.3.5-final-0, default/linux/x86/13.0/developer, gcc-4.8.3, glibc-2.19-r1, 3.10.55-desper i686) I don't know if that ebuild failure somehow depends on my current Python migration (with still many ebuilds to be re-emerged due to the Python 2.6 removal) Other ebuilds build fine, however.
*** This bug has been marked as a duplicate of bug 510270 ***