On Sunday, August 30, 2015 9:41:04 AM the...@sys-concept.com wrote: > All it was needed was in portage.use > > # required by app-portage/gentoolkit-0.3.0.9-r2 > # required by app-portage/gentoolkit (argument) > =sys-apps/portage-2.2.20.1 python_targets_python3_3 > > Thelma
Now you'll probably run into similar errors when you do run an update with the --newuse (ideally you should use it for every update -- it's the same as the N flag on my original reply) or when one of those packages is updated. > On 08/30/2015 08:43 AM, Mick wrote: > > On Saturday 29 Aug 2015 20:36:04 neu pat wrote: > >> I emerge python3.4 set as active: > >> eselect python list > >> Available Python interpreters: > >> [1] python2.7 > >> [2] python3.3 > >> [3] python3.4 * > >> but it still complain about Multiple package instances > >> > >> [ebuild U ] sys-apps/portage-2.2.20.1 [2.2.14] > >> PYTHON_TARGETS="python3_4* -python3_3*" > >> > >> !!! Multiple package instances within a single package slot have been > >> pulled !!! into the dependency graph, resulting in a slot conflict: > >> > >> sys-apps/portage:0 > >> > >> (sys-apps/portage-2.2.20.1:0/0::gentoo, ebuild scheduled for merge) > >> pulled in by > >> sys-apps/portage (Argument) > >> > >> (sys-apps/portage-2.2.14:0/0::gentoo, installed) pulled in by > >> > >> sys- apps/portage[python_targets_python2_7(-)?,python_targets_python3_3(-)?, > >> -python_single_target_python2_7(-),-python_single_target_python3_3(-)] > >> required by (app-admin/webapp-config-1.52-r1:0/0::gentoo, installed) > >> > >> > >> > >> sys- apps/portage[python_targets_python2_7(-)?,python_targets_python3_3(-)?, > >> python_targets_python3_4(-)?,python_targets_pypy(-)?,- python_single_target_ > >> python2_7(-),-python_single_target_python3_3(-),- python_single_target_pytho > >> n3_4(-),-python_single_target_pypy(-)] required by > >> (app-portage/gentoolkit-0.3.0.9-r2:0/0::gentoo, installed) > >> > >> How to fix it? > >> > >> #joseph > > > > Try the --newuse flag, after you remove any 'python_targets_python3_3' entries > > you have inadvertently left in your /etc/portage/package.use > > > -- Fernando Rodriguez