I forgot to mention:
After rebuilding all of qt with this amount of changes, be prepared to rebuild
all of KDE-4 as well. Not doing this often results in weird behavviour that is
impossible to track down, hence the large elog warning in all the qt-*
ebuilds.
On Sunday 25 October 2009 15:36:05 Alan McKinnon wrote:
> On Sunday 25 October 2009 15:26:19 Alan E. Davis wrote:
> > To follow up, after removing "qt" (by mistake), and all the qt-* packages
> > I could find, this is what I found when running "emerge -uDav world""
> >
> > x11-libs/qt-gui:4
> >
> > ('ebuild', '/', 'x11-libs/qt-gui-4.5.3-r1', 'merge') conflicts with
> > ~x11-libs/qt-gui-4.5.2[-debug] required by ('ebuild', '/',
> > 'x11-libs/qt-webkit-4.5.2-r1', 'merge')
>
> Something wants qt-webkit-4.5.2-r1
>
> > x11-libs/qt-sql:4
> >
> > ('ebuild', '/', 'x11-libs/qt-sql-4.5.3', 'merge') conflicts with
> >
> > >=x11-libs/qt-sql-4.5.0:4[mysql] required by ('installed', '/',
> >
> > 'app-office/akonadi-server-1.2.1', 'nomerge')
>
> akonadi-server requires qt-sql with USE=mysql
>
> > x11-libs/qt-core:4
> >
> > ('ebuild', '/', 'x11-libs/qt-core-4.5.3-r1', 'merge') conflicts with
> > ~x11-libs/qt-core-4.5.2[qt3support,-debug] required by ('ebuild',
> > '/', 'x11-libs/qt-sql-4.5.2', 'merge')
> >
> > x11-libs/qt-dbus:4
> >
> > ('ebuild', '/', 'x11-libs/qt-dbus-4.5.3', 'merge') conflicts with
> > ~x11-libs/qt-dbus-4.5.2[-debug] required by ('ebuild', '/',
> > 'x11-libs/qt-gui-4.5.2-r2', 'merge')
> >
> > media-libs/x264:0
> >
> > ('ebuild', '/', 'media-libs/x264-0.0.20090923', 'merge') conflicts with
> > <media-libs/x264-0.0.20090908 required by ('installed', '/',
> > 'media-video/avidemux-2.5.1-r2', 'nomerge')
>
> We need to establish why qt-4.5.2 packages are being pulled in instead of
> 4.5.3
>
> Please run emerge -avuNDt world and post that (snipping irrelevant bits as
> appropriate).
>
> You might have left a qt-*-4.5.2 package installed by mistake, or some
> other package is hard-coded to require a qt-4.5.2 version.
>
> The solution for the first is to uninstall the package you missed, the
> solution for the second is to unmerge the offending package and remerge it
> (but recent portage should be taking care of that all by itself). Either
> way emerge -t will provide clues.
>
--
alan dot mckinnon at gmail dot com
