On Saturday, 23 June 2018 12:35:32 BST you wrote: > On Saturday, 23 June 2018 11:09:10 BST Alec Ten Harmsel wrote: > > On Sat, Jun 23, 2018 at 10:38:35AM +0100, Mick wrote: > > > On Saturday, 23 June 2018 10:30:09 BST Neil Bothwick wrote: > > > > On 23 June 2018 10:14:31 BST, Mick <michaelkintz...@gmail.com> wrote: > > > > >I came up to this today following a portage sync: > > > > > > > > > ># emerge -uaNDv world > > > > > > > > > > > > > > >These are the packages that would be merged, in order: > > > > > > > > > >Calculating dependencies / > > > > > > > > > >!!! Problem resolving dependencies for sys-devel/gdb from @selected > > > > >.. done! > > > > > > > > > > > > > > >!!! The ebuild selected to satisfy "sys-devel/gdb" has unmet > > > > >requirements. > > > > >- sys-devel/gdb-7.12.1::gentoo USE="client nls python server xml > > > > >-lzma > > > > >- > > > > >multitarget -test -vanilla" ABI_X86="(64)" > > > > >PYTHON_SINGLE_TARGET="-python2_7 - > > > > >python3_4 -python3_5" PYTHON_TARGETS="python2_7 -python3_4 > > > > >-python3_5" > > > > > > > > > > The following REQUIRED_USE flag constraints are unsatisfied: > > > > > python? ( exactly-one-of ( python_single_target_python2_7 > > > > > > > > > >python_single_target_python3_4 python_single_target_python3_5 ) ) > > > > > > > > > > ....... > > > > > > > > Start with "grep - ir python /etc/portage". That found the source of > > > > the > > > > problem on one of my systems, I was setting PYTHON_SINGLE_TARGET for > > > > one > > > > package. > > > > > > Thanks Neil, I already had a look just in case I had set something up > > > and > > > forgot about it. This is all it showed: > > > > > > # grep -ir python /etc/portage > > > /etc/portage/package.use/package.use:=media-libs/lcms-1.19-r1 python > > > > How about `emerge --info | grep PYTHON_SINGLE_TARGET'? The problem looks > > > > to be: > > > PYTHON_SINGLE_TARGET="-python2_7 -python3_4 -python3_5" > > > > At least one PYTHON_SINGLE_TARGET needs to be set. I'd guess that > > PYTHON_SINGLE_TARGET got updated to 3.6, leaving GDB in its dust. > > > > Alec > > Thanks Alec, yes python-3.6 was moved to the stable tree. This is what I > have: > > PYTHON_SINGLE_TARGET="python3_6" PYTHON_TARGETS="python2_7 python3_6"
Errm ... no I don't! This morning after an update the targets have moved back to ... python3_5, despite having set up with eselect python3_6. Is the default python target determined by the profile and does this override choices through eselect? Should 'eselect python update' set 3.6 as the default when emerge seems to be determined to use 3.5? # eselect python list Available Python interpreters, in order of preference: [1] python3.6 [2] python3.5 [3] python3.4 (uninstalled) [4] python2.7 (fallback) While from emerge --info I get: PYTHON_SINGLE_TARGET="python3_5" PYTHON_TARGETS="python2_7 python3_5" I don't fancy rebuilding libreoffice + 67 more packages on 3 PCs just for grins. -- Regards, Mick
signature.asc
Description: This is a digitally signed message part.
