On 03/17/2017 02:49 AM, Dale wrote: > Ralf wrote: >> On 03/17/2017 02:28 AM, Neil Bothwick wrote: >>> Read the message again, it needs one of python3_4 or python3_5 in >>> single target, you have neither. >> ... And read mine :-) >> I know. >> And I know how I could fix that for single packages, but then the >> next package complains about the very same issues. So somehow >> 'default' settings seem not to apply any more. >>> >>> Do you have any PYTHON entries in make.conf? >> No, not yet. My profile: >> default/linux/amd64/13.0/desktop/gnome/systemd >> >> And I didn't do anything suspicious in the meanwhile, so for me it >> seems they changed something in the profile. >> >> Thanks >> Ralf >>> >>> On 17 March 2017 01:09:29 GMT+00:00, Ralf >>> <ralf+gen...@ramses-pyramidenbau.de> wrote: >>> >>> Hi, >>> >>> so I just emerged some unrelated packages, and then the following >>> happened when trying to update my system: >>> >>> !!! The ebuild selected to satisfy ">=app-editors/gedit-3.22.0" has >>> unmet requirements. >>> - app-editors/gedit-3.22.0::gentoo USE="introspection python spell -test >>> -vala" ABI_X86="64" PYTHON_SINGLE_TARGET="-python3_4 -python3_5" >>> PYTHON_TARGETS="python3_4 -python3_5" >>> >>> The following REQUIRED_USE flag constraints are unsatisfied: >>> python? ( exactly-one-of ( python_single_target_python3_4 >>> python_single_target_python3_5 ) ) >>> >>> The above constraints are a subset of the following complete >>> expression: >>> python? ( introspection exactly-one-of ( >>> python_single_target_python3_4 python_single_target_python3_5 ) >>> python_single_target_python3_4? ( python_targets_python3_4 ) >>> python_single_target_python3_5? ( python_targets_python3_5 ) ) >>> >>> >>> So somehow PYTHON_TARGET and PYTHON_SINGLETARGET got screwed on my >>> system. I know how I could fix this for gedit only, but then other >>> packages begin complaining about the same issue as well. >>> >>> Anything helps! >>> >>> Cheers >>> Ralf >>> >>> >>> -- >>> Sent from my Android device with K-9 Mail. Please excuse my brevity. >> >> > > > I would check emerge --info just to confirm it. If that shows a wrong > setting, then you know it is a setting, somewhere. If it doesn't, > whole new can of worms. > > Dale > > :-) :-)
It tells me: PYTHON_SINGLE_TARGET="python2_7" PYTHON_TARGETS="python2_7 python3_4" So that's what I guess, that it's a setting somewhere... But where? Everything used to work before. Ralf
