The other day I tried to update the system by running the usual "emerge -uvDN world", but it was impossible to run it properly as I am getting the following error since then !!! Problem resolving dependencies for app-office/libreoffice from @selected ... done! !!! The ebuild selected to satisfy "app-office/libreoffice" has unmet requirements. - app-office/libreoffice-5.1.0.3::gentoo USE="branding cups dbus gtk (-aqua) -bluetooth -coinmp -collada -debug -eds (-firebird) -gltf -gnome -gstreamer -gtk3 -java -jemalloc -kde -libressl -mysql -odk -postgres (-telepathy) -test -vlc" ABI_X86="64" LIBREOFFICE_EXTENSIONS="-nlpsolver -scripting-beanshell -scripting-javascript -wiki-publisher" PYTHON_SINGLE_TARGET="-python3_4 -python3_5" PYTHON_TARGETS="python3_4 -python3_5" The following REQUIRED_USE flag constraints are unsatisfied: exactly-one-of ( python_single_target_python3_4 python_single_target_python3_5 ) The above constraints are a subset of the following complete expression: 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 ) bluetooth? ( dbus ) collada? ( gltf ) eds? ( gnome ) gnome? ( gtk ) telepathy? ( gtk ) libreoffice_extensions_nlpsolver? ( java ) libreoffice_extensions_scripting-beanshell? ( java ) libreoffice_extensions_scripting-javascript? ( java ) libreoffice_extensions_wiki-publisher? ( java ) (dependency required by "@selected" [set]) (dependency required by "@world" [argument]) Apparently, libreoffice's ebuild is not setting PYTHON_SINGLE_TARGET correctly. I never had to set this variable for any of the packages. Could you please give a look at this issue?
The problem here is that >=libreoffice-5.1.0.3 only has python3_4 and python3_5 support while your global PYTHON_SINGLE_TARGET is at python2_7. That's what requires you to make a manual adjustment. Meanwhile, build with python2_7 appears to have been fixed so maybe it could go back into the ebuild...
Thanks for the fast reply. Well, as updating now is not so important, I guess I can wait for the ebuild to be fixed. Thanks again.
*** This bug has been marked as a duplicate of bug 472932 ***
