Hi,
I'm on the way to rebuild all packages using Python to be built with
Python3.9, as well
I have created the corresponding ebuilds in a local overlay.
But many times, emerge cannot proceed because one of the dependencies
hasn't an ebuild
for Python3.9, yet.
Emerge tries to disable python3.9 for that package by an entry in
/etc/portage/package.use.
Looking at the ebuild one finds a dependency for a package which cannot
be built for Python3.9, yet.
How can I make emerge tell me this type of conflict?
I'm using
--verbose-conflict --autounmask-backtrack=y
already.
Many thanks for a hint,
Helmut
I'm on the way to rebuild all packages using Python to be built with
Python3.9, as well
I have created the corresponding ebuilds in a local overlay.
But many times, emerge cannot proceed because one of the dependencies
hasn't an ebuild
for Python3.9, yet.
Emerge tries to disable python3.9 for that package by an entry in
/etc/portage/package.use.
Looking at the ebuild one finds a dependency for a package which cannot
be built for Python3.9, yet.
How can I make emerge tell me this type of conflict?
I'm using
--verbose-conflict --autounmask-backtrack=y
already.
Many thanks for a hint,
Helmut