On Saturday, 19 December 2020 11:37:31 GMT Neil Bothwick wrote:
> On Sat, 19 Dec 2020 12:33:10 +0100, n952162 wrote:
> > I do an emerge @world, it tells me I have slot collisions and stops. 
> > Following Neil B.'s advice, I try to go through the collisions and see
> > what the differences are.  jinja was a nice example, because there was a
> > collision of the same package with itself!  The only difference was the
> > PYTHON_TARGET.  I hoped someone could explain how I could force
> > equivalency in that simple case.
> 
> You need to follow the trail back further. If portage wants to install
> two variants of jnja, look to see what is requiring them, that is most
> likely where the real solution lies.

'emerge --tree -uNDpv @system' or '@world', will also show the respective 
dependency tree of any packages portage is trying to update.  If an older 
version of jinja is being dragged in by a non-system package, you can 
temporarily uninstall that package and make a note of it to re-install it 
later if you need/want to.