Alan McKinnon writes: > On 05/11/2013 15:37, Alex Schuster wrote:
[kde-misc/fsrunner pulls in QT 4.8.4] > > This does not make any sense, does it? > > Actually, it does make sense, in a weird kind of way > > kid3 and fsrunner are not part of KDE proper (i.e. they are not shipped > in the huge KDE tarballs). So they may be inconsistent with the main > release due to no QA checks beyond what the dev does. And I doubt the > gentoo KDE team checks such packages before updating ebuilds. But what exactly is it that pulls in the older Qt? > I would use this approach: > > Remove from world every KDE package that is not in kde-base (quickpkg > first to make restores easier), then update world and do a depclean. > Chances are very good it will complete cleanly. Well, I was at this point already, after excluding fsrunner and kid3. > Then emerge all those KDE packages back in using the -t option to emerge > and see what is causing issues. emerge fsrunner would happily just install fsrunner, but emerge -Dpu fsrunner again wants to downgrade Qt to 4.8.4. The same goes for kid3. No big deal, I don't really need those. > I think the odds are very good you will find an out-of-sync package that > directly DEPENDS on some old version of Qt (or something equally silly). > That package might even already be in the emerge output, but buried in > the voluminous output portage gives these days But emerge -uD @world no longer complains. Of course I have other problems now... but I will start a new thread for that. Alex