Summary: | sys-apps/portage-3.0.18: autounmask proposes retroacting USE changes | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Nikita Zlobin <cook60020tmp> |
Component: | Core - Dependencies | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED DUPLICATE | ||
Severity: | major | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Nikita Zlobin
2021-05-03 15:52:51 UTC
I faced again certain case for abi_x86_32 use flag, at x11-libs/libva upgrade, which I tried to avoid as long as possible when faced it first.
For now I have =libva-2.7.1_rc73. It's no problem to install 2.5.0-r1 or 2.7.1. But installing recent - 2.10.0 - prints this:
==================
Calculating dependencies... done!
The following USE changes are necessary to proceed:
(see "package.use" in the portage(5) man page for more details)
# required by x11-libs/libva-intel-driver-2.4.1::gentoo
# required by x11-libs/libva-intel-driver (argument)
>=x11-libs/libva-2.10.0 -abi_x86_32
Would you like to add these changes to your config files? [Yes/No] no
* In order to avoid wasting time, backtracking has terminated early
* due to the above autounmask change(s). The --autounmask-backtrack=y
* option can be used to force further backtracking, but there is no
* guarantee that it will produce a solution.
====================
Emerge list is not even printed.
Backtracking is hopeless.
Just to clarify. libva upgrade from 2.7.1 to 2.10.0 adds new dependency for 'wayland' use - wayland-scanner. I got 'wayland' use set by default from distro, decided to not resist for now. But now, with this bug, I expect this upgrade to be a big pain, so decided to add global '-wayland' to USE (of course I could add use line for wayland-scanner manually, but would better avoid doing so, as I prefer keep distinguishable formatss for manual and dependency uses). Softly good news, it affects only USE flag proposals, keyword unmasking works ok. Duplicate for bug 784806 (there was different case, around 'abi_x86_32' use flag). Not sure about whether to change to RESOLVED, as prior bug is still UNCONFIRMED. *** This bug has been marked as a duplicate of bug 784806 *** |