# emerge -uDN blender * IMPORTANT: 4 news items need reading for repository 'gentoo'. * Use eselect news read to view new items. Calculating dependencies... done! [ebuild U ] dev-util/boost-build-1.63.0 [1.62.0-r1] [ebuild r U ] dev-libs/boost-1.63.0 [1.62.0-r1] [ebuild rR ] media-libs/openimageio-1.6.13 [ebuild rR ] 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: dev-libs/boost:0 (dev-libs/boost-1.63.0:0/1.63.0::gentoo, ebuild scheduled for merge) pulled in by (no parents that aren't satisfied by other packages in this slot) (dev-libs/boost-1.62.0-r1:0/1.62.0::gentoo, installed) pulled in by >=dev-libs/boost-1.51.0:0/1.62.0= required by (dev-libs/liborcus-0.11.2:0/0.11::gentoo, installed) ^^^^^^^^^^ (and 8 more with the same problem) NOTE: Use the '--verbose-conflicts' option to display parents omitted above 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. You may want to try a larger value of the --backtrack option, such as --backtrack=30, in order to see if that will solve this conflict automatically. For more information, see MASKED PACKAGES section in the emerge man page or refer to the Gentoo Handbook. The following packages are causing rebuilds: (dev-libs/boost-1.63.0:0/1.63.0::gentoo, ebuild scheduled for merge) causes rebuilds for: (media-gfx/blender-2.78a-r1:0/0::gentoo, ebuild scheduled for merge) (media-libs/openimageio-1.6.13:0/0::gentoo, ebuild scheduled for merge) Reproducible: Always Portage 2.3.3 (python 3.5.2-final-0, default/linux/amd64/13.0/desktop/plasma/systemd, gcc-5.4.0, glibc-2.23-r3, 4.9.6-gentoo x86_64) ================================================================= System uname: Linux-4.9.6-gentoo-x86_64-Intel-R-_Core-TM-_i7-3740QM_CPU_@_2.70GHz-with-gentoo-2.3 KiB Mem: 24626196 total, 17185180 free KiB Swap: 26488828 total, 26488828 free Timestamp of repository gentoo: Sun, 29 Jan 2017 23:00:01 +0000 Timestamp of repository poly-c: Sat, 28 Jan 2017 18:43:08 +0000 sh bash 4.4_p11 ld GNU ld (Gentoo 2.27 p1.0) 2.27 app-shells/bash: 4.4_p11::gentoo dev-java/java-config: 2.2.0-r3::gentoo dev-lang/perl: 5.24.1_rc4::gentoo dev-lang/python: 2.7.12::gentoo, 3.4.5::gentoo, 3.5.2::gentoo dev-util/cmake: 3.7.2::gentoo dev-util/pkgconfig: 0.29.1::gentoo sys-apps/baselayout: 2.3::gentoo sys-apps/openrc: 0.23.2::gentoo sys-apps/sandbox: 2.10-r3::gentoo sys-devel/autoconf: 2.13::gentoo, 2.69-r2::gentoo sys-devel/automake: 1.13.4-r1::gentoo, 1.14.1-r1::gentoo, 1.15-r2::gentoo sys-devel/binutils: 2.27::gentoo sys-devel/gcc: 5.4.0-r2::gentoo sys-devel/gcc-config: 1.8-r1::gentoo sys-devel/libtool: 2.4.6-r2::gentoo sys-devel/make: 4.2.1::gentoo sys-kernel/linux-headers: 4.9::gentoo (virtual/os-headers) sys-libs/glibc: 2.23-r3::gentoo Repositories:
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.
