app-portage/kelogviewer depends on kde-base/pykde, which depends on =dev-python/PyQt-3.14.1-r2, which is broken on x86 (see bug #164562). As Norberto Bensa indicated in that bug, kelogviewer successfully compiles and runs with dev-python/pykde (which depends on >=dev-python/PyQt-3.16.0) instead of kde-base/pykde, so I propose a patch to apply this change. AFAIK this is the only way to successfully emerge kelogviewer right now. The attached patch also updates the post-install message. Reproducible: Always Steps to Reproduce:
Created attachment 109842 [details, diff] patch
Can do that as soon as amd64 has keyworded dev-python/pykde
On x86 here everything works fine, all packages emerge without problems. Could you please try PyQt and pykde with qt 4.2.2? And try different USE flag combinations (especially with USE=-arts).
I do have Qt 4.2.2, it fails with it. I'll play with different USE flags when my exams are over (i.e. in a few days).
Even think of USE flags on Qt as qt3support or similar. Thanks, so I can work on other issues.
(In reply to comment #3) > On x86 here everything works fine, all packages emerge without problems. Could > you please try PyQt and pykde with qt 4.2.2? And try different USE flag > combinations (especially with USE=-arts). Of course I should NOT talk about Qt 4. Please tell me the output of `emerge -pv =qt-3*`.
*** Bug 170838 has been marked as a duplicate of this bug. ***
Sorry for not replying for so long. (In reply to comment #3) > On x86 here everything works fine, all packages emerge without problems. Could > you please try PyQt and pykde with qt 4.2.2? And try different USE flag > combinations (especially with USE=-arts). > This is not the case here - dev-python/PyQt-3.14.1-r2 still fails, exactly like described in bug #164562. I'm not sure what USE flags you're referring to - Qt's, pykde's, PyQt's? (In reply to comment #6) > Of course I should NOT talk about Qt 4. Please tell me the output of `emerge > -pv =qt-3*`. > Yeah, I've also already noticed that Qt4 has nothing to do with it ;) $ emerge -pv =qt-3* These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild R ] x11-libs/qt-3.3.8 USE="cups gif ipv6 mysql opengl -debug -doc -examples -firebird -immqt -immqt-bc -nas -nis -odbc -postgres -sqlite -xinerama" 0 kB Please tell me if you need any additional info.
Ok, I assume you use testing profile. Please test the ebuilds/patches provided in bugs 155170 and 166178, which seem to correct problems for some people. As was told in bug 166411, dev-python/pykde is to be removed (whenever that will happen), so I can't switch kelogviewer's dependency. I also contacted kde team, so they can help out resolving the problems with pykde.
I've tested the patch and the modified ebuild from bug #155170 - they didn't help in any way, dev-python/PyQt-3.14.1-r2 still failed. However, I noticed that in comment 40 in that bug DocReedSolomon said it's a qscintilla problem, so I tried what he suggested (downgraded to dev-python/qscintilla-1.5.1) and dev-python/PyQt-3.14.1-r2 built fine. Then I unmerged dev-python/pykde and emerged =kde-base/pykde-3.5.6 - it built fine and seems to work fine as well. I also reemerged kelogviewer (the one from Portage, without the patch from comment #1) - no problems here, either. I have no idea if it's a qscintilla bug or a PyQt bug, so I don't know which solution is better - to mask >dev-python/qscintilla-1.5.1 until it's fixed or to try to fix PyQt-3.14.1-r2 - but I've used the former fix in my local overlay just to get it to work with kde-base/pykde. PS. Yes, this is ~x86, see attachment in bug #164562 for emerge --info.
(In reply to comment #10) > However, I noticed that in comment 40 in that bug DocReedSolomon said it's a > qscintilla problem, so I tried what he suggested (downgraded to > dev-python/qscintilla-1.5.1) and dev-python/PyQt-3.14.1-r2 built fine. Good. So kelogviewer will run in serious problems when even stable users will see that qscintilla version. A member of KDE team will have a look which version of pykde will be the loser and leave the tree and also will have a look at the issues. Meanwhile, maybe kde-base/pykde will build with a newer version of PyQt...cannot check that today.
Please consider that the stable version of kde-base/pykde doesn't include KABC bindings, but the testing version of dev-python/pykde does when excluding one of them from the tree.
As nothing happened, I keyworded dev-python/pykde myself and changed the dependency. Thanks for the patience.
This broke the stable tree, as the current stable dev-python/pykde blocks >=kde-base/kdelibs-3.3.1, and thus blocks the current stable kdelibs (kdelibs-3.5.5-r10).
(In reply to comment #14) > This broke the stable tree, as the current stable dev-python/pykde blocks > >=kde-base/kdelibs-3.3.1, and thus blocks the current stable kdelibs > (kdelibs-3.5.5-r10). It broke nothing. As kelogviewer isn't stable, but I changed the dependency to pykde-3.16.0
*** Bug 174830 has been marked as a duplicate of this bug. ***
