On Sun, Jul 5, 2015 at 2:25 PM, Sebastian Pipping <sp...@gentoo.org> wrote: > > > I really wonder if there is any update path from having > > dev-qt/qtcore-4.8.6-r2 > dev-qt/qtgui-4.8.6-r4 > > installed before to > > dev-qt/qtcore-4.8.7 > dev-qt/qtgui-4.8.7 > > > > Usually this kind of conflict happens when for SOME reason, at least one part of the dev-qt/*:4 collection is not being pulled into the depgraph, like if there's one qt* package which is now orphaned/depcleanable. If even one piece is not pulled into the dep list, it will try to hold all the rest of the pieces back at 4.8.6.
Something like this may help, to just force all installed qt4 pieces to upgrade, regardless of whether they are deps of anything: emerge -1av $(qlist -ICS dev-qt/ | grep 4$) Another possibility for a conflict is if you have some package.use entries for dev-qt/ that are too version specific, where the upgraded 4.8.7 version of some component would not meet the USE requirements of some reverse dep. Then it'd lock that one component at 4.8.6 and again it's game-over for the upgrade. Hope this helps, Ben Kohler (iamben @ Freenode)
