Created attachment 377092 [details] emerge --info Portage dependency resolver bails out in some occasions: lebrodyl ~ # emerge -Du world These are the packages that would be merged, in order: Calculating dependencies... done! Traceback (most recent call last): File "/usr/bin/emerge", line 50, in <module> retval = emerge_main() File "/usr/lib64/portage/pym/_emerge/main.py", line 1037, in emerge_main return run_action(emerge_config) File "/usr/lib64/portage/pym/_emerge/actions.py", line 4061, in run_action emerge_config.args, spinner) File "/usr/lib64/portage/pym/_emerge/actions.py", line 320, in action_build settings, trees, myopts, myparams, myaction, myfiles, spinner) File "/usr/lib64/portage/pym/_emerge/depgraph.py", line 8403, in backtrack_depgraph myaction, myfiles, spinner) File "/usr/lib64/portage/pym/_emerge/depgraph.py", line 8435, in _backtrack_depgraph success, favorites = mydepgraph.select_files(myfiles) File "/usr/lib64/portage/pym/_emerge/depgraph.py", line 3093, in select_files return self._select_files(args) File "/usr/lib64/portage/pym/_emerge/depgraph.py", line 3429, in _select_files return self._resolve(myfavorites) File "/usr/lib64/portage/pym/_emerge/depgraph.py", line 3584, in _resolve self.altlist() File "/usr/lib64/portage/pym/_emerge/depgraph.py", line 6229, in altlist self._resolve_conflicts() File "/usr/lib64/portage/pym/_emerge/depgraph.py", line 6356, in _resolve_conflicts self._process_slot_conflicts() File "/usr/lib64/portage/pym/_emerge/depgraph.py", line 1212, in _process_slot_conflicts self._solve_non_slot_operator_slot_conflicts() File "/usr/lib64/portage/pym/_emerge/depgraph.py", line 1130, in _solve_non_slot_operator_slot_conflicts forced.add(nodes[0]) IndexError: tuple index out of range In some occasions means, in certain setup (see example below), some execution of 'emerge -vaDu world' works fine (dependency resolver finishes properly and portage exits due to unsatisfied package dependencies), while later (no changes in setup, just running emerge again) may yield mentioned dependency resolver exception. I can reproduce the problem with the following example setup: 1. amd64 base 2. ~amd64 kde-4.13.1 (although I don't expect it to change anything) 3. problem appears after additionally unkeywording/unmasking "live" kdepim version 4.9999 from kde overlay. Such setup should cause dependency failure (our 'live' kde packages require all other kde packages to be live as well, in test setup I just "wished to install" 'live' kdepim).
Created attachment 377094 [details] success.txt This is what is expected to happen all the time in given setup :)
*** This bug has been marked as a duplicate of bug 510270 ***
