On 12/4/20 10:49 PM, Arve Barsnes wrote:
On Fri, 4 Dec 2020 at 21:24, n952162 <n952...@web.de> wrote:
I guess you mean, remove them all and then let emerge tell me which ones
I need. I'll try that. But isn't '=' more restrictive than '>=',
promising me troubles earlier?
The earlier you encounter any conflicts, they're generally easier to solve.
No, that didn't work. After about 4 iterations of supplying newly
required USE flags, I ended up with this
(this after commenting out all the python dependencies in
/etc/portage/package.use/* and adding back in what emerge wanted):
Hard to say what the problem is when I don't know what you've added
back to USE, but I wonder what state your portage tree is in, because
it seems like many of the packages creating your conflicts, like the
two below, dev-python/ipaddress and dev-python/futures, don't exist at
all in my tree. They were removed several weeks ago. When did you last
sync? If recently, when did you last --depclean?
dev-python/setuptools[python_targets_python2_7(-),-python_single_target_python2_7(-)]
required by (dev-python/ipaddress-1.0.23:0/0::gentoo, installed) USE=""
ABI_X86="(64)" PYTHON_TARGETS="python2_7"
dev-python/setuptools[python_targets_python2_7(-),-python_single_target_python2_7(-)]
required by (dev-python/futures-3.1.1:0/0::gentoo, installed) USE="-doc"
ABI_X86="(64)" PYTHON_TARGETS="python2_7"
Regards,
Arve
Okay, I've never done a depclean. Is that something I need to do? I
mean, I'm always worried it'd remove something that I need, but given
all the problems I have, I guess that'd be the lesser of evils...
I'll give that a go and go to bed.
