QT's current stable version is 3.3.4-r2. emerge -upD world makes sure we have that version. uim-qt current stable version (0.1.7) has: DEPEND=">=app-i18n/uim-0.4.3 || ( =x11-libs/qt-3.3.3 =x11-libs/qt-3.3.2 )" So that: # emerge -p =app-i18n/uim-qt-0.1.7 Produces: [ebuild UD] x11-libs/qt-3.3.3 [3.3.4-r2] [ebuild R ] app-i18n/uim-qt-0.1.7 It seems there's a dependency checking problem in update -uD world, as it should not update to 3.3.4-r1. If someone has uim-qt installed, he ends up in infinite remerging of qt when he updates world, switching from 3.3.3 to 3.3.4-r1 and back again... I don't know if it's fixed in ~x86, but I'm talking about a dependency problem between 2 stable (~x86) packages. That's why I haven't assigned this bug to KDE, but to baselayout instead. Reproducible: Always Steps to Reproduce: 1. emerge uim-qt 2. emerge -upD world 3. emerge -upD world 3. emerge -upD world 3. emerge -upD world
Well, of course I intended to write "I don't know if it's fixed in ~x86, but I'm talking about a dependency problem between 2 stable (x86) packages.", not "~x86" :)
It's intended. The latest uim-qt is included to uim package (>=0.4.6_alpha1), and uim-qt does depend on these versions of qt. If you use uim-qt with qt-3.3.4-r2, please consider using uim-0.4.6 with USE="qt". (It conflicts with uim-qt, so you need to unmerge uim-qt first.)
uim-0.4.6 is not part of the stable tree, so it's still a dependency bug in the stable tree. On x86, latest uim stable version is uim-0.4.5.1. So this won't likely be fixed until uim-0.4.6 gets unmasked.
k, I unmasked uim-qt-0.2.0 for the time being, so if you do not want to use unstable version of uim you can use that instead.
