Neil Bothwick wrote: > On Thu, 04 Jun 2020 21:24:39 +0000, Caveman Al Toraboran wrote: > >> if i exec: "emerge -avDuNt --quiet-build=y @world": >> >> > These are the packages that would be merged, in reverse order: >> > >> > Calculating dependencies... done! >> > >> > The following USE changes are necessary to proceed: >> > (see "package.use" in the portage(5) man page for more details) >> > # >> > >=dev-python/docutils-0.16 -python_targets_python2_7 >> > >> > Would you like to add these changes to your config files? >> > [Yes/No] >> >> so >=dev-python/docutils-0.16 doesn't want >> python_targets_python2_7. let's remove it then by >> adding: >> >> >=dev-python/docutils-0.16 -python_targets_python2_7 >> >> into: /etc/portage/package.use/stuff >> >> but then i get this: >> >> > The following USE changes are necessary to proceed: >> > (see "package.use" in the portage(5) man page for more details) >> > # required by dev-python/m2r-0.2.1::gentoo[-test] >> > # required by dev-python/automat-20.2.0::gentoo >> > # required by dev-python/twisted-20.3.0::gentoo >> > # required by www-servers/tornado-6.0.4::gentoo >> > # required by dev-python/ipykernel-5.1.4::gentoo[-test] >> > # required by dev-python/ipyparallel-6.2.3::gentoo >> > # required by dev-python/ipython-7.5.0::gentoo[smp] >> > # required by @selected >> > # required by @world (argument) >> > >=dev-python/docutils-0.16 python_targets_python2_7 >> > >> > Would you like to add these changes to your config files? >> > [Yes/No] >> >> which i guess means that docutils wants py2.7. >> >> >> any idea how to handle this situation? > Allow portage to add the changes to your config, then run etc-update or > equivalent. When portage adds package.use changes, it also adds comments > showing what requires those changes. With that information, you should be > able to see which package is causing this. > >
One of us is reading that wrong. Given my eyes, maybe it is me. My new glasses should be in within the next week or so. In the first instance, it wants py2.7 disabled. So he adds it to the config file to disable it. When he runs the command again, it wants to enable py2.7 for the same package and version. If I'm reading that right, even if he lets emerge add the change, it will lead to two problems. One, there will be one line enabling py2.7 and another line disabling it. If I recall correctly, emerge will take the last one. Two, he will be back to the first problem, it wanting py2.7 disabled. In other words, back where he started. Am I reading that wrong or something?? Dale :-) :-)
