Created attachment 662020 [details] output from emerge -pvD qt-creator After unmasking dev-qt/qt-creator in /etc/portage/package.accept_keywords, it asks for all already installed stable dev-qt/qt* to be rebuilt as non-stable "~amd64".
I don't use this but from my understanding this is because of the qt-creator's default USE=qmldesigner, if want to use with 5.14.x current stable QT you need to turn it off.
It's a bit awkward that dev-qt/qtquicktimeline has no stable version, indeed. The emerge output isn't helping to resolve the conflict as it does not pinpoint that exact package's role in the conflicting versions. It's well hidden in that output: (dev-qt/qtdeclarative-5.15.1:5/5.15::gentoo, ebuild scheduled for merge) USE="widgets -debug -gles2-only -jit -localstorage -test -vulkan" pulled in by ~dev-qt/qtdeclarative-5.15.1 required by (dev-qt/qtquicktimeline-5.15.1:5/5.15::gentoo, ebuild scheduled for merge) USE="-debug -test" ^ ^^^^^^
But qt-creater isn't stable as well, so this is perfectly normal.
Even if normal, maybe the flag could be masked in stable for now to get less confused users? The problem seem more like to be that portage's output is too hard to decrypt for the average user to know what to do.
(In reply to Ionen Wolkens from comment #4) > Even if normal, maybe the flag could be masked in stable for now to get less > confused users? Err wait, that wouldn't work. I guess it would need to be made non-default if that can be considered.
*** Bug 746941 has been marked as a duplicate of this bug. ***
It's fine for an unstable package to have a default enabled USE flag for an unstable dependency. There is not really anything to do here, users mixing stable and unstable need to up their portage game.
With 5.15.1 stabilised, we can consider this obsolete/invalid.
