There is no SLOT conflict to warn about when you call --buildpkgonly with two atoms that would *only* conflict if --buildpkgonly was *not* issued. # emerge -v1a =dev-db/mysql-{5.5.43,5.6.24} --buildpkgonly --nodeps These are the packages that would be built, in order: [ebuild N ~] dev-db/mysql-5.5.43 USE="community embedded extraengine perl ssl {test} -bindist (-cluster) -debug -jemalloc -latin1 -max-idx-128 -minimal -profiling (-selinux) -static -static-libs (-systemtap) (-tcmalloc)" 22,734 KiB [ebuild N ~] dev-db/mysql-5.6.24 USE="community embedded extraengine perl ssl {test} (-cluster) -debug -jemalloc -latin1 -minimal -profiling (-selinux) -static -static-libs (-systemtap) (-tcmalloc)" 33,860 KiB Total: 2 packages (2 new), Size of downloads: 56,594 KiB !!! Multiple package instances within a single package slot have been pulled !!! into the dependency graph, resulting in a slot conflict: dev-db/mysql:0 (dev-db/mysql-5.5.43:0/0::gentoo, ebuild scheduled for merge) pulled in by =dev-db/mysql-5.5.43 (Argument) (dev-db/mysql-5.6.24:0/0::gentoo, ebuild scheduled for merge) pulled in by =dev-db/mysql-5.6.24 (Argument) 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. Would you like to merge these packages? [Yes/No]
