Created attachment 598886 [details] emerge --info Hi, today build sys-libs/talloc-2.1.14 breaks with unmet requirements: !!! The ebuild selected to satisfy "sys-libs/talloc" has unmet requirements. - sys-libs/talloc-2.1.14::gentoo USE="-compat -python" PYTHON_SINGLE_TARGET="-python2_7" PYTHON_TARGETS="python2_7" The following REQUIRED_USE flag constraints are unsatisfied: python_single_target_python2_7 The above constraints are a subset of the following complete expression: exactly-one-of ( python_single_target_python2_7 ) python_single_target_python2_7? ( python_targets_python2_7 ) From my system: eselect python show python3.7 eselect python list Available Python interpreters, in order of preference: [1] python3.7 [2] python3.6 [3] python2.7 (fallback) The System works with musl overlay, but I think it has nothing to do with it. Take a view to emerge --info in attachment, for that.
@Lloyd you can get going if you put into /etc/portage/package.use: --- sys-libs/talloc python python_single_target_python2_7 I have experienced this emerge error with several ebuilds since a day: --- exactly-one-of ( python_single_target_python2_7 ) python_single_target_python2_7? ( python_targets_python2_7 ) --- Which is weird but everytime solves with this additioned flag: python_single_target_python2_7 My guess: It is worked on to get rid of python2 in the portage tree, see: https://bugs.gentoo.org/694800
Python 2.7 is reaching EOL and the python2_7 target has been recently removed from the default targets. You can add it to your make.conf globally or to separate packages.
@Ulenrich adding the python2_7 line into /etc/portage/package.use do not work for me. But since version: sys-libs/talloc-2.1.16 talloc compiles with python3. So I add >=sys-libs/talloc-2.2.0 ~amd64 into /etc/portage/packages.accept_keywords and now it compiles, without going back to version python2_7. Keep in mind that I'm now on the testing branch(!), but it works. I need talloc for the freeradius server. As far as I can see, it works without problems.
(In reply to Tomáš Mózes from comment #2) > the python2_7 target has been recently removed from the default targets. No such thing has happened yet. The actual cause of "problem" is change in python-single-r1.eclass: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=4da21ec689a66fe87ef67476dc6245808f6dde88 These users, who customize configuration of USE flags, now need to set PYTHON_SINGLE_TARGET (for relevant packages) in addition to PYTHON_TARGETS.
(In reply to Arfrever Frehtes Taifersar Arahesis from comment #4) > (In reply to Tomáš Mózes from comment #2) > > the python2_7 target has been recently removed from the default targets. > > No such thing has happened yet. Sorry, must have misread some commit :-/
