[Buildroot] Diagnosing conflicts due to new Python version

From: Grant Edwards <grant.b.edwards@gmail.com>
To: buildroot@uclibc.org
Subject: [Buildroot] Diagnosing conflicts due to new Python version
Date: Tue, 11 Jan 2022 16:11:41 -0000 (UTC)	[thread overview]
Message-ID: <srka7t$pu1$1@ciao.gmane.io> (raw)

It seems that every time a new Python version is unmasks, it breaks
things.

This time it's a python-exec version conflict that prevents emerge
-u. FAICT, Python 3.10 requires python-exec 2.4.8, and some other
package requires 2.4.6.

I've fixed things temporarily with:

package.use:

   */* PYTHON_TARGETS: -python3_10
   */* PYTHON_SINGLE_TARGET -python3_10

package.mask:

   =dev-lang/python-3.10

No, at least I can continue to update the machine.

When I eventually get the spare time to try to get Python 3.10
working, how does one figure out which package is causing the problem
by requring the older version of python-exec?

I've tried adding a 't' to the emerge flags, but that doesn't seem to
show anything useful.

Is there any documentation on how to determine the cause of a package
version conflict?

--
Grant

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot