| 1 |
On Tuesday 13 October 2009 14:48:35 Allan Gottlieb wrote: |
| 2 |
> I just started getting this blocker yesterday (was away for the weekend) |
| 3 |
> |
| 4 |
> [blocks B ] >x11-libs/qt-dbus-4.5.1-r9999 |
| 5 |
> (">x11-libs/qt-dbus-4.5.1-r9999" is blocking x11-libs/qt-script-4.5.1, |
| 6 |
> x11-libs/qt-test-4.5.1, x11-libs/qt-gui-4.5.1, |
| 7 |
> x11-libs/qt-qt3support-4.5.1, x11-libs/qt-sql-4.5.1, |
| 8 |
> x11-libs/qt-core-4.5.1) |
| 9 |
> |
| 10 |
> (the entire output from emerge world is below |
| 11 |
> EMERGE_DEFAULT_OPTS="--ask --deep --tree --verbose --with-bdeps=y") |
| 12 |
> |
| 13 |
> I read the news article and was directed to |
| 14 |
> http://www.linuxized.com/p192, which said to add dbus and qt3support to |
| 15 |
> my USE flags. I already had dbus and adding qt3support did not change |
| 16 |
> the result. The std handbook recommendation is to remove qt-dbus, but |
| 17 |
> the news article suggests this one is more complicated. Should I |
| 18 |
> perhaps mask qu-dbus-4.5.2 and if so do I then remove the mask when the |
| 19 |
> rest has installed. |
| 20 |
> |
| 21 |
> This is a stable x86 box. |
| 22 |
|
| 23 |
qt*-4.5.1 blocks qt*-4.5.2. It's not a simple single package that you upgrade, |
| 24 |
it's multiple packages and throughout the build you will have incompatible |
| 25 |
packages installed at the same time. |
| 26 |
|
| 27 |
Either: |
| 28 |
|
| 29 |
unmerge all of qt |
| 30 |
emerge all of qt |
| 31 |
|
| 32 |
or: |
| 33 |
|
| 34 |
upgrade to masked portage-2.2 which can deal with such things easily. |
| 35 |
|
| 36 |
Note that you will likely need to rebuild kdelibs and other stuff after |
| 37 |
building qt. There's an elog about it. |
| 38 |
|
| 39 |
-- |
| 40 |
alan dot mckinnon at gmail dot com |
Archives