since a few days (more specific since guile 1.8.1 was out/unmasked) whenever i run emerge -auND world i get the following message from portage: ===== emerald ~ # emerge -auND world These are the packages that would be merged, in order: Calculating world dependencies \ !!! Multiple versions within a single package slot have been !!! pulled into the dependency graph: ('ebuild', '/', 'dev-scheme/guile-1.6.8', 'nomerge') pulled in by ('ebuild', '/', 'app-office/gnucash-2.0.4', 'nomerge') ('ebuild', '/', 'dev-scheme/guile-1.8.1-r1', 'merge') pulled in by ('ebuild', '/', 'dev-lang/swig-1.3.31', 'nomerge') ('ebuild', '/', 'media-gfx/graphviz-2.8-r2', 'nomerge') ('ebuild', '/', 'sys-devel/autogen-5.8.8', '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. ===== i just had a look at all mentioned ebuilds gnucash requires guile 1.6* all others require whether >=guile-1.4 or just guile so with my understanding it shouldn't be a problem at all to create a correct dependency graph and install all packages while avoiding the upgrade to guile 1.8* since it's not acceptable by at lease one installed ebuild. so i actually don't know if it's supposed to be that i have to manage portage.mask to mask out all newer ebuilds that would replace a required version/dependency of another ebuild (guile 1.8.1 replace 1.6.8) ? with my understanding of a package management system such system should always try to accomodate all requirements/dependencies of all installed packages and only write such message if the requirements can not be fulfilled at all because of really confliction version requirements (like one requesting guile-1.6* and another one guile-1.8*). actually it's quite annoying to have to keep portage.mask up to date that way that when i want to update the system i have to check if there are packages still in package.mask because of such dependency problems that now may be installed without any conflict anymore. (i hope this lengthy comment is still understandable)
Created attachment 108195 [details] emerge --info
*** This bug has been marked as a duplicate of bug 163368 *** *** This bug has been marked as a duplicate of bug 163368 ***
for the curious me... is this behavior caused by the ebuild with the dependency or by portage unable to build a correct dependency graph or even something else ? if it's portage is it too hard to fix it so a correct graph will be built ?
