Summary: | media-gfx/blender-2.78a-r1 !!! Multiple package instances within a single package slot have been pulled !!! into the dependency graph, resulting in a slot conflict: | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | tman <cornicx> |
Component: | Current packages | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
tman
2017-01-30 00:07:24 UTC
Try adding liborcus too - IIRC portage doesn't consider all rebuilds outside of @world. I used to have to switch between boost versions frequently while adding support for openshadinglanguage, and encountered this issue every time I needed to downgrade or upgrade boost. You can get a more complete list of the packages which are conflicting if you run # emerge -uDN --verbose-conflicts blender As a workaround I couldn't find a better way than uninstalling boost, boost-build, blender and all of the conflicting packages (making a list as you do so) and reinstalling them. So I would try to uninstall the 8 or so packages listed by # emerge -uDN --verbose-conflicts blender using # emerge --unmerge blender boost boost-build liborcus ... (I didn't use emerge -pvc blender boost boost-build liborcus ... as it reduces the number of packages you need to remove and later recompile, none of the conflicting packages on my system were critical) Then try to reinstall just boost, boost-build and blender # emerge -1av --verbose-conflicts boost boost-build blender Continue to uninstall further conflicting packages until this succeeds Lastly reinstall the remaining conflicting packages # emerge -1v liborcus ... and add blender back to the world set # emerge --noreplace blender *** This bug has been marked as a duplicate of bug 607244 *** This is similar to bug 607244 in the sense that "partial" updates are error-prone, as described in bug 607244, comment #8. |