I assume those emerge commands weren't done on one machine but come from those two different machines. This change in USE Flags can't come from that line in package.accept_keywords. This is a change in PYTHON_TARGETS in make.conf, package.use or package.env. Carefully go through those config files/directories, I am sure you will find the offending line.
Regards Franz Am Fr., 3. Jan. 2020 um 11:44 Uhr schrieb Mickaël Bucas <mbu...@gmail.com>: > Hello > > For some time I've been wondering why I had a difference on > dev-python/olefile-0.46 between 2 machines : one was installed with > python_targets_python3_7, the other wasn't. > And I finally pinpointed it to package.accept_keywords containing > "dev-python/olefile ~amd64" on one of the machines only > > At the time of writing, dev-python/olefile-0.46 is the stable version, and > KEYWORDS contains "amd64" (no tilde) among others. > > When package.accept_keywords doesn't contain "dev-python/olefile ~amd64", > I get : > emerge -pv1 --verbose-conflicts olefile > These are the packages that would be merged, in order: > Calculating dependencies... done! > [ebuild R ] dev-python/olefile-0.46::gentoo USE="-doc" > PYTHON_TARGETS="python2_7 python3_6 (-pypy3) (-python3_7) (-python3_8)" 0 > KiB > Total: 1 package (1 reinstall), Size of downloads: 0 KiB > > => Python 3.7 is disabled > > When package.accept_keywords contains "dev-python/olefile ~amd64", I get : > emerge -pv1 olefile > These are the packages that would be merged, in order: > Calculating dependencies... done! > [ebuild R ] dev-python/olefile-0.46::gentoo USE="-doc" > PYTHON_TARGETS="python2_7 python3_6 python3_7* -pypy3 -python3_8" 0 KiB > Total: 1 package (1 reinstall), Size of downloads: 0 KiB > > => Python 3.7 is enabled > > It seems really really strange to me for the same version of a stable > package to be "influenced" by keywording. > Is it a bug or a feature ? > Did I do something wrong ? > > Thanks > Best regards > Mickaël Bucas >
