All of lore.kernel.org
 help / color / mirror / Atom feed
* [Buildroot] Diagnosing conflicts due to new Python version
@ 2022-01-11 16:11 Grant Edwards
  2022-01-11 20:10 ` Thomas Petazzoni
  0 siblings, 1 reply; 4+ messages in thread
From: Grant Edwards @ 2022-01-11 16:11 UTC (permalink / raw)
  To: buildroot

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2022-01-11 23:05 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-01-11 16:11 [Buildroot] Diagnosing conflicts due to new Python version Grant Edwards
2022-01-11 20:10 ` Thomas Petazzoni
2022-01-11 22:57   ` Grant Edwards
2022-01-11 22:57     ` Grant Edwards

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.