>>108780355
Ok yeah I don't get it, can any more experienced gentoofags tell me what's going on here:
[blocks B ] <dev-qt/qtshadertools-6.10.3:6 ("<dev-qt/qtshadertools-6.10.3:6" is soft blocking dev-qt/qtbase-6.10.3-r1)
[blocks B ] <dev-qt/qtsvg-6.10.3:6 ("<dev-qt/qtsvg-6.10.3:6" is soft blocking dev-qt/qtbase-6.10.3-r1)
[blocks B ] <dev-qt/qttools-6.10.3:6 ("<dev-qt/qttools-6.10.3:6" is soft blocking dev-qt/qtbase-6.10.3-r1)
[blocks B ] <dev-qt/qtdeclarative-6.10.3:6 ("<dev-qt/qtdeclarative-6.10.3:6" is soft blocking dev-qt/qtbase-6.10.3-r1)
Total: 107 packages (91 upgrades, 1 new, 1 in new slot, 14 reinstalls), Size of downloads: 4019534 KiB
Conflict: 11 blocks (4 unsatisfied)
I don't have anything weird on my system, at least that I remember, so I have no idea how this could've come about. Did they just break qt6 upgrades in the repos, should I wait for some extra packages to be updated? Should I mask or uninstall some packages? How does this even happen and how do I resolve this
I tried to see if an LLM would have any useful input, codex is telling me to run
emerge -avNDu @world --ignore-built-slot-operator-deps=y
emerge -av --changed-slot @world
emerge -av @preserved-rebuild
emerge -avNDu @world
Which seems very sketchy. Checking to see with -p does show the --ignore... option resolving the blocks, but using a debug option to ignore slot deps doesn't sound right.