"Mark Haney" <mha...@ercbroadband.org> posted
4a72e86b.7000...@ercbroadband.org, excerpted below, on Fri, 31 Jul 2009
08:49:47 -0400:
> Do you really wanna see how bloody stupid this whole problem is with QT?
> Here's what I did:
>
> emerge -C qt-svg qt-sql qt-dbus qt-qt3support qt-gui qt-core qt-test
> qt-assistant
>
>
> I figure this will get the system clean enough for me to actually do
> something but stare at 20+ blocks.
>
> Nope.
>
>> octavian ~ # ACCEPT_KEYWORDS="~amd64" emerge -uav qt-svg qt-sql qt-dbus
>> qt-gui qt-core qt-test qt-assistant
snippy snippy... (clipping the below to the relevant)
>> [ebuild U ] x11-libs/qt-script-4.5.2 [4.5.1]
>> [blocks b ] <x11-libs/qt-script-4.5.2
>> ("<x11-libs/qt-script-4.5.2" is blocking
You missed one. qt-script-4.5.1 is still installed, and it's blocking
the others. As I said, all bits of qt4 must be the same version, so to
get 4.5.2, you can't have 4.5.1 installed. Not a bit of it.
I believe portage could resolve it if all parts were 4.5.1 and it could
upgrade them all to 4.5.2 at once, but with mixed versions, or with one
bit of 4.5.1 and trying to pull the others, because it tries to install
the latest available, it doesn't work because that blocks and portage
isn't smart enough to know how to /safely/ resolve it. (Portage defaults
to just spitting out the blockers and letting you resolve it, if it can't
be SURE it can do so safely.)
Once you have all bits of qt4 either on the same version, or all removed,
portage should be able to resolve things on its own.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
