1 |
"Mark Haney" <mhaney@××××××××××××.org> posted |
2 |
4A72E86B.7000205@××××××××××××.org, excerpted below, on Fri, 31 Jul 2009 |
3 |
08:49:47 -0400: |
4 |
|
5 |
> Do you really wanna see how bloody stupid this whole problem is with QT? |
6 |
> Here's what I did: |
7 |
> |
8 |
> emerge -C qt-svg qt-sql qt-dbus qt-qt3support qt-gui qt-core qt-test |
9 |
> qt-assistant |
10 |
> |
11 |
> |
12 |
> I figure this will get the system clean enough for me to actually do |
13 |
> something but stare at 20+ blocks. |
14 |
> |
15 |
> Nope. |
16 |
> |
17 |
>> octavian ~ # ACCEPT_KEYWORDS="~amd64" emerge -uav qt-svg qt-sql qt-dbus |
18 |
>> qt-gui qt-core qt-test qt-assistant |
19 |
|
20 |
snippy snippy... (clipping the below to the relevant) |
21 |
|
22 |
>> [ebuild U ] x11-libs/qt-script-4.5.2 [4.5.1] |
23 |
>> [blocks b ] <x11-libs/qt-script-4.5.2 |
24 |
>> ("<x11-libs/qt-script-4.5.2" is blocking |
25 |
|
26 |
You missed one. qt-script-4.5.1 is still installed, and it's blocking |
27 |
the others. As I said, all bits of qt4 must be the same version, so to |
28 |
get 4.5.2, you can't have 4.5.1 installed. Not a bit of it. |
29 |
|
30 |
I believe portage could resolve it if all parts were 4.5.1 and it could |
31 |
upgrade them all to 4.5.2 at once, but with mixed versions, or with one |
32 |
bit of 4.5.1 and trying to pull the others, because it tries to install |
33 |
the latest available, it doesn't work because that blocks and portage |
34 |
isn't smart enough to know how to /safely/ resolve it. (Portage defaults |
35 |
to just spitting out the blockers and letting you resolve it, if it can't |
36 |
be SURE it can do so safely.) |
37 |
|
38 |
Once you have all bits of qt4 either on the same version, or all removed, |
39 |
portage should be able to resolve things on its own. |
40 |
|
41 |
-- |
42 |
Duncan - List replies preferred. No HTML msgs. |
43 |
"Every nonfree program has a lord, a master -- |
44 |
and if you use the program, he is your master." Richard Stallman |