This bug applies at least to all of the versions of sci-geosciences/gpsd-3+. Did not test it for the 2+ versions. When trying to emerge sci-geosciences/gpsd, emerge fails the dependecy calculation with the message there are unmet requirements. The unmet requirement is "python" and is pulled in by the useflag "X". The current workaround for me is to disable the X useflag for this package in /etc/portage/packag.use. The X useflag is not a requirement by any package pulling gpsd in. It is globally set by profile. Reproducible: Always Steps to Reproduce: 1. Enable useflag "X" on global scale 2. emerge sci-geosciences/gpsd 3. This will try to emerge the latest stable version, which is sci-geosciences/gpsd-3.7 on amd64. Actual Results: !!! The ebuild selected to satisfy "sci-geosciences/gpsd" has unmet requirements. - sci-geosciences/gpsd-3.7::gentoo USE="X bluetooth (consolekit) cxx dbus ipv6 (multilib) ncurses (policykit) qt4 shm sockets udev usb -debug -ntp -python -test" ABI_X86="64" GPSD_PROTOCOLS="aivdm ashtech earthmate evermore fv18 garmin garmintxt gpsclock itrax mtk3301 navcom nmea ntrip oceanserver oldstyle oncore rtcm104v2 rtcm104v3 sirf superstar2 timing tnt tripmate tsip ubx -clientdebug" The following REQUIRED_USE flag constraints are unsatisfied: X? ( python ) Expected Results: Either try to pull in python or find python already installed on this system. This happened on both my x86 and amd64 systems.
Created attachment 347574 [details] emerge --info output
The following REQUIRED_USE flag constraints are unsatisfied: X? ( python ) This means that for USE=X to be effective, you need USE=python, so effectively you need to have: USE="X python".
In that case, should autounmask not handle this? The problem for me arrised during a world update and it did merge fine before. (2.95). Maybe a news item about changed merge behaviour?
