161218 J. Roeleveld wrote: > 161218 Philip Webb wrote: >> I want to see which pkgs might have updates available in 'testing', >> so I enter, where 'emergeu' = 'ACCEPT_KEYWORDS="~amd64" emerge' >> USE="openssl qt5 text ruby_targets_ruby23 widgets gui network >> printsupport" emergeu -DNup world >> Portage replies (after some other irrelevant stuff) : >> !!! The ebuild selected to satisfy "app-crypt/pinentry" has unmet >> requirements. >> - app-crypt/pinentry-1.0.0::gentoo USE="-caps -emacs -gnome-keyring gtk >> ncurses qt4 qt5 -static" ABI_X86="64" >> >> The following REQUIRED_USE flag constraints are unsatisfied: >> at-most-one-of ( qt4 qt5 ) >> >> The above constraints are a subset of the following complete >> expression: >> any-of ( ncurses gtk qt4 qt5 ) gtk? ( !static ) qt4? ( !static ) qt5? ( >> !static ) static? ( ncurses ) at-most-one-of ( qt4 qt5 ) >> >> (dependency required by "app-crypt/gnupg-2.1.16::gentoo" [ebuild]) >> (dependency required by "kde-base/kdelibs-4.14.27::gentoo" [ebuild]) >> (dependency required by "kde-base/katepart-4.14.3::gentoo" [installed]) > Somewhere, qt4 is set. > This might be in a profile, as default or in /etc/portage/...
Yes, it was in make.conf (red face). I forgot that the USE list mb extended by flags set there. > Alternatively, specify -qt4 in that USE flag list. I use '-*' in make.conf , so removing qt4 will suppress it. 161218 Andrej Rode wrote: > I bet kdelibs-4/katepart-4 is pulling in/setting `qt4` USE flag. It was also being brought in by a KDE 4 pkg in World, which I've removed. Sorry for the noise. Portage needs serious improvement, but in this case it was my own oversight which was responsible. -- ========================,,============================================ SUPPORT ___________//___, Philip Webb ELECTRIC /] [] [] [] [] []| Cities Centre, University of Toronto TRANSIT `-O----------O---' purslowatchassdotutorontodotca
