Alan McKinnon wrote:
> On Tuesday 13 October 2009 14:48:35 Allan Gottlieb wrote:
>
>> I just started getting this blocker yesterday (was away for the weekend)
>>
>> [blocks B ] >x11-libs/qt-dbus-4.5.1-r9999
>> (">x11-libs/qt-dbus-4.5.1-r9999" is blocking x11-libs/qt-script-4.5.1,
>> x11-libs/qt-test-4.5.1, x11-libs/qt-gui-4.5.1,
>> x11-libs/qt-qt3support-4.5.1, x11-libs/qt-sql-4.5.1,
>> x11-libs/qt-core-4.5.1)
>>
>> (the entire output from emerge world is below
>> EMERGE_DEFAULT_OPTS="--ask --deep --tree --verbose --with-bdeps=y")
>>
>> I read the news article and was directed to
>> http://www.linuxized.com/p192, which said to add dbus and qt3support to
>> my USE flags. I already had dbus and adding qt3support did not change
>> the result. The std handbook recommendation is to remove qt-dbus, but
>> the news article suggests this one is more complicated. Should I
>> perhaps mask qu-dbus-4.5.2 and if so do I then remove the mask when the
>> rest has installed.
>>
>> This is a stable x86 box.
>>
>
> qt*-4.5.1 blocks qt*-4.5.2. It's not a simple single package that you
> upgrade,
> it's multiple packages and throughout the build you will have incompatible
> packages installed at the same time.
>
> Either:
>
> unmerge all of qt
> emerge all of qt
>
> or:
>
> upgrade to masked portage-2.2 which can deal with such things easily.
>
> Note that you will likely need to rebuild kdelibs and other stuff after
> building qt. There's an elog about it.
>
>
It may be more than just likely. I had to rebuild about all of KDE 3
and a huge part of KDE 4. Since it was so many packages, it could
easily have been them all. Funny thing is, I already had my USE flags
set correctly.
Dale
:-) :-)
