1 |
On 13.10.2009 14:48, 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 (">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) |
5 |
> |
6 |
> (the entire output from emerge world is below |
7 |
> EMERGE_DEFAULT_OPTS="--ask --deep --tree --verbose --with-bdeps=y") |
8 |
> |
9 |
> I read the news article and was directed to |
10 |
> http://www.linuxized.com/p192, which said to add dbus and qt3support to |
11 |
> my USE flags. I already had dbus and adding qt3support did not change |
12 |
> the result. The std handbook recommendation is to remove qt-dbus, but |
13 |
> the news article suggests this one is more complicated. Should I |
14 |
> perhaps mask qu-dbus-4.5.2 and if so do I then remove the mask when the |
15 |
> rest has installed. |
16 |
|
17 |
I just solved a similar block, also involving PyQt4, by adding |
18 |
dev-python/PyQt4 -dbus |
19 |
to my /etc/portage/package.use. (I also added -qt3support to USE in |
20 |
/etc/make.conf to get rid of the mess where some packages have that |
21 |
defined, and some not.) |
22 |
|
23 |
But I am already at qt-*-4.5.2 the upgrade to which is a longer |
24 |
procedure as Alan points out. |
25 |
|
26 |
Cheers, |
27 |
Peter. |
28 |
|
29 |
P.S.: Sorry, if this appears twice. I sent a similar reply half an hour |
30 |
ago and it hasn't shown up yet... |