| 1 |
Hi, |
| 2 |
|
| 3 |
I'm on the way to rebuild all packages using Python to be built with |
| 4 |
Python3.9, as well |
| 5 |
I have created the corresponding ebuilds in a local overlay. |
| 6 |
But many times, emerge cannot proceed because one of the dependencies |
| 7 |
hasn't an ebuild |
| 8 |
for Python3.9, yet. |
| 9 |
Emerge tries to disable python3.9 for that package by an entry in |
| 10 |
/etc/portage/package.use. |
| 11 |
|
| 12 |
Looking at the ebuild one finds a dependency for a package which cannot |
| 13 |
be built for Python3.9, yet. |
| 14 |
How can I make emerge tell me this type of conflict? |
| 15 |
I'm using |
| 16 |
--verbose-conflict --autounmask-backtrack=y |
| 17 |
already. |
| 18 |
|
| 19 |
Many thanks for a hint, |
| 20 |
Helmut |
Archives