On 2022-01-12, Arve Barsnes <[email protected]> wrote: > On Wed, 12 Jan 2022 at 01:44, Grant Edwards <[email protected]> wrote: >> Still not sure what command one uses to determine what package is >> preventing some other package from being upgraded... > > It should all be in the emerge output, although it's quite hard to read. > > If you want help interpreting it you could post the complete conflict > output, but what you've posted in your initial message is just the bit > that says that python-exec-2.4.8 requires python-exec-conf-2.4.6. > That's not a conflict, that's just one of the packages having one > dependency. To have a conflict, a different package would need to > require a different version.
Right. And how to determine which package requires the older version is the question. Since I can't reinstall ipkg-utils, I don't have any way to recreate the conflict. > Most of the times this particular kind of conflict is with an older > package that requires older PYTHON_TARGETS than can be provided, and I > expect something that got depcleaned with ipkg-utils, or ipkg-utils > directly, required python-exec or python-exec-conf with > PYTHON_TARGETS="python3_7". Note that dev-lang/python itself is not > the source of any of these problems, I still have python 2.7 and 3.10 > installed (along with 3.9 which is the default version on this machine > now). Then it must have been ipkg-utils itself that required the older python_exec, but there was no ebuild present for it. I know that ipkg-utils was not mentioned at all in the emerge output. After unmerging ipkg-utils and python2.7 the conflict was gone. Next time I'll keep a copy of the entire emerge output. -- Grant
