Updating vim and vim-core to latest stable releases (7.1.042) breaks latest portage-stable gvim (7.0.235) Perhaps I just synced at a bad time.. !!! Multiple versions within a single package slot have been !!! pulled into the dependency graph: ('ebuild', '/', 'app-editors/vim-core-7.0.235', 'merge') pulled in by ('installed', '/', 'app-editors/gvim-7.0.235', 'nomerge') ('installed', '/', 'app-editors/vim-core-7.1.042', 'nomerge') pulled in by ('installed', '/', 'app-editors/vim-7.1.042', 'nomerge') It may be possible to solve this problem by using package.mask to prevent one of those packages from being selected. However, it is also possible that conflicting dependencies exist such that they are impossible to satisfy simultaneously. If such a conflict exists in the dependencies of two different packages, then those packages can not be installed simultaneously. For more information, see MASKED PACKAGES section in the emerge man page or refer to the Gentoo Handbook. !!! Depgraph creation failed. Reproducible: Always Steps to Reproduce: 1. Sync portage tree 2. run vim, vim-core updates 3. start gvim 7.0.x Actual Results: see description Expected Results: I imagine gvim 7.1.x should be marked stable in the tree, to go with the 7.1.x vim and vim-core
(In reply to comment #0) > Perhaps I just synced at a bad time.. yeah, resync.
Oh well, apparently noone did this yet.
*** This bug has been marked as a duplicate of bug 185677 ***
