app-crypt/qca-ossl does not depend on x11-libs/qt but should, trying to merge it without having qt installed fails: >>> Compiling source in /var/tmp/portage/app-crypt/qca-ossl-2.0.0_beta3/work/qca-ossl-2.0.0-beta3 ... Configuring qca-ossl ... Verifying Qt 4 build environment ... fail Reason: Unable to find the 'qmake' tool for Qt 4. Be sure you have a proper Qt 4.0 build environment set up. This means not just Qt, but also a C++ compiler, a make tool, and any other packages necessary for compiling C++ programs. If you are certain everything is installed, then it could be that Qt 4 is not being recognized or that a different version of Qt is being detected by mistake (for example, this could happen if $QTDIR is pointing to a Qt 3 installation). At least one of the following conditions must be satisfied: 1) --qtdir is set to the location of Qt 2) $QTDIR is set to the location of Qt 3) QtCore is in the pkg-config database 4) qmake is in the $PATH This script will use the first one it finds to be true, checked in the above order. #3 and #4 are the recommended options. #1 and #2 are mainly for overriding the system configuration. * * ERROR: app-crypt/qca-ossl-2.0.0_beta3 failed. * Call stack: * ebuild.sh, line 49: Called src_compile * environment, line 2580: Called die * The specific snippet of code: * ./configure --qtdir=/usr $(use debug && echo "--debug" || echo "--release") --no-separate-debug-info || die "configure failed"; * The die message: * configure failed * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/tmp/portage/app-crypt/qca-ossl-2.0.0_beta3/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/app-crypt/qca-ossl-2.0.0_beta3/temp/environment'. Reproducible: Always Steps to Reproduce: 1. emerge --unmerge qt 2. emerge qca-ossl
How about that, it is missing all right... this is a job for the qt team! Thanks for the report.
qca-ossl-2.0.0_beta3.ebuild has the following: DEPEND=">=app-crypt/qca-${QCA_VER} >=dev-libs/openssl-0.9.6" qca-2.0.1-r1.ebuild has the following: DEPEND="!<app-crypt/qca-1.0-r3 || ( x11-libs/qt-core:4 >=x11-libs/qt-4.2.0:4 )" Therefore this is an invalid bug.
I just hit this issue as well. It seems that I emerged qca when I still had monolithic qt-4.3.3. Now I'm trying to emerge kde-meta-4.1.2, and I was forced to remove monolithic qt-4.3.3 in favour of split qt-4.4.2, after which I went straight to emerging kde-meta-4.1.2. I guess if I'd directly emerged split qt-4.4.2 instead of letting kde-meta pull it in, I'd have avoided this. So, technically speaking I guess this is an invalid bug, but I won't be surprised if more people start stumbling upon it.
(In reply to comment #3) > it in, I'd have avoided this. So, technically speaking I guess this is an > invalid bug, but I won't be surprised if more people start stumbling upon it. > I stumbled upon it. No biggie as such, I just emerged qt manually, but using kde-meta kinda didn't work here.
I got the same issue here and things are a bit different. Yesterday I uninstalled qt 4.3 in order to install kde-meta-4.1.x. I started to emerge kde-meta yesterday and today I typed emerge --resume. There was no more built qt4 on my machine when emerge --resume choose to install app-crypt/qca-ossl-2.0.0_beta3 . Emerge failed with the message displayed upstair. I think there is another problem here and it's not invalid.
(In reply to comment #2) > qca-ossl-2.0.0_beta3.ebuild has the following: > > DEPEND=">=app-crypt/qca-${QCA_VER} > >=dev-libs/openssl-0.9.6" > > qca-2.0.1-r1.ebuild has the following: > > DEPEND="!<app-crypt/qca-1.0-r3 > || ( x11-libs/qt-core:4 > >=x11-libs/qt-4.2.0:4 )" > > Therefore this is an invalid bug. > Well I doubt: it looks like having qca-1.0-r3 is enough and app-crypt/qca-1.0-r3 : DEPEND="x11-libs/qt:3"
(In reply to comment #6) Shame on me. I can't hide my stupid last comment... I made a mistake and must apologize ! I think my problem comes from the fact qca-2.0.1 should have been compiled against qt-4.3.x long time before I started to compile kde-meta. It could be an explanation. Maybe you should add qt dependancy in order to get ride of this kind of trouble and force qca-2.x to be compiled again if required.
